sys::NullErr: Coerce to non-null
fan.sys.NullErr.makeCoerce (NullErr.java:38)
...
...
Any chance of having the Err message updated to report which variable is null? Or do we loose variable names in the fcode?
It's always handy when exception messages are as explicit as possible.
brianSat 10 Mar 2012
Yeah that is a great idea. But it isn't really feasible technically since those coercion are mapped into fcode as a single opcode and without pushing an extra string literal onto the stack you don't have the proper context.
SlimerDude Sat 10 Mar 2012
Any chance of having the Err message updated to report which variable is null? Or do we loose variable names in the fcode?
It's always handy when exception messages are as explicit as possible.
brian Sat 10 Mar 2012
Yeah that is a great idea. But it isn't really feasible technically since those coercion are mapped into fcode as a single opcode and without pushing an extra string literal onto the stack you don't have the proper context.