On 08/04/2018 04:29 PM, Jeremiah Breeden wrote: > I did not realize that. I've always followed the mantra taught to me about > not > using > them in POs. That's really neat. Should we go ahead > and add a delete loop to it to prevent the potential for someone to start a > connection > between the close and the delete protected calls? Or do you think it will be > alright?
It should be true of any compiler, as in general it's impossible to detect potentially blocking operations. This is part of the reason the restriction was a mistake: the language should not have rules it cannot enforce. I haven't looked at the big picture enough to be sure, but I'd think that if the system is in a state where it's closing all connections, it should not allow the creation of a new connection. If it does, then perhaps it should have an atomic Stop operation that closes and deletes all connections, and puts the PO into a state where any further operations raise an exception. It's probably not worth the effort to implement that unless we do encounter problems with it being 2 calls. -- Jeff Carter "My mind is a raging torrent, flooded with rivulets of thought, cascading into a waterfall of creative alternatives." Blazing Saddles 89 ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Gnoga-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gnoga-list
