On 6/26/20 2:37 PM, Robert Withers wrote:

> On 6/26/20 1:55 PM, Robert Withers wrote:
>
>> Closer to my heart, at this point are my questions and request for help
>> in splitting off a pruned stack for an exception, to unblock the event
>> loop yet still allow introspection of an error, or a halt. Here is what
>> I wrote. Tim, might you be able to advise me here?
>>
>> *
>>
>> lost
>>
>> *
>>
>> http://lists.squeakfoundation.org/pipermail/squeak-dev/2020-June/210452.html

The requirements for exceptions within an event loop are:

- Copy stack
- Restart eventLoop
- Prune stack/Create Continuation
- Open Debugger
- When Proceeded, reschedule EventualMessageSend, on the Continuation, in the vat queue.

Would someone please help me here? I am a little lost. I appreciate you!

Kindly,
rabbit

> Not only do I want this, but the short stack, when Proceeded, should reschedule an eventual message on the event loop to reintroduce this short stack back into event loop land. As such, i was thinking perhaps a continuation could enable this. Liekwise, when a exception is thrown, do these steps:
>
>> - Modify the Vat to have a an active stack, a priority queue and a vat-aware continuation pool.
>> - Copy the stack. Does this mean create a special continuation, that is event loop aware?
>> - Resume the event loop by discarding the previous event handling exception.
>> - Prune the stack (of the continuation). above and below. Site of signaled exception.
>> - Open a Debugger
>> - On Proceed, reschedule the eventual message in the Vat's queue.
>
> I have no idea what B looks like. Outside of my experience doing continuations and stack manipulation and pool scheduling. I need a VatSemaphore (please peruse the ResultSemaphore in PromisesRemote). I pray someone may swoop in with solutions!
>
> Kindly,
> rabbit
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20200712/4752f0c9/attachment.html>