To answer my own question: Yes, it will explode. I was just getting
lucky. Right, back to the drawing board :-)
On Jul 22, 2005, at 6:07 PM, Byron Ellis wrote:
> I'm not sure I understand here... If I do, say...
>
> setClass("id","externalptr")
>
> where classes of that type come back from, eff
I'm not sure I understand here... If I do, say...
setClass("id","externalptr")
where classes of that type come back from, effectively, C functions
that do something like
PROTECT(ret = NEW_OBJECT(MAKE_CLASS("id")));
R_SetExternalPtrAddr(ret,myid);
UNPROTECT(1);
return ret;
am I just asking for
Paul Roebuck wrote:
> On Wed, 20 Jul 2005, John Chambers wrote:
>
>
>>Paul Roebuck wrote:
>>
>>
>>>Is it possible for S4 to (continue) dispatch to a class
>>>created during dispatching? The code below doesn't work;
>>>is this not possible or have I ommitted something?
>>
>>"doesn't work"? This i
On Wed, 20 Jul 2005, John Chambers wrote:
> Paul Roebuck wrote:
>
> > Is it possible for S4 to (continue) dispatch to a class
> > created during dispatching? The code below doesn't work;
> > is this not possible or have I ommitted something?
>
> "doesn't work"? This is not helpful. Please show w
Paul Roebuck wrote:
> Is it possible for S4 to (continue) dispatch to a class
> created during dispatching? The code below doesn't work;
> is this not possible or have I ommitted something?
"doesn't work"? This is not helpful. Please show what you got and what
you expected. The result below is
Is it possible for S4 to (continue) dispatch to a class
created during dispatching? The code below doesn't work;
is this not possible or have I ommitted something?
Concept was to create a SEXP with R_AllocatePtr, give it
a class attribute, and continue dispatch. Example code
below omits multiple p
