From: Sebastian Redl (sebastian.redl_at_[hidden])
Date: 2006-02-04 05:42:52
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.
If it produces bytecode, you again need an interpreter, but the native
call interface might still be unportable.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk