As I've been working on the vim-gopeg plugin (which has a notion of regions) I noticed that the peg.peg only really looks for package and import as keywords and doesn't really consider everything before the grammar as a sort of pre-amble (which would have helped earlier had I known I could not use standard import () syntax because of that).
What I'm proposing for discussion is a new peg.peg that separates the the grammar into two main components, or perhaps just an initial component Preamble (or whatever) followed but what is there now.
Then, the Preamble would be set to contain exactly the same syntax GoCode with modification to support things like # for comments and such. The Go AST and parser is readily available to derive that grammar. (By the way, why the Java, C and other grammer pegs and not one for Go itself? wink).
One side-effect is that we could change ActionBody (which I think has a bug) to be GoCode or something like that.
In fact, if we do this we get full Go syntax checking as well as PEG grammar checking.
It would also make the vim-gopeg plugin a lot easier to do because this stuff is very similar.
Please let me know if this is a path worse pursuing and if so I wouldn't mind working on it.
As I've been working on the vim-gopeg plugin (which has a notion of regions) I noticed that the
peg.pegonly really looks forpackageandimportas keywords and doesn't really consider everything before the grammar as a sort of pre-amble (which would have helped earlier had I known I could not use standardimport ()syntax because of that).What I'm proposing for discussion is a new
peg.pegthat separates the the grammar into two main components, or perhaps just an initial componentPreamble(or whatever) followed but what is there now.Then, the
Preamblewould be set to contain exactly the same syntax GoCode with modification to support things like#for comments and such. The Go AST and parser is readily available to derive that grammar. (By the way, why the Java, C and other grammer pegs and not one for Go itself? wink).One side-effect is that we could change
ActionBody(which I think has a bug) to beGoCodeor something like that.In fact, if we do this we get full Go syntax checking as well as PEG grammar checking.
It would also make the
vim-gopegplugin a lot easier to do because this stuff is very similar.Please let me know if this is a path worse pursuing and if so I wouldn't mind working on it.