cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Learn how to build custom Python data connectors and further customize JMP’s Data Connector Framework with the Python Data Connector Demo, available now in the JMP Marketplace!
  • See how to create experiments to support product design and ID useful product features. Register for June 12 webinar, 2pm US Eastern Time.

Discussions

Solve problems, and share tips and tricks with other JMP users.
Choose Language Hide Translation Bar
ErraticAttack
Level VI

Fatal JMP16 bug

This isn't a question, just brining awareness to an issue that I recently noticed within my scripts since moving to JMP16 -- namely, I'd assume that Is Namespace( ... ) would not return a truthy value for a deleted namespace, but it does in JMP16.2 (but not in JMP14.3)

 

Because of this, the following script crashes JMP16.2:

ns = New Namespace();
ns:ns = New Namespace();
ns:ns << Delete Namespace();
Show( Is Namespace( ns:ns ) );
If( Is Namespace( ns:ns ),
	ns:ns:__item__ = 4;
);

I've needed to modify my scripts to the equivalent of this to get around the issue:

ns = New Namespace();
ns:ns = New Namespace();
ns:ns << Delete Namespace();
Show( Is Namespace( ns:ns ) );
If( Is Namespace( ns:ns ) & !Is Missing( ns:ns << Get Name ),
	ns:ns:__item__ = 4;
);

 

Jordan
11 REPLIES 11

Re: Fatal JMP16 bug

Thanks very much for this information. A JMP developer has investigated and logged the issues you found so that they can be corrected in a future release!

hogi
Level XIII

Re: Fatal JMP16 bug

any update here?
sounds like a candidate for Tiny Traps in Jmp and JSL  ...

Recommended Articles