16 Apr
2013
16 Apr
'13
4:23 a.m.
On Apr 15, 2013, at 11:21 PM, Nathaniel Echols wrote:
We're using a feature in Boost that traps certain C++ issues whose effect might otherwise be undefined. Some of these wouldn't normally crash the interpreter,
Is there any hope that this feature could instead raise an exception or warning, based on the value of some environment variable? As it is, you either have to be blind to the potential for such problems or you must accept that your interpreter is subject to sudden crashing. James