Re: path to as string
Re: path to as string
- Subject: Re: path to as string
- From: Brennan <email@hidden>
- Date: Thu, 30 Jun 2005 10:24:39 +0200
On 28/6/05 at 12:06, Christopher Nebel <email@hidden> wrote:
> why any of this is relevant to users, aside from the fact that you
> shouldn't be saying "path to ... as string" in the first place. (Use
> "as Unicode text" instead.)
Chris, PLEASE add this to the Applescript Lanuage Guide.
Rightly or wrongly, people will continue expect that 'string' is the most
intuitive datatype for handling sequences of characters until told
otherwise.
AFAICT There is no warning in ASLG that 'string' is a deprecated type for
working with paths. This should be mentioned clearly and be
cross-referenced from all the appropriate places.
Yes, encoding is covered under the newer section, 'Unicode Text and
International Text', but the cross-reference from the entry on 'String' in
'Common Value Class Defintions' is not emphatic enough. It just says "For
information on additional string value class types see..." which sounds
like something we don't need to look at right away.
Neither does ASLG say what (if anything) happens to the encoding when we
concatenate two Unicode Text objects by coercing to string, which is the
suggested workaround. This is important and missing information.
It should be made very clear in ASLG when to use each form, and (more
importantly) when not to, otherwise threads like this will run and run.
Much easier just to say "look at page X of ASLG".
BTW shouldn't there be a discussion of the alias class in ASLG? Most of
the section "References to Files" seems to have been removed from the HTML
version (though it is still present in the PDF version). This is a
significant shortcoming.
Brennan
_______________________________________________
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