Anyway, I created a new fill_pmc_args branch with my two or three lines of
work. The commit message for the one commit that makes that branch different
from the master also describes the limitations I'm aware of.
--
Joshua Tolley / eggyknap
End Point Corporation
http://www.endpoint.com
I have been informed by bacek++ on #parrot that we should use
VTABLE_push_string(interp, pmc);
Duke
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAkuq3I0ACgkQRiRfCGf1UMOFxQCePwVdlssB8Iiwmpl/s/C/IAu0
> ODwAoKO3EbNQfp2KlH9l5Towi+rb1B+C
> =KsiO
> -----END PGP SIGNATURE-----
>
>
--
Jonathan "Duke" Leto
jona...@leto.net
http://leto.net
ACTUALLY, never call VTABLE_* methods directly, or you will go blind.
We should be using Parrot_PMC_push_string from src/extend.c, which was
documented but unwritten. plobsing++ is writing as we speak right now.
This is why Parrot rocks.
Duke