Function arguments

0 views
Skip to first unread message

Joshua Tolley

unread,
Mar 24, 2010, 11:46:21 PM3/24/10
to plpa...@googlegroups.com
I sat down today fully intending to get arguments stuck in the new
ResizablePMCArray dukeleto coded the other day, and realized I've no idea how
to do it. I think I've found the necessary functions, but they're 1) not
linked in, and 2) not declared, and trying to include the necessary header
causes the same sorts of errors as when including parrot.h.

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

signature.asc

Jonathan Leto

unread,
Mar 25, 2010, 5:08:56 PM3/25/10
to plpa...@googlegroups.com
Howdy,

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

Jonathan Leto

unread,
Mar 25, 2010, 5:13:39 PM3/25/10
to plpa...@googlegroups.com
Howdy,

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

Reply all
Reply to author
Forward
0 new messages