Pippijn van Steenhoven wrote:
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.
Yeah I'd rather not add any explicit support for Perl. The language is
going the way of the dodo. But a more general way to generate bindings
for perl/python bindings would be welcome.
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:
No,
http://blog.mozilla.com/cjones/2009/08/04/introducing-porky-py-low-fat-pork/
1. restructure source tree, use autotools
Note Chris Jones mentioned that he might want to try moving to a more
modern system such as scons.
2. remove smbase string
3. remove other smbase ADTs and use std:: ones
4. remove even more smbase ADTs and use boost:: ones
No boost. I might accept one or two useful classes from boost, but no
more than that.
5. remove some unused or unneeded parts of elsa (they have some weird
macro support I don't think actually works)
I wrote it, it mostly works pretty well. It's certainly not useless as
it's the only way we can use elsa.
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
I'd agree with you on this, I hate elsa's xml support and think it's
useless. I don't think anyone other than Joshua got it to be even
remotely useful.
7. add (intrusive) perl support to elsa's AST
Like I said: no perl-specific stuff in elsa.
8. rewrite the deparser in perl and remove it from the C++ code
what's deparser?
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.
Indeed. I like most of your changes, so we can start working the ones we
agree with(1-3) and go from there.
Taras
_______________________________________________
dev-static-analysis mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-static-analysis
