Re: Q: 10.4.2 "Do Shell Script" revision & passwords
Re: Q: 10.4.2 "Do Shell Script" revision & passwords
- Subject: Re: Q: 10.4.2 "Do Shell Script" revision & passwords
- From: Paul Berkowitz <email@hidden>
- Date: Wed, 13 Jul 2005 14:46:54 -0700
- Thread-topic: Q: 10.4.2 "Do Shell Script" revision & passwords
On 7/13/05 2:34 PM, "Michelle Steiner" <email@hidden> wrote:
>
> On Jul 13, 2005, at 2:27 PM, Christopher Nebel wrote:
>
>> Don't be surprised if it gets punted back as "behaves correctly".
>> "yes" is not a boolean. "true" and "false" are.
>
> I should have waited for your reply. <g>
>
> But "yes" compiles. What is the class of "yes"? Applescript says it
> is a constant, but it also says that "true" is a constant
They're both constants, sure. 'true' and 'false' are the only boolean
constants, so if a parameter or property stipulates 'boolean' type you're
limited to 'true' and 'false'. 'yes' is a defined constant that is accepted
for certain enumerated constants. The usual set is yes/no/ask, but there are
others around. Occasionally, as with the 'replacing' parameter of 'store
script', although it specifies yes/no/ask it seems to accept (coerce) 'true'
and 'false' as synonyms for 'yes' and 'no': that might be the case for
(most?) other command parameters stipulating this set of enumerated
yes/no/ask constants too. But not vice versa: 'boolean' type won't take
'yes' or 'no', only 'true' or 'false'. (I think there are probably a few
boolean implementations that might accept 1 and 0, although I can't recall
any offhand.)
>
> In what situations would yes and no be used in a script?
>
> BTW, "true" does compile correctly.
--
Paul Berkowitz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden