Re: Interactive programming with pengines
Jan Wielemaker <[email protected]>
| Newsgroups | gmane.comp.ai.prolog.swi |
|---|---|
| Message-ID | <[email protected]> |
On 02/11/2014 03:48 AM, Alan Baljeu wrote: > I don't know if it makes sense here, but with Chr I can write: > > build_some_stuff(xxx), break. > > With that, all the objects remain built and I can write endless queries on that state. What I'm tempting to look at is adding primitives that allow for monitoring activity around message queues. Not sure what it would look like. One option would be a debug hook into adding a message to a queue and fetching one, both providing both the term and the sender/receiver. One probably would also want information about which threads are blocked in a read/write from/to a queue and a way to inspect the contents of a queue. If you have that, you can write a nice UI that shows communicating threads (pengines in this case). You can also write a little background thread that writes terms send to the main thread input queue, so you have what Torbjörn wants to see, but without removing them from the input queue (well, you *could* also do that. I think something like that would make a lot of sense for debugging threaded applications where the threads do a lot of communication. Cheers --- Jan _______________________________________________ SWI-Prolog mailing list [email protected] https://lists.iai.uni-bonn.de/mailman/listinfo.cgi/swi-prolog