On Sat, May 20, 2017 at 4:06 PM, Mathieu Lafon <mla...@gmail.com> wrote:
> Regarding the two proposals made by Alexandre :>> - Adding a new FAproc command will require to duplicate a lot of code> already present in proc, leading to more maintenance. Users may find> confusing to have a separate command and new users may not find it.
I concur with Colin's answer to this: appropriate refactoring may
avoid any duplication. But never mind, as stated, this is not my
preferred choice.
> - Adding a runtime handler seems to be limited to argument parsing,> where the current proposal is a base framework which can be easily> extended to later support other usecase on proc arguments (type> assertion, doc-string, ...).
Yes, and to me this lack of ambition is a bonus. Think KISS principle.
Do one thing at a time, and do it right. Don't open a Pandora box on
vague promises.
In this specific case: type assertions and doc strings can quite
easily fit in handlers too, or in formatted comments at the top of the
proc's body.
> Unless I don't get the intent, it seems> necessary to specify the named arguments when calling the command.> Users may find counter-intuitive to have to specify the arguments in a> second time (I assume proc only use 'args' in that case).
Please give an example, I'm lost. You may even give a hefty list of
them, as an exercise for me to map to [eatargs] form :)
-Alex
------------------------------------------------------------------------------
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