Re: (beep) as string
Re: (beep) as string
- Subject: Re: (beep) as string
- From: Walter Ian Kaye <email@hidden>
- Date: Tue, 18 Nov 2003 15:46:36 -0800
At 12:56p -0800 11/18/2003, Christopher Nebel didst inscribe upon an
electronic papyrus:
On Nov 17, 2003, at 2:51 AM, Nigel Garvey wrote:
"Fredo d;o)" posted this line in a script on bbs.applescript.net
yesterday:
Hehe, I thought that d;o) was this listserv munging a non-English
name so I ran my new scripts on it, but couldn't make heads or tails
of the result. Finally I realized it was a smiley. LOL
According to the language spec, it's a bug. I'll have to test with
older versions, since I could have sworn that used to not work.
Mac OS 7.6.1: "Can't make some data into the expected type."
It does beep, though. ;)
If it turns out to have changed recently, then we'll see about
fixing it in a small update; if it's always been that way, then
we'll leave it alone.
However, 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.
Heck, I'd be happy if we could just recapitalize variables... :)
-boo
_______________________________________________
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.