> Gesendet: Donnerstag, 23. November 2017 um 18:24 Uhr> Von: fred...@free.fr> An: "Tcl List Core" <tcl-...@lists.sourceforge.net>> Betreff: [TCLCORE] TIP #462 : Request For Comments> Howdy Tcl'ers,> > It's been nearly 3 weeks since I've published the final draft for TIP #462> and pushed the reference implementation to the Fossil repo. Has anyone found> the time to play with the new commands ? Do you have any suggestion/remarks/correction> about the TIP ?> > Cheers,> Fred
Dear Fred,
I didn't really understand your last response to my last reply, which was based on a misunderstanding.
Today, after re-reading the TIP more sorrowfully, I hopefully understand your reply.
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"
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.
Best regards
Martin Lemburg
Berlin / Germany
mart...@gmx.net
http://about.me/Martin0815
------------------------------------------------------------------------------
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