2:07:14stassatsis your LOOP crippled at that point?
2:07:14drmeisterIt creates a widget, displays the widget and then launches a thread that has a jupyter notebook cell dynamic environment and can update widgets.
2:15:08drmeisterWell, the key point is I can set up complex dashboard of jupyter widgets and have them updated asynchronously from a thread that watches a bunch of processes, directories and files to monitor their progress.
2:15:23drmeisterWhether this is a good idea - I'm not so sure.
2:15:44drmeisterI just didn't like the idea of evaluating a jupyter notebook cell and having it go off into la la land for hours and days.
2:16:30drmeisterI could put a button into it that would exit the evaluation.
2:16:52drmeisterI'm still mulling over approaches of how to develop an "application" in a Jupyter notebook.
5:13:37drmeisterHmmm. I was describing to Bike my musings about an instruction that would check the status of a flag and if it was set would unwind the stack.
5:14:10drmeisterSomething that would be inserted at the bottoms of loops and at the ends of functions to check for signals and do something if a signal was received.
5:14:25drmeisterHe thought it sounded like this facility that you were thinking of adding for debugging.
5:26:59drmeisterGot it. I found some stuff in Muchnick's book.
5:28:48beachThen you also make sure that every back arc (and return, and ...) is such that your virtual machine is in a state that makes it capable to take Unix signals.
5:56:23drmeisterUnix signals are asynchronous and C++ exception handling is synchronous - there is no way to marry them other than to have safe points in the code.