Tom Christiansen <[EMAIL PROTECTED]> writes: > >I intend to extend the parameter lists RFC to cover optional > >(non-tailing) arguments. > > Will this include having typed variadic functions, allowing you, for > example, to say something like > > This function takes any number of arrays, all passed by reference. > > I keep thinking of a * or a ... to say "repeat the previous thing", > but that's stepping on other toes. Doesn't that tend to lead us in the direction of pack madness where we end up with yet another 'sub language' within perl. We've already got pack specifiers and regexen and the 'old' prototyping stuff. I'm not arguing *against* these things you understand, I'm just vaguely worried. -- Piers
- Re: RFC 168 (v1) Built-in functions should be functions Damian Conway
- Re: RFC 168 (v1) Built-in functions should be functi... John Porter
- Re: RFC 168 (v1) Built-in functions should be fu... Tom Christiansen
- Re: RFC 168 (v1) Built-in functions should b... John Porter
- Re: RFC 168 (v1) Built-in functions shou... Tom Christiansen
- Re: RFC 168 (v1) Built-in functions should be fu... Johan Vromans
- Re: RFC 168 (v1) Built-in functions should be functi... David L. Nicol
- Re: RFC 168 (v1) Built-in functions should be functi... Damian Conway
- Re: RFC 168 (v1) Built-in functions should be fu... Tom Christiansen
- Re: RFC 168 (v1) Built-in functions should b... John Porter
- Re: RFC 168 (v1) Built-in functions should b... Piers Cawley
- Re: RFC 168 (v1) Built-in functions shou... Tom Christiansen
- Re: RFC 168 (v1) Built-in functions... Piers Cawley
- Re: RFC 168 (v1) Built-in functions... Damian Conway
- Re: RFC 168 (v1) Built-in functions should be fu... Nathan Wiger
- Re: RFC 168 (v1) Built-in functions should b... Tom Christiansen
- Re: RFC 168 (v1) Built-in functions shou... Nathan Wiger
- Re: RFC 168 (v1) Built-in functions should be fu... John Porter
- Re: RFC 168 (v1) Built-in functions should be functions Damian Conway
- RE: RFC 168 (v1) Built-in functions should be functions Fisher Mark