Uri Guttman can see a day where:
> python and ruby, etc. are
> defaulting to using the parrot back end as it will be faster, and
> compatible with perl etc. imagine the work reduction if all/most of the
> interpreted languages can share one common back end.
What about the compiled ones? Did we consider and reject GCC back end
for reasons beyond "not-devloped-here?"
Inline.pm syntax is fully upgradable to a native back end instead
of invoking external compilers, of course.
--
David Nicol 816.235.1187
.sig file closed by executive order
