|
| Re: Update from 2.3 to 2.5: Old 64b problem occurs again [message #1220590 is a reply to message #1219875] |
Thu, 12 December 2013 11:11  |
Eclipse User |
|
|
|
Hi Ingo,
that's suprising to me. Could you share your grammar?
Best regards,
Sebastian
--
Looking for professional support for Xtext, Xtend or Eclipse Modeling?
Go visit: http://xtext.itemis.com
Am 06.12.13 14:01, schrieb Ingo Meyer:
> Hi,
>
> today I tested the new 2.5 Xtext version for the first time with our
> huge project.
> Unfortunaletly it was a short test as immediately the fuu error
> "The code for the static initializer is exceeding the 65535 bytes limit"
> occurs in the parser of the Xtext main bundle in the first splitted
> internal class "abstract class InternalMyParser1 extends
> AbstractInternalAntlrParser".
> Strangewise the ui bundle is ok.
> Same project under 2.3 runs fine.
>
> MWE file is:
>
> fragment = parser.antlr.XtextAntlrGeneratorFragment {
> options = {
> backtrack = true // enables infix operators
> memoize = true //
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=314935
>
> //
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=349992
> classSplitting = true // solves class file
> limits
> fieldsPerClass = "100" // lower number means
> more aggressive splitting, default was 1000
> methodsPerClass = "100" // lower number
> means more aggressive splitting, default was 5000
> }
> antlrParam = "-Xconversiontimeout"
> antlrParam = "60000"
> }
>
> fragment = parser.antlr.XtextAntlrUiGeneratorFragment {
> options = {
> backtrack = true // enables infix operators
> memoize = true //
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=314935
>
> //
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=349992
> classSplitting = true // solves class file
> limits
> fieldsPerClass = "100" // lower number means
> more aggressive splitting, default was 1000
> methodsPerClass = "100" // lower number
> means more aggressive splitting, default was 5000
> }
> antlrParam = "-Xconversiontimeout"
> antlrParam = "60000"
> }
>
> (Please no comments about backtracking... We need that! :( )
>
> For me this is a project stopper as we can do nothing more to solve that.
> So anybode an idea?
> Any news from ANTLR about that, or is that an Xtext problem?
>
> Many thanks for any help,
>
> Ingo
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03700 seconds
Home
)