>> $IO::STDERR->print @stuff;
>> print $IO::STDERR @stuff;
You know, I already resent having to use STDERR instead of stderr.
Adding five noisy characters, or seven, is way, way over the top.
As for system globals, when one suggested to Larry that these be
something on the order of SYS::ARGV
>> foo->bar($baz, $coon)
>> should be made synonymous with
>> foo->bar $baz, $coon
>>
>> I can see no ambiguity in this call, but it not always works with Perl5.
Arrow invocation does not a listop make. Only indirect object invocation
style does that.
print STDOUT $foo, $bar, $glarch;
Nathan Wiger wrote:
> > This RFC proposes to remove indirect object syntax
>
> Please show me how to write:
>
>print STDERR @stuff;
>
> without it, while keeping it a method of the STDERR filehandle, and
> without requiring ->.
Hopefully STDERR as a "filehandle" is going away. Assuming it
> 'foo'->bar($baz)
>
> looks visually clattered, but C> looks as if it expresses
> its meaning. The default choice is done so that if you need other
> choice, your code does not look artificial.
Hear, hear!
> foo->bar($baz, $coon)
>
> should be made synonymous with
>
> foo
> This RFC proposes to remove indirect object syntax
Please show me how to write:
print STDERR @stuff;
without it, while keeping it a method of the STDERR filehandle, and
without requiring ->.
-Nate
On Sat, Sep 16, 2000 at 08:08:06AM -, Perl6 RFC Librarian wrote:
> There only way to avoid the action at a distance is to prohibit one of these
> interpretations. Since the other way C> to write this
> method call is as convenient as the indirect object syntax, the proposal
> is to
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Method calls should not suffer from the action on a distance
=head1 VERSION
Maintainer: Ilya Zakharevich <[EMAIL PROTECTED]>
Date: 15 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 244
Version: