On Tue, 21 May 2002 12:18:50 -0400, Dan Sugalski wrote:
> At 8:44 AM -0500 5/20/02, brian wheeler wrote:
> >I've been trying to catch up with parrot again (darn it, babies take more
> >time than I thought :) and I've come up with a question... how do you do
> >"other" things to PMCs that aren't normal ops?
>
> Call methods on the perl-level classes that map to the PMCs.
What if the functionality required isn't available through any number
of vtable method calls? Is this what user/language defined ops are for,
or do even more vtable methods have to be defined? If the latter, where
do we stop?
> >In particular, I was wondering about shift/unshift, push/pop on the
> >PerlArray PMC. Am I missing something obvious?
>
> Ah, those. In that case you use the vtable methods I've forgotten. :)
Will these all map to a splice vtable method, or will there be a
method for each?
--
Peter Haworth [EMAIL PROTECTED]
"I defy you to use the documentation to understand ... the ANSI C++ draft
standard. It's not for nothing that comp.lang.std.c++ has a FAQ sixteen
times the thickness of the Hong Kong phone book." -- Felix Gallo
