v2.5 suggestions

new topic     » topic index » view thread      » older message » newer message 

How about a specific constant we can use with abort() that will trigger the
crash routines?  abort(1/0) will work, I suppose, but abort(FATAL_ERROR) might be
more elegant.  Also, a way to reset or re-order multiple crash routines would
probably come in handy.

And let's get routine_id()'s for the built-in functions for the final v2.5
already.  This can't possibly be a very big deal at all...

new topic     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu