On Fri, 21 Sep 2001, Pedroni Samuele wrote:
> I don't know if you are aware of that, but the Parrot VM
> both has instructions that deal with static typed data
> integers (IV?) , floats (NV?) and strings (STRING)
> so you can't delay the problem of a string library
> to the dynamic typed stuff (PMCs) like in Python
> But clearly the PMCs and how to implement
> python runtime and semantics through them
> and how easy is "our" problem.
> A "Parrot Python String" will not be a STRING
> but given there are STRINGs it should be
> decided how they work...
Some thought I had on this topic...:
Compiling Python and Ruby source-code to Parrot byte-code won't ever
generate any integer-specific, string-specific, or float-specific opcodes,
except to the extent required by the implementation of Python's and Ruby's
object systems in Parrot. (and also except if someone writes a really good
optimiser.)
Python's and Ruby's ideas of what are Integers, Floats and Strings would
have to be implemented directly in the Parrot assembly language to take
advantage of those bytecodes (and therefore of interoperability with
Perl).
________________________________________________________________
Mathieu Bouchard http://hostname.2y.net/~matju
