On 31.10.2012 21:15, Taras Glek wrote:
Actually one big reason that dehydra failed is that spidermonkey became
a lot harder to embed due to increased churn(new jits landing, etc). So
I strongly advice against wasting time on it. Certain other JS JIT
engines have much more stable APIs(but much crappier JS, eg lack of
generators makes dehydra less fun). Python has the benefit of maturity +
shipping with generators, comprehensions, lambdas which make it much
better suited than various JS implementations for this.
The other thing to note is that the best way to do something like
dehydra is to build it as a highlevel wrapper on top of a lower level
api like python-gcc. The only reason dehydra was implemented the way it
was is because it came first before lower-level AST compiler bindings
were shown to be practical.
Thank you for the clarification, Sorry about my superficial speculation.
@Klaus - another option for you is to walk your C++ in C++ using Clang
Matchers [1] (part of the emerging Clang Tooling framework)
Cheers,
Alek
[1] http://clang.llvm.org/doxygen/namespaceclang_1_1ast__matchers.html
_______________________________________________
dev-static-analysis mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-static-analysis
