[armedbear-devel] Error condition is too strong
blake at mcbride.name
Thu Jan 13 21:14:01 UTC 2011
On second thought, if Java has anything like (I'm mainly from the C
world) flush all buffers, close all files, hold other threads, etc.
could be a problem too.
On Thu, Jan 13, 2011 at 3:08 PM, Blake McBride <blake at mcbride.name> wrote:
> On Thu, Jan 13, 2011 at 2:59 PM, Erik Huelsmann <ehuels at gmail.com> wrote:
>> Hi Blake,
>>> I am in the process of embedding ABCL into a web server application I
>>> have. While it is okay for an error to either be caught and handled,
>>> or not handled and having the thread terminate, it definitely is not
>>> okay for an error condition to kill the entire server.
>>> I am executing a (load "file") command (where "file" doesn't exist)
>>> from Java and it kills the entire server. I tried enclosing it in a
>>> try/catch block (I tried Exception & Throwable) and it still killed
>>> the server.
>> Are there any other forbidden functions for "well behaving" libraries?
> Not that I can think of. Thanks!
More information about the armedbear-devel