Hi, I am going to do some work on the elsa parser. First, I will get rid of a lot of smbase (string, some ADTs). Then I would like to remove anything not needed for pork. Then, I would like to have perl bindings (maybe python bindings) directly into the AST and build some tools with that. I would also like to rewrite the deparser (pretty printer) in a scripting language. For that, I would like to add intrusive support for perl. Before I do all that, I want to restructure the source tree and use automake, autoconf and libtool.
Now: what is the stuff in porky/parser.py and porky/parser.py? Are you
trying to write a C++ parser in python? I hope not.. Anyway, I would like
to give you some of my changes (all, if you want them, but that is
unlikely), so I will do them in the following order:
1. restructure source tree, use autotools
2. remove smbase string
3. remove other smbase ADTs and use std:: ones
4. remove even more smbase ADTs and use boost:: ones
5. remove some unused or unneeded parts of elsa (they have some weird
macro support I don't think actually works)
6. remove XML in/output from elsa (yes, it's nice, but it's for the
best and can easily be replaced by "my $xml = XMLout($ast)" after
integrating elsa with perl
7. add (intrusive) perl support to elsa's AST
8. rewrite the deparser in perl and remove it from the C++ code
and then I'll just go on and do nice (for me) things with it such as
creating a binding to a backend I am working on at the moment.
Since I am working on said backend and this is not fully functional, yet,
you will have a lot of time to think about it, also because I seem to be
having a minor RSI problem. Please tell me what parts (if any) you would
like to have from my development. It would be nice if we could work
together.
Regards,
--
Pippijn van Steenhoven
signature.asc
Description: Digital signature
_______________________________________________ dev-static-analysis mailing list [email protected] https://lists.mozilla.org/listinfo/dev-static-analysis
