Re: (beep) as string
Re: (beep) as string
- Subject: Re: (beep) as string
- From: Arthur Knapp <email@hidden>
- Date: Tue, 18 Nov 2003 09:44:03 -0500
Subject: (beep) as string
Date: Mon, 17 Nov 2003 10:51:00 +0000
From: Nigel Garvey <email@hidden>
display dialog "The required label does not exist..." & (beep) with
set msg to "The required label " & (beep) & "does not exist..."
But it's not an empty list: it's a list containing a non-result!
Its the <<class undf>> value, which pops up from time to time in
strange places. (Note: those are the "chevron" things, option-\ and
shift-option-\ on a U.S. keyboard). Consider this:
set v to <<class undf>>
When you compile this, the editor then shows this:
set v to
However, the value has actually "compiled," and you can test this by
running the script, there will be no error. Once you modify the script
such that it has to recompile, however, you can the normal syntax
error:
set v to --> error "Expected expression but found end of script."
I used to get this mysterious, invisible value in my early
AppleScript experiments:
{, 3.14, , true, etc, , ,}
Its clearly an internal "null" value of some kind that wasn't
intended to be accessable to scripters. Note: it is not to be confused
with this:
<<class null>>
which is an entirely different "null" value.
{ Arthur J. Knapp;
<
mailto:email@hidden>;
What...? Oh...!
}
_______________________________________________
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.