4 Feb
2006
4 Feb
'06
1:11 p.m.
Sebastian Redl wrote:
Stefan Seefeld wrote:
I'm not quite sure what 'inherent' portability issues you anticipate. The framework is written in (std) C++ and python, and the parser itself in pure C++.
The inherent portability issues lie at the very end of the back-end, in the code generation. If it is to produce native code, it's unportable.
Ah, obviously. I'm only talking about source-to-source translation and other introspection use cases, which 'only' require a front-end. Regards, Stefan