Re: Should crash be the top of ex.err?

new topic     » goto parent     » topic index » view thread      » older message » newer message
SDPringle said...

Sometimes the fault might be up several levels of the stack trace anyway.

Could you give me an example of this? Maybe I'm misunderstanding you, but I can't imagine any case where I'd care to see crash() at the top level unless there actually was and error in crash().

SDPringle said...

To me, you ought to have a list of 'called from' lines that the user can click on. This way the user gets the opportunity to jump to where he needs to go.

That's pretty cool functionality. Maybe you'd have to talk to Pete about that.

In the mean time, I'd settle for Euphoria presenting a stack trace that associates the error with where I said it was, not one that associates it with the location of the crash() routine.

All the current behavior does is reveal the man behind the curtain. Since the goal of using crash() is to indicate an error at a particular spot, I'd like Euphoria to honor that request.

- David

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

Search



Quick Links

User menu

Not signed in.

Misc Menu