On Thu, Oct 15, 2009 at 2:21 PM, Alan Ruttenberg alanruttenberg@gmail.com wrote:
On Thu, Oct 15, 2009 at 5:50 AM, Erik Huelsmann ehuels@gmail.com wrote:
Hi Alan,
On Thu, Oct 15, 2009 at 5:53 AM, Alan Ruttenberg alanruttenberg@gmail.com wrote:
I'm sorry about this bug report. Basically, a system I've been working with for a long time has ceased to function in odd ways. I suspect it has to do with exception handling changes recently introduced because the symptom seems to be that a java function that I call that has a timeout function continues to run even after the timeout is supposed to have happened.
Are you talking about ABCL? Or about something else? Which version of ABCL? Trunk? 0.16?
Both it appears. The java code being called is from the pellet reasoner, which has timers which it checks while it does it's work, and when they are exceeded it throws the exception.
Ok. The most helpful would be a version number (or repository revision number) which starts failing.
Could you provide a bit more information on what the code is doing?
One of the things I mean to ask here: are you calling the lisp code from the EVAL function? Or straight SYMBOL.execute() calls?
Unfortunately working on isolating the bug isn't something I have time for so I've had to revert back to an earlier version.
Wish I could say more at this point, but perhaps just notice that this is happening might ring a bell for someone.
If you're not talking about J, but specifically about ABCL, then, no, no bell yet. However, I'd like to look into it, ofcourse.
abcl. I'll try to narrow it when I have some time.
Thanks!
Bye,
Erik.