I've been tracking down a hard crash, which apparently is unrelated to the
unsequenced modification warnings.
https://github.com/codenameone/CodenameOne/issues/1911
It's unclear exactly what the doomsday code is, but at least my test case
is simple
My eye is drawn to this bit
PUSH_INT(11);
SP-=2; if((*SP).data.i >= SP[1].data.i) /* IF_ICMPGE */ goto
label_L1821402884;
PUSH_POINTER(get_field_euphoria_EuphoriaBoard_allegiance(__cn1ThisObject));
(*SP).type = CN1_TYPE_INT; /* ILOAD */
(*SP).data.i = ilocals_3_;
SP++;
Decrementing SP and then using SP[1] looks like a violation of good
practice, even if
it's supposed to be OK "in this case" because there's no possible
interruption.
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
Visit this group at https://groups.google.com/group/codenameone-discussions.
To view this discussion on the web visit
https://groups.google.com/d/msgid/codenameone-discussions/7190a9c0-1c67-4ada-a8da-19e642568f8b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
