Re: handler failure [oops! correction]
Re: handler failure [oops! correction]
- Subject: Re: handler failure [oops! correction]
- From: Axel Luttgens <email@hidden>
- Date: Fri, 15 Nov 2002 09:32:23 +0100
First, I would like to apologize for a previous post of mine to the
"handler failure" thread, that may seem redundant with what has been
since written in the present thread.
That's the problem when you reply to a message without having had the
opportunity to receive (and thus read) subsequent messages.
Since I'm presently in a similar situation, I hope it won't be the case
for this message...
Michael Terry wrote:
>
On 11/13/02 11:40 AM, "has" <email@hidden> wrote:
>
>
>
>
>[snip]
>
>
>
>
>
>
>
OK, has, I'll play your little game. It looks to me like property
>
identifiers are linked to their values by a number index at compile time. A
>
separate index is created for each scope. If a handler moves into a new
>
scope and references a property, there's a problem. It tries to look up its
>
property's value in the new index using the index number it was given for
>
the old index at compile time. Results are even less comprehensible than
>
above if the index number refers to a position in the new index which
>
doesn't exist.
>
>
[snip: scripts]
>
>
>
Hypothesis: your last sentence (and corresponding scripts) seem to
indicate that one is referencing some script properties created and
maintained by AppleScript itself.
(could lead to some interesting experiments)
I just performed some quick experiments; my results where consistent but
differed from yours (very likely due to implementation differences - OSX
10.1.5 / A.S 1.8 here).
_______________________________________________
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.