[codenameone-discussions] Re: IOS builds failing: error unexpected statement

2017-04-26 Thread Dave Dyer
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

[codenameone-discussions] Re: IOS builds failing: error unexpected statement

2016-10-16 Thread Shai Almog
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

[codenameone-discussions] Re: IOS builds failing: error unexpected statement

2016-10-16 Thread Dave Dyer
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

[codenameone-discussions] Re: IOS builds failing: error unexpected statement

2016-10-13 Thread Shai Almog
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

[codenameone-discussions] Re: IOS builds failing: error unexpected statement

2016-10-12 Thread Dave Dyer
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

[codenameone-discussions] Re: IOS builds failing: error unexpected statement

2016-10-12 Thread Dave Dyer
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

[codenameone-discussions] Re: IOS builds failing: error unexpected statement

2016-10-11 Thread Shai Almog
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

[codenameone-discussions] Re: IOS builds failing: error unexpected statement

2016-10-11 Thread Dave Dyer
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