cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Sign-in to the JMP Community will be unavailable intermittently Dec. 6-7 due to a system update. Thank you for your understanding!
  • We’re retiring the File Exchange at the end of this year. The JMP Marketplace is now your destination for add-ins and extensions.
  • JMP 19 is here! Learn more about the new features.

JMP Wish List

We want to hear your ideas for improving JMP. Share them here.
Choose Language Hide Translation Bar

Error Types

I think it would be neat if we could throw and catch error types like in python/js/ruby since we have classes now.  So if I wanted to only catch specific error types I could do that. 

 

And being able to have a builtin error type that we could have the classes inherit would be great.  Then having the exception_msg be that class with easier to parse information (including traceback with lines) rather than the {"Name Unresolved: bbb"(1, 2, "bbb", bbb /*###*/)}.

That way we could do something like 

Names default to here(1);
try(
	a = bbb;
, 
	show(exception_msg["message"]) // show the relevant message
	show(exception_msg["caller"]) // what function the exception happened in
	show(exception_msg["traceback"][2]["message"]); 
	show(exception_msg["traceback"][2]["line"]);
);

Similar to this https://community.jmp.com/t5/JMP-Wish-List/Improved-JSL-Stack-Trace-in-Log-on-Error/idi-p/78104

 

1 Comment
Ryan_Gilmore
Community Manager
Status changed to: Archived
We are archiving this request. If this is still important please comment with additional details and we will reopen. Thank you!