Changing file-extension for standalone grammar definitions from .g?

Currently standalone files like common and the example json use the file extension .g. However, it looks like g is already associated with the ANTLR parser. While I suppose it’s possible to make Lark compatible with ANTLR, in the meantime it’s probably best to use a different file extension. I would propose the extension lrk as it doesn’t seem to be used by anything currently.

I’m about to submit a pull request to change the file extensions to .lrk in the relevant file names and in the code referencing the .g extension. It’s on a separate branch so if you want to use a different extension that should be easy enough to change.

[erezsh]

@dirk-thomas @RobRoseKnows Fantastic! If you have these 3 covered, I can do vscode. And I don’t mind bumping to 0.6.0 soon. There are other breaking changes I’m looking to make, so it could be a good opportunity.

Also, I noticed that although the grammar is similar to ANTLR, It’s also very similar… to Perl !

• Perl has both “strings” and /regexps/i

• Perl also differentiates between lowercase and UPPERCASE

And all editors have it. So perhaps you can use the perl syntax file for some quick-and-easy copy pastes.

Anyway, write them in your free time, and I’ll add them to the README. When they’re all done, I’ll bump the version and update the docs.

P.S. I gave it some thought, and I think .lark is the best choice. It’s clear, simple, and google-able.

Cheers, Erez

[erezsh]

Merged.