Damian Conway wrote: > > I intend to extend the parameter lists RFC to cover optional > (non-tailing) arguments. Personally, I would like to see the > indirect object syntax removed in all contexts, inclusing > this one, and filehandles simply passed as a first argument. Whoa there! :-) Not necessarily opposed, but I just submitted an RFC on this very topic, which seems like it overlaps much with this current discussion. I'd invite you to read it before submitting yours, so that you can either integrate it or oppose it. ;-) Basically, it "fixes" the indirect notation by making all of these Do The Right Thing: $r = new CGI (@args); # CGI->new(@args) $r = new(CGI, @args); # CGI->new(@args) $r = new(CGI @args); # CGI->new(@args) It's all in the details (I'm sure you see the edge cases already, but they're addressed), so I invite people to read it. I posted it to -subs. -Nate
- 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