On Monday, 20 January 2014 at 20:01:58 UTC, Ola Fosheim Grøstad wrote:
Ideally safe-D should conceptually give you isolates so that an application can call a third party library that loads a corrupted file and crash on a null-ptr (because that code path has never been run before) and you catch that crash and continue. Yes, the library is buggy and only handles consistent files well, but as an application programmer that is fine.

The point is: for true isolation you'll need another process. If you are aware that it could die: let it be. Just restart it or throw the file away or whatever. So given true isolation hlt on null ptr dereference isn't an issue.


Reply via email to