Tom Christiansen wrote: > >Well, as I mentioned in another recent parallel thread, if C<for> is to > >be properly functionalized, > > Whoa -- why? Syntax keywords (eg if, unless) certainly need not be > expressible as functions. This isn't tcl! Ah, the old "If you want Tcl, you know where to find it" non-argument. "Closures?" "No! This is Perl, not Lisp!" "Objects?" "No! This is Perl, not Smalltalk!" "Patterns?" "No! This is Perl, not Snobol!" "Subroutines?" "No! This is Perl, not Basic!" "Upvars?" "No, and for the following well-understood technical reasons..." -- John Porter
- RFC 168 (v1) Built-in functions should be functions Perl6 RFC Librarian
- Re: RFC 168 (v1) Built-in functions should be fun... Peter Scott
- Re: RFC 168 (v1) Built-in functions should be... Johan Vromans
- Re: RFC 168 (v1) Built-in functions should be fun... Damian Conway
- Re: RFC 168 (v1) Built-in functions should be... John Porter
- Re: RFC 168 (v1) Built-in functions shoul... Tom Christiansen
- Re: RFC 168 (v1) Built-in functions s... John Porter
- Re: RFC 168 (v1) Built-in functi... Tom Christiansen
- Re: RFC 168 (v1) Built-in functions shoul... Johan Vromans
- Re: RFC 168 (v1) Built-in functions should be... David L. Nicol
- Re: RFC 168 (v1) Built-in functions should be... Damian Conway
- Re: RFC 168 (v1) Built-in functions shoul... Tom Christiansen
- Re: RFC 168 (v1) Built-in functions s... John Porter
- Re: RFC 168 (v1) Built-in functions s... Piers Cawley
- Re: RFC 168 (v1) Built-in functi... Tom Christiansen
- Re: RFC 168 (v1) Built-in fu... Piers Cawley
- Re: RFC 168 (v1) Built-in fu... Damian Conway