Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » TMF (Xtext) » The code of method ... is exceeding the 65535 bytes limit
The code of method ... is exceeding the 65535 bytes limit [message #555054] Wed, 25 August 2010 10:22 Go to next message
F. Alexander Njemz is currently offline F. Alexander NjemzFriend
Messages: 20
Registered: July 2010
Junior Member
Hi,

The error occurs in the parser generated by Xtext.
I searched around the forums and found out about
the classSplitting option.
Even though de.itemis.xtext.antlr.ex.rt.AntlrGeneratorFragment
is inaccessible it seems Xtext 'knows' about the
classSplitting option, however I'm still getting the error.
Any help?
Thanks.

Regards,

Alexander
Re: The code of method ... is exceeding the 65535 bytes limit [message #555081 is a reply to message #555054] Wed, 25 August 2010 12:06 Go to previous messageGo to next message
Meinte Boersma is currently offline Meinte BoersmaFriend
Messages: 434
Registered: July 2009
Location: Leiden, Netherlands
Senior Member
What do you mean, that "de.itemis.xtext.antlr.ex.rt.AntlrGeneratorFragment
is inaccessible"?

That class inherits from org.eclipse.xtext.generator.parser.antlr.ex.rt.AntlrGenerato rFragment without adding anything to it (the getTemplate method is overridden to provide the same result as super.getTemplate) and is flagged deprecated. So, in any case you wouldn't need it.


Re: The code of method ... is exceeding the 65535 bytes limit [message #555126 is a reply to message #555081] Wed, 25 August 2010 14:07 Go to previous messageGo to next message
F. Alexander Njemz is currently offline F. Alexander NjemzFriend
Messages: 20
Registered: July 2010
Junior Member
By 'inaccessible' I meant, that I wasn't able to reference it inside the workflow file.

The error went away after I modified the grammar a little.
But still, is classSplitting supported by the default
fragment parser.antlr.XtextAntlrGeneratorFragment?
Or would one need to change it to
parser.antlr.ex.rt.AntlrGeneratorFragment?

Thanks.
Re: The code of method ... is exceeding the 65535 bytes limit [message #555132 is a reply to message #555126] Wed, 25 August 2010 14:13 Go to previous messageGo to next message
Sebastian Zarnekow is currently offline Sebastian ZarnekowFriend
Messages: 3118
Registered: July 2009
Senior Member
Hi Alexander,

class splitting is supported by each Antlr fragment. Please keep in
minde that the workflow contains two fragments that generate antlr
parsers. You have to enable it for both of them.

Regards,
Sebastian
--
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com

Am 25.08.10 16:07, schrieb Alexander:
> By 'inaccessible' I meant, that I wasn't able to reference it inside the
> workflow file.
> The error went away after I modified the grammar a little.
> But still, is classSplitting supported by the default
> fragment parser.antlr.XtextAntlrGeneratorFragment?
> Or would one need to change it to
> parser.antlr.ex.rt.AntlrGeneratorFragment?
>
> Thanks.
Re: The code of method ... is exceeding the 65535 bytes limit [message #555134 is a reply to message #555126] Wed, 25 August 2010 14:34 Go to previous message
Meinte Boersma is currently offline Meinte BoersmaFriend
Messages: 434
Registered: July 2009
Location: Leiden, Netherlands
Senior Member
classSplitting should be supported (equally) by both, since they both inherit from org.eclipse.xtext.generator.parser.antlr.AbstractAntlrGenera torFragment which allows to set the options which is an instance of org.eclipse.xtext.generator.parser.antlr.AntlrOptions and the boolean property is checked in AbstractAntlrGeneratorFragment#splitParserAndLexerIfEnabled (and only there).


Previous Topic:Extraction to multiple files
Next Topic:XText nature icon cannot be superseded
Goto Forum:
  


Current Time: Thu Mar 28 13:22:58 GMT 2024

Powered by FUDForum. Page generated in 0.03569 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top