> > 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
- Re: Beefier prototypes (was Re: Multiple... John Porter
- Re: Beefier prototypes (was Re: Mul... Peter Scott
- Re: Beefier prototypes (was Re: Multiple... Chaim Frenkel
- Re: Beefier prototypes (was Re: Mul... Bart Lateur
- Re: Beefier prototypes (was Re:... Chaim Frenkel
- Re: Beefier prototypes (was Re:... Bart Lateur
- Re: Beefier prototypes (was Re:... Chaim Frenkel
- Re: Beefier prototypes (was Re:... Bart Lateur
- Re: Beefier prototypes (was Re:... Tom Christiansen
- Re: Beefier prototypes (was Re: Multiple for loop va... John Porter
- Re: Beefier prototypes (was Re: Multiple for loop va... Damian Conway
- Re: Beefier prototypes (was Re: Multiple for loo... Chaim Frenkel
- Re: Beefier prototypes (was Re: Multiple for loo... Damian Conway
- Re: Beefier prototypes (was Re: Multiple for... Chaim Frenkel
- Re: Beefier prototypes (was Re: Multiple for... Damian Conway
- Re: Multiple for loop variables Eric Roode
- Re: Multiple for loop variables Graham Barr
- Re: Multiple for loop variables John Porter
- Re: Multiple for loop variables Steve Simmons
- Re: Multiple for loop variables Peter Scott
- Re: Multiple for loop variables David L. Nicol