Line 1: Syntax Error: Expecting the following tokens: LEFTPARRANGE and ASSIGN tokens are recognized, but LEFTPAR not although it is there.
Line 1: Lexical Error: Cannot recognize token: s
The compiled grammars from 5.2 do not always work correctly. Compiled grammars from 1.0 do.I didn't know that. :o I do not have a 1.0 but I do have an old 3.0.1. I will try and report back.
I will try to analyze the problem. Can you attach a cgt?Of course. Thanks a lot for looking into this problem. :)
You were right. Old version 3.0.1 runs better, although with some quircks.The compiled grammars from 5.2 do not always work correctly. Compiled grammars from 1.0 do.I didn't know that. :o I do not have a 1.0 but I do have an old 3.0.1. I will try and report back.
Line 1: Syntax Error: Expecting the following tokens: LEFTPAR
I have tested my FCL grammar with 3.0.1 and GoldEngine and it works. I haven't yet figured out exact rule for appending some whitespace character at the end of the line (or file?) to overcome the mentioned bug but hopefully that will be sorted out. So, now I have a work around and will continue to invest time in Gold Parser, being it 3.0.1 or 5.20. Whatever.I am also translating Coco /R to be Freepascal/Lazarus compatible. Almost finished except for two assembler routines that I have to change to Pascal. Code already works for Windows32/64
Thank you Thaddy !!! 8) ;) 8)
Btw. I have to correct my self and say that 3.0.1 supports comment groups. Only comment attributes are not supported. Meaning, this is not compatible with 3.01:Good enough for me! ::)
Comment Block @= { Nesting = All, Advance = Character }
I am also translating Coco /R to be Freepascal/Lazarus compatible.I looked at Coco/R and Antlr for Delphi but they just didn't "click" for me. Gold, plex/pyacc and Lazarus Lex&Yacc are more to my taste. If you ever decide to try improving GoldEngine compatibility with Gold 5.2.0 then give me a note and I will help as much as possible. I have tried to dig into it myself but that didn't go well.
thank you for the feedback.You're most welcome ;)
Avra, thanks for the link. Saves me lot's of work, It looks fine code, but there is some room to improve. I will suggest some pulls.You're welcome. I also have some ideas for improvement.