[codenameone-discussions] Re: IOS builds failing: error unexpected statement
An interesting bit about this "statement expected" error. I've been
generating my own builds, and out of a few dozen builds that
I got as far as feeding to xcode, TWO so far have failed due to this.
Since I was watching for it, I re-ran the identical build and
the error did not repeat.The errant label seems to be a free floating
label, inserted randomly at the end of a method. Everything
else about the file looks well-formed.
So, based on this evidence, theories involving resource exhaustion, rogue
processes and other bolts from the blue
are less likely.
> JAVA_VOID
> com_codename1_ui_Display_invokeAndBlock___java_lang_Runnable_boolean(CODENAME_ONE_THREAD_STATE,
>
> JAVA_OBJECT __cn1ThisObject, JAVA_OBJECT __cn1Arg1, JAVA_BOOLEAN
> __cn1Arg2) {
> volatile JAVA_INT ilocals_2_ = 0; /* dropEvents */
> DEFINE_INSTANCE_METHOD_STACK(4, 7, 0, 2603, 2629);
> locals[0].data.o = __cn1ThisObject; locals[0].type =
> CN1_TYPE_OBJECT; locals[1].data.o = __cn1Arg1;
> locals[1].type = CN1_TYPE_OBJECT;
> ...
>
label_L1075083982: END_TRY();
> __CN1_DEBUG_INFO(1230);
> BC_ASTORE(6);
> __CN1_DEBUG_INFO(1231);
> set_field_com_codename1_ui_Display_dropEvents(threadStateData, 0 /*
> ICONST_0 */, __cn1ThisObject);
> __CN1_DEBUG_INFO(1232);
> BC_ALOAD(6);
> throwException(threadStateData, POP_OBJ());
>
> label_L986065593:
> __CN1_DEBUG_INFO(1231);
> set_field_com_codename1_ui_Display_dropEvents(threadStateData, 0 /*
> ICONST_0 */, __cn1ThisObject);
> __CN1_DEBUG_INFO(1233);
> releaseForReturnInException(threadStateData, cn1LocalsBeginInThread,
> methodBlockOffset);
> return;
>
> label_L590511187:
> }
>
>
>
--
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 codenameone-discussions+unsubscr...@googlegroups.com.
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/900f304a-6035-497f-803e-c2279f63c7c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[codenameone-discussions] Re: IOS builds failing: error unexpected statement
It would slow things down. If we do that this would mean we would need to compile and link the whole class library without stripping anything until link stage. This will balloon the result especially if a user clicks include source. Since more time is spent uploading/downloading than compiling for many users this would slow down almost all apps including yours. Try a typical app, even a large one, builds take 3 - 5 minute for iOS assuming no queuing -- 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 codenameone-discussions+unsubscr...@googlegroups.com. 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/ef782a1b-433a-4971-b684-a50fc937156f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[codenameone-discussions] Re: IOS builds failing: error unexpected statement
There are definitely some things you could do that are not too difficult or drastic. Segregating the published APIs from the used APIs for the classes you compile would result in a huge speedup with change in the result, and it would be self-checking; if you didn't get it right then your compiles would break. -- 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 codenameone-discussions+unsubscr...@googlegroups.com. 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/3235d87c-c9dd-4067-8179-92124e4fbbb6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[codenameone-discussions] Re: IOS builds failing: error unexpected statement
Java doesn't support AoT modularity and doesn't support it at all at the current release anyway. Java wasn't designed for modern mobile devices either... -- 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 codenameone-discussions+unsubscr...@googlegroups.com. 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/f04359fd-4cd0-44a3-85fe-8b34877a0729%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[codenameone-discussions] Re: IOS builds failing: error unexpected statement
I'm afraid that breaking my app into 75 separate game apps would be a terrible idea and not a net saving of my time or an improvement of the user experience. It's a shame that codenameone doesn't support any kind of modularity (as java does) that would permit me to rebuild only the parts that change. But I understand that would be hard. -- 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 codenameone-discussions+unsubscr...@googlegroups.com. 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/36fad2c3-797a-416b-bcea-2c6dc52e0993%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[codenameone-discussions] Re: IOS builds failing: error unexpected statement
As fragile as your build process is, you really ought to have 24 hour coverage. I'm currently on the 4'th attempted build. If nothing else, these crapped-out builds cause your server load to be much higher than it ought to be. . -- 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 codenameone-discussions+unsubscr...@googlegroups.com. 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/2d01612e-bf2e-43de-a756-76a1ba72c54b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[codenameone-discussions] Re: IOS builds failing: error unexpected statement
Nope, we are all offsite so no one touched anything to trigger or fix the issue. We haven't touched the translation code in a while. I'll login to the servers and peek around. -- 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 codenameone-discussions+unsubscr...@googlegroups.com. 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/8cd04d50-de6f-41c1-b13e-666dd2ec6fcd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[codenameone-discussions] Re: IOS builds failing: error unexpected statement
This repeated 3 times, but the fourth attempt at the same build succeeded. I'd feel better about this if you told me there was a problem you understand and fixed. -- 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 codenameone-discussions+unsubscr...@googlegroups.com. 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/9bd50cc7-f40a-42b0-9f5e-6fcff5e24964%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
