23 Jan
2011
23 Jan
'11
6:58 p.m.
On 23 January 2011 20:15, Ville Voutilainen <ville.voutilainen@gmail.com> wrote:
I think I've found the reason, and it's not autoload but rather Condition.getMessage(), which
Ok, actually it's probably a bit of both. As Blake said, defining a class makes (time) print a correct message. The Condition.getMessage() is botched, it shouldn't return anything else besides null, but there seems to be an autoload problem as well.