At 10:51 AM 5/16/01 +0200, Carl Johan Berglund wrote:
>At 15.02 -0700 01-05-15, Nathan Wiger wrote:
>> $*ARGS is chomped;
>>
>>I wonder if that wouldn't be better phrased as:
>>
>> autochomp $*ARGS; # $ARGS.autochomp
>
>I see your point, but I see a clear difference between these properties
>and actions taken on the variable. When we say $*ARGS is chomped, we don't
>ask $*ARGS to do anything right away, just remember that when we later ask
>it to return something, we want that something chomped.
I've been reading "is" as a declarative imperative, something which
declares a property of something you are creating. Here it's being used to
moify the properties of something that already exists, and it reads funny
to me. Many properties that one can set at declaration time are compile
time only, yet this usage might suggest to many people that they can be
changed at run time. If you see what I mean.
I'm sure I could get used to it, I'm just speaking to learnability.
--
Peter Scott
Pacific Systems Design Technologies
http://www.perldebugged.com
