Re: SWITCH question
- Posted by irv Jan 07, 2018
- 1913 views
...
I'm not sure what's going on with cos(0), but with map:new() and stack:new() we're calling delete_routine() before returning the integer.
So, for complex reasons we're storing this integer value internally as an atom (with the full eu atom struct, etc) just so we can attach the delete_routine routine_id to it. We call this autopromotion.
http://openeuphoria.org/forum/m/121848.wc
The fact that it's an atom on the inside, even though it looks like an integer when you print it out or test it with integer(), is probably what's making it break here.
There's a ticket for this. http://openeuphoria.org/ticket/963.wc
If the object is deleted, then it's obvious why there is a sig fault. But is there anything that can prevent the deletion? If not, then we just have to live with limited capability for the switch statement, and need to spell that out in the docs.
And secondly, does the eu.ex interpreter also delete the objects, or are they kept around? See post 55
