Recently I came accross what I consider a flaw (although not a very big
one) with Benchmark. If the programmer forgot to include a RETURN
statement in a function, upon completion of the execution of the function
the program simple exits (returning control to the CLI, if it was launched
from there). Now, the way it's done in other implementation, this should
generate a runtime error of some kind. I spent *HOURS* trying to track
this one down.
The exit to CLI occurs only when range checking is enabled. When range
checking is disabled the procedure returns with an undefined result. When a
post-mortem debugger is made available this will generate a run-time error.
Thanks for bringing this to my attention… Talk to you later.