Samples + Parser.cs

Apr 25, 2009 at 6:33 AM
Edited Apr 25, 2009 at 6:34 AM
This is a pretty cool project although Parser.cs in every sample look scary.

Why not use one of these libraries that can return an AST already?

example npeg can actually create a custom type .. not in the library using Activator.CreateInstance as long as it implements the correct interface to be added to the rest of the ast.
NPEG won't fluctuate any.  Terminals/NonTerminal there today will not change and project is completely unit tested.


Also in the documentation folder can you guys provide the references used to create the parsers?
Example where can i find complete documentation of the PE/PDB file format and IL?



Apr 25, 2009 at 4:56 PM
I appreciate that building a parser by hand is not for every one and that in many cases a generated parser is the better way to go. Unfortunately none of the current contributors to this project is like to get the time to write samples using irony or npeg any time soon. The seems like a good place for some-one else to step in and fill the gap. :-)

The format of PE files can be found on MSDN. Search for "portable executable file format" and "common language infrastructure". I do not know of any description of PDB files. If you find one, please let me know...