> > You know, I would like to pass code blocks in any arg position;
   > > I want  sub foo(&\@&\@&)  to be callable as 
   > > 
   > >  foo { alpha() } @bravo { charlie() } @delta { echo() };
   > > 
   > > No C<sub>s, no commas.

Already in the RFC.

   > And one further note:  it would be nice if, given a prototype
   > which does not include a rest-gobbling member, the invocation
   > need not have a terminating semicolon.  This is in the interest
   > of defining user subs which look like syntactic constructions.
   > E.g.
   > 
   >    sub my_while(&&);
   > 
   >    my_while { pred() } { # don't gimme no Tcl flac.
   >            ...
   >    } # no semicolon needed here!

Just added to the RFC :-)

Damian

Reply via email to