Community
Participate
Working Groups
Build Identifier: Xpand SDK 1.0.0.v201006150611 The generation of whitespaces / linebreaks can be controlled by adding a minus sign just before any closing bracket. The syntax highlighting marks the rest of the file as comment if this is applied to the tag <<ENDREM>>. Reproducible: Always
Created attachment 176367 [details] screenshot that shows the wrong highlighting
Created attachment 191201 [details] fixes the syntaxHighlighting this patch fixes the syntaxHighlighting The problem was, that two multiLineRules with the same startSeqence (REM) but with different endSequences were added to the XpandPartitionScanner. But on evaluating the rules the first rule which matches the startSequence will be evaluated and followers will not be evaluated. So I introduced a MultiLineMultiEndSequenceRule for the XpandPartitionScanner which can evaluate rules with one startSequence and one or more endSequences like ENDREM and ENDREM-.
Created attachment 191202 [details] fixes the completionProposals this fixes the completionProposals in following partitions of comments ending with ENDREM-
There is still a problem with the parser! The "-" will not be recognized, so it is marked as a "mismatched input" error. In this case the grammar has to be expanded!
*** Bug 331930 has been marked as a duplicate of this bug. ***
The patch does not work properly, but it directed to the right location. The MultiLineRule in XpandPartitionScanner needs to detect the situation that a '-' character is at the position where the closing bracket is expected. By overriding MultiLineRule#sequenceDetected this could be accomplished. In the grammar the optional '-' character has to be added to the closing token: COMMENT : 'REM' RG ( options {greedy=false;} : . )* '\u00ABENDREM' '-'? ;
changeset 7551ba7b0f79ed8e4661f2d21e365488709905cc db5c8e077dfadfae2e0528fe5a98a1a27cbd62ec
Requested via bug 522520. -M.
