>>>>> "DC" == Damian Conway <[EMAIL PROTECTED]> writes: >> How would the parser handle this? Some '}' would need ';' some don't. DC> The trailing C<&> parameter specification tells the parser that there DC> the last argument will be a raw block and that it need not be a followed DC> by a semicolon. It's no harder than parsing an C<if>, C<while>, or C<for>, DC> except that parser has to update itself when it sees the parameter DC> specification. An excersize left for the student, eh? Sounds messy. That next brace could be one of many things. Does the prototype help guide the decision that it is a block and not an anon-hash? <chaim> -- Chaim Frenkel Nonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183
- 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
- Re: Multiple for loop variables Jeremy Howard