Tom Christiansen wrote:
>
> Please print to STDERR some "darn" thing.
>
> I know Damian never inflected it this way, but I always find the
> leading object a bit (e)vocative. It's more natural to me in regular
> coding to put the verb first; call me Imperative.
I absolutely, positively, 100% AGREE with this. I am *very* much aware
of this. That's why I think that losing the indirect object syntax - or
even requiring it to be explicitly notated - would be the biggest
numbskull mistake ever made.
print $STDERR "ELEMENT: $_\n" for (@list);
print $FILE $line while ($line = <$STDIN>);
And the other bizillions of examples which demonstrate how incredibly
beautiful this is. Just looking at code like this gives me the warm
fuzzies.
But which one's an object? method? builtin? Who cares? Maybe the CS
purists, but not me.
-Nate
