----- Mail original -----
> De: "Martin Lemburg" <mart...@gmx.net>> > Let me comprehend:> 1. open and exec stay to be only root namespace commands> 2. there will be no ::tcl::process::(exec|open) commands.> 3. nothing changes in this "area"
That's right.
> > But why not initially enhancing the ability to create (sub) processes> a bit, using the ::tcl::process namespace?> To have a less "command line" orientated syntax for creating> (a)synchronous (sub) processes eventually bound with a pipe.> > Why staying with the need to build strings as "command lines" to> start (sub) processes?> > Perhaps, I never was in too deep into console based system> management. I ever disliked the need to build command lines to be> used with both commands, so … is there really no interest in such an> addition?> > Yes, it is not part of the TIP 462, but I would have expected in the> TIP from the start - that's the reason for the confusion of mine.
No problem. Indeed that could be the subject of a future TIP, adding new, lower-level subcommands to the [tcl::process] ensemble for direct process creation/handling (including those not created by Tcl itself). But it is a much broader scope than the initial concern addressed by TIP #462 (see the original Tcl Bounty description).
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Tcl-Core mailing list
Tcl-...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tcl-core