| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
so the same parser generator can be uses for cifs and rpc
|
| | |
|
| | |
|
| |
|
|
| |
more conversion from idl to .struct of srvsvc
|
| | |
|
| | |
|
| |
|
|
|
| |
this now gives us enough to parse complete function calls, including
the return values
|
| |
|
|
|
| |
we can now handle arrays of structures, pointers to structures,
pointers in unions etc
|
| | |
|
| |
|
|
|
|
|
|
|
| |
now handles recursive function definitions, unions etc
it is sufficient for some basic types like UNISTR2 and BUFFER5
to be defined in the *.struct file and used successfully
this generator uses templates (in *.tpl files) for all code
generation, allowing easy replacement of the backend functions
|
| |
|
|
| |
added a couple of sample .prs files
|
|
|
it was sufficient to generate info level 6 of the add printer driver
for spoolss
It has two capabilities:
1) generate the header and C code for parsing a structure, given a
*.struct file that describes the structure. Evetually I hope to
make *.struct compatible with MIDL.
2) it provides a harness that can read a binary data file from
prs_dump() which contains real data from a client and display the
parse of it from the output of the awk parser. This allows you to
"play" with the structure definition until it comes out right, it
takes just a few mimutes of playing with the .struct file to work
out the right layout.
all this is very primitive right now. I hope next to completely
replace the spoolss parser with a single .struct file that describes
all the structures, and auto-generates working code. That will require
quite a bit more work.
|
