"Ask us anything" and the executionContexts

Dick Kriesel dick.kriesel at mail.com
Sat Dec 17 04:14:16 EST 2005


Your answer left me a hope that maybe we were just a BZ away from being able
to use the executionContexts in a standalone, so I decided to search BZ
before asking about that possibility.  The result was a surprise, so here's
another question:

Would you please comment on the resolutions of BZ 724 and BZ 1243?  I know
you're not speaking officially for RR, but you know the BZ business process
pretty well.

On 2003-9-29 Jeanne Devoto (then still at RR) commented on BZ 724: the
executionContexts "... will be documented sooooooon (probably the next
nonbugfix release)..."  She later commented "Removed for 2.1.2."

BZ 724 shows severity "minor" and status "RESOLVED/FIXED."  But there's
still no entry for the executionContexts in the dictionary.

BZ 1243 in an enhancement request for implementing and documenting anything
like the functionality of the executionContexts (my words, not Dar's).

BZ 1243 shows status "RESOLVED/NOT_A_BUG."  Of course it was "not_a_bug;" it
was an enhancement request.

If these weren't marked "resolved" I'd vote for them.  Instead of voting,
what's the next step to take?

Thanks again in advance, Jacque.

-- Dick



On 12/16/05 8:41 AM, "J. Landman Gay" <jacque at hyperactivesw.com> wrote:
> Dick Kriesel wrote:
>> On 12/15/05 10:27 PM, "J. Landman Gay" <jacque at hyperactivesw.com> wrote:
>> 
>> 
>>> Ask us anything, anything at all. Really.
>> 
>> 
>> An offer far too good to refuse.
>> 
>> The executionContexts could be a useful tool if it were sanctioned for use
>> in standalones.  What is there about the executionContexts that causes it to
>> remain undocumented and unsupported for standalones?
>> 
>> Thanks in advance, Jacque!
> 
> Hey, I didn't say I could *answer*. :)
> 
> But as I understand it, the executionContexts was implemented internally
> when the script editor was rewritten, back when MetaCard first changed
> over to allowing clickable breakpoints (yes, there was a time when that
> wasn't in there.) It was never intended for consumer use, but its
> availability leaked out and some folks started taking advantage of it.
> Officially it isn't really supported, and there are no guarantees that
> it won't change in the future. Thus, it's not documented.





More information about the Use-livecode mailing list