Re: scripts revert to +AKs-class foob+ALs-
Re: scripts revert to +AKs-class foob+ALs-
- Subject: Re: scripts revert to +AKs-class foob+ALs-
- From: John Delacour <email@hidden>
- Date: Wed, 13 Aug 2003 22:23:48 +0100
At 1:11 pm -0700 13/8/03, Matthew Galaher wrote:
Thanks for all the help on this. While I would still be interested
to know why any script would change elements to chavrons followed by
'class' foobar where actual working code was before hand, My script
now completes syntax checking with out error. But I had installed
Developer Tools, logged out and a few other things so I can no
longer be sure what the cause was. It was in a finder tell block and
the example was from real code.
If you compile a script in an environment where a class/event and its
human language are in scope, then the token will resolve to its human
language equivalent in your script.
If you open the script in an environment where the class is either
not available or has no human language equivalent, then you will get
+AKs-class abcd+ALs-
+AKs-constant ****abcd+ALs-
+AKs-event cantdoit+ALs-
The case is usually that the application that contained the thing is
missing from the new environment ot is of an earlier version that
does not use that class.
If you compile a script sontaining 'path to application support'
under a recent OS and then move the script to a machine running Mac
OS 7.6, you will get
path to +AKs-constant afdrasup+ALs-
and the script will run nevertheless because the system understands
the constant even though it has no human language label, but this is
rare.
JD
.
_______________________________________________
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.