Gregory Shrago

Created March 05, 2013 15:02

Grammar-Kit supports left recursion in one special case: Pratt-like expression parsing.Here's an example: https://github.com/JetBrains/Grammar-Kit/blob/master/testData/generator/ExprParser.bnfAnoth...

1. Community
2. IntelliJ IDEA Open API and Plugin Development
3. Starting point for a Java-like grammar for Grammar-Kit?

• 0 votes

Created March 07, 2013 23:21

I'm interested in fixing any problems with Live Preview so you can send me anything to reproduce the problem (email or github). It will be fixed.

1. Community
2. IntelliJ IDEA Open API and Plugin Development
3. Starting point for a Java-like grammar for Grammar-Kit?

• 0 votes

Created June 03, 2013 17:55

In order to simplify this apublic DataSource.getConnection(Project)method is added to IDEA 13 and IDEA 12.1.X codebases.

1. Community
2. IntelliJ IDEA Open API and Plugin Development
3. Can I access and use the IDEA Data Sources?

• 0 votes

Created December 18, 2012 14:40

Any SQL dialect uses generated + handwritten lexers approach.So you can hack OracleLexer or even SqlLexer class instead. ;-)I've added "." as allowed character so your case will be covered.Expect t...

1. Community
2. IntelliJ IDEA Open API and Plugin Development
3. Extend SQL dialect?

• 0 votes

Created September 27, 2013 17:56

Dear Terence,We do care in fact. Unfortunately sometimes it is hard to help without the ability to really reproduce the problem.The AbstratTreeUi you mentioned is a very complicated piece of code w...

1. Community
2. IntelliJ IDEA Open API and Plugin Development
3. Suggestions for tracking down a null pointer exception?

• 0 votes

Created October 21, 2013 14:48

There's no need to repeat the work of other authors. One can read about PEG and IntelliJ parsing architecture somewhere else and then discover Grammar-Kit which just combines all the above.https://...

1. Community
2. IntelliJ IDEA Open API and Plugin Development
3. Grammar kit tutorial(s)

• 0 votes

Created October 24, 2013 23:23

There're different levels of problem reporting: lexer errors, parser errors and annotators/inspections reports.String literal contents related problems belong to 1.lexer level or 2.semantic level, ...

1. Community
2. IntelliJ IDEA Open API and Plugin Development
3. Parsing strings and other various basic types

• 0 votes

Created December 03, 2013 12:04

I've checked the plugin sources on github. Not sure (I haven't run them) but..PsiErrorElements are created when PsiBuilder.error() or PsiBuilder.Marker.error() methods are used. The difference is t...

1. Community
2. IntelliJ IDEA Open API and Plugin Development
3. error squiggly red underline off-by-one in parser

• 0 votes

Created January 08, 2014 13:44

You need an Annotator for that.Here's the explanation: Syntax Highlighting and Error Highlighting

1. Community
2. IntelliJ IDEA Open API and Plugin Development
3. BNF Rule Syntax Highlighting for Custom Language

• 0 votes

Created January 28, 2014 13:40

You seem to put too much of syntax logic into your lexer.IntelliJ IDEA platform assumes lexers are fast and uses them very often.Solution: decouple lexer & parser logic as it is usually done: Make ...

1. Community
2. IntelliJ IDEA Open API and Plugin Development
3. Problems with performance in custom language plugin

• 0 votes