>  > Wouldn't it be easier to try to solve the argument expansion
>  > problem as a list problem?  How about a list command which 
>  > expands sublists?  
>  
>  This has already been proposed, and the key issue is that it 
>  doesn't really simplify things.  You own solution does not 
>  significantly differ from some previous ideas for an 'expand' 
>  command.  I don't think this really improves on anything ...

My apologies, then.  I didn't recall a list solution, and re-reading TIPs
and several really long old c.l.t. threads yesterday led me to believe that
all the expand command proposals involved "expand-and-execute", and were not
merely list operations.  But its been a loooong discussion. :-)


>  
>  >   eval [lexpand button .b expand $stdargs -text $mytext -bd $border]
>  
>  and here you use 'expand'.  A mistake?  Unmentioned syntax?

Oops.  Mistake.  Should have been "sublist."  


>  >   eval [lexpand -flag EXPAND exec $prog EXPAND $opts1 EXPAND
>  > [getMoreopts] $file1 $file2]
>  
>  Ack, that's unfriendly looking.  

I agree.  The only similar "flag string" proposal I saw in old postings used
"+".  I thought that perhaps something like the (now more common) use of
"-> " in regexp might work, and be visually distinctive.  But if this really
does retrace old ground, I apologize for burning the bandwidth.

Good luck,
Bob
-- 
Bob Techentin                        techentin.robert@[...].edu 
Mayo Foundation                                 (507) 538-5495 
200 First St. SW                            FAX (507) 284-9171
Rochester MN, 55901  USA            http://www.mayo.edu/sppdg/ 


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Tcl-Core mailing list
Tcl-Core@[...].net
https://lists.sourceforge.net/lists/listinfo/tcl-core