8 Oct
2013
8 Oct
'13
5:19 p.m.
On 7 October 2013 21:18, Gavin Lambert
While it's *possible* that the null came from some global state that will break all future operations, it's more likely that it was some local state within the operation that becomes irrelevant when it starts processing the next operation anyway.
In other words, you are pretending the code knows the root cause of the programming bug it was never supposed to have and can magically recover from it. (Not sure what this has to do with Boost anymore...) -- Nevin ":-)" Liber mailto:nevin@eviloverlord.com (847) 691-1404