excellent! now i can get rid of that silly no-op bytecode i've been
using. thanks for the quick turnaround, leo.
-jeff
On Thu, 5 May 2005, Leopold Toetsch wrote:
> Jeff Horwitz wrote:
> > i'm neck deep in writing the IMC eval code for pugs. ...
>
> > ... but i imagine there's a more
> > elegan
Jeff Horwitz wrote:
i'm neck deep in writing the IMC eval code for pugs. ...
... but i imagine there's a more
elegant solution out there.
t/src/compiler.t has now all the steps to run a PIR code string from C.
It's not elegant though, because there are no APIs, but it should make
things running.
Jeff Horwitz wrote:
i'm neck deep in writing the IMC eval code for pugs. if i've already
loaded bytecode using Parrot_readbc/loadbc, i can then successfully call
the PIR compiler and eval code at will from C/Haskell. great!
however, without the Parrot_readbc step, everything bombs out because the
i'm neck deep in writing the IMC eval code for pugs. if i've already
loaded bytecode using Parrot_readbc/loadbc, i can then successfully call
the PIR compiler and eval code at will from C/Haskell. great!
however, without the Parrot_readbc step, everything bombs out because the
packfile isn't set
