Re: (beep) as string
Re: (beep) as string
- Subject: Re: (beep) as string
- From: Christopher Nebel <email@hidden>
- Date: Tue, 18 Nov 2003 16:57:51 -0800
On Nov 18, 2003, at 3:46 PM, Walter Ian Kaye wrote:
At 12:56p -0800 11/18/2003, Christopher Nebel didst inscribe upon an
electronic papyrus:
I happen to agree with the "buggy" behavior. I expect to change
AppleScript at some point to be not so fussy about "undefined" values
-- Perl works this way, and it seems to work well for them.
Well Perl lets you undefine a value. Would we get similar
functionality then?
I mean, there's more to Perl's handling of "undefined" than
unfussiness.
I'm not sure that I'd add the "undef" command; I was thinking more of
their treatment of "undef" as a value and the way that uninitialized
variables return undef. For example, this breaks in AppleScript,
because x isn't defined yet:
set x to x + 1
However, the equivalent "$x = $x + 1" works in Perl and sets $x to 1,
because $x is implicitly the value "undef", which coerces to zero.
AppleScript sort of has this in the "missing value" value, but it's not
the same thing as the internal "undefined" value (yes, there is one)
and it's not very consistently handled.
Heck, I'd be happy if we could just recapitalize variables... :)
That's an entirely different matter. However, it's also on my list.
--Chris Nebel
AppleScript Engineering
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.