> >> my_while { pred() } { # don't gimme no Tcl flac. > >> ... > >> } # no semicolon needed here! > > DC> Just added to the RFC :-) > > How would the parser handle this? Some '}' would need ';' some don't. The trailing C<&> parameter specification tells the parser that there the last argument will be a raw block and that it need not be a followed by a semicolon. It's no harder than parsing an C<if>, C<while>, or C<for>, except that parser has to update itself when it sees the parameter specification. Damian
- Re: Beefier prototypes (was Re: Multi... Chaim Frenkel
- Re: Beefier prototypes (was Re: ... Bart Lateur
- Re: Beefier prototypes (was ... Chaim Frenkel
- Re: Beefier prototypes (was ... Bart Lateur
- Re: Beefier prototypes (was ... Chaim Frenkel
- Re: Beefier prototypes (was ... Bart Lateur
- Re: Beefier prototypes (was ... Tom Christiansen
- Re: Beefier prototypes (was Re: Multiple for loop... John Porter
- Re: Beefier prototypes (was Re: Multiple for loop... Damian Conway
- Re: Beefier prototypes (was Re: Multiple for ... Chaim Frenkel
- Re: Beefier prototypes (was Re: Multiple for ... Damian Conway
- Re: Beefier prototypes (was Re: Multiple ... Chaim Frenkel
- Re: Beefier prototypes (was Re: Multiple ... 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
- Re: Multiple for loop variables Eric Roode
- Re: Multiple for loop variables Jonathan Scott Duff