Bart Lateur wrote: > > Combine this with the RFC that bare filehandles must die, in favor of > $FH filehandles, and you won't be able to make the distinction between > > print $HANDLE, $string; > and > print $string, $string; Sure you will! Please re-read the precedence rules from the RFC. 1. main::print 2. CORE::print 3. $ARG[1]->print > In fact, it's already impossible to distinguish between > > print $HANDLE; > and > print $string; > > which essentially renders one of both illegal. That's a different beast altogether. Maintaining the default filehandle will always require a special CORE::print that sends stuff to the right place, even with the current indirect object notation. -Nate
- Re: RFC 174 (v1) Parse C<func($obj, @args)> as... Tom Christiansen
- Re: RFC 174 (v1) Parse C<func($obj, @args)>... Tom Christiansen
- Re: RFC 174 (v1) Parse C<func($obj, @args)> as... Nathan Wiger
- Re: RFC 174 (v1) Parse C<func($obj, @args)>... Tom Christiansen
- Re: RFC 174 (v1) Parse C<func($obj, @args... Nathan Wiger
- Re: RFC 174 (v1) Parse C<func($obj, @args)> as... Damian Conway
- Re: RFC 174 (v1) Parse C<func($obj, @args)> as C<... Damian Conway
- Re: RFC 174 (v1) Parse C<func($obj, @args)> as... Tom Christiansen
- Re: RFC 174 (v1) Parse C<func($obj, @args)>... Nathan Wiger
- Re: RFC 174 (v1) Parse C<func($obj, @args... Bart Lateur
- Re: RFC 174 (v1) Parse C<func($obj, @... Nathan Wiger
- Re: RFC 174 (v1) Parse C<func($obj, @args)> as C<... Damian Conway
- Re: RFC 174 (v1) Parse C<func($obj, @args)> as C<... Damian Conway
- Re: RFC 174 (v1) Parse C<func($obj, @args)> as... Nathan Wiger
- Re: RFC 174 (v1) Parse C<func($obj, @args)>... Tom Christiansen
- Re: RFC 174 (v1) Parse C<func($obj, @args... Buddha Buck
- Re: RFC 174 (v1) Parse C<func($obj, @... Tom Christiansen
- Re: RFC 174 (v1) Parse C<func($obj, @... Bart Lateur
- Re: RFC 174 (v1) Parse C<func($obj, @args... Nathan Wiger
- Re: RFC 174 (v1) Parse C<func($obj, @args)> as... Tom Christiansen
- Re: RFC 174 (v1) Parse C<func($obj, @args)> as C<... Damian Conway