What about allocSExp(ENVSXP)? Then SET_ENCLOS() to set the parent? Seems to
work for me.
Michael
On Sun, Aug 29, 2010 at 11:02 AM, Oliver Flasch
wrote:
> Hi,
>
> as Seth Falcon in 2006, I also need to create new environments from package
> C code. Unfortunately, both NewEnvironment and R_NewHash
Hi,
as Seth Falcon in 2006, I also need to create new environments from package C
code. Unfortunately, both NewEnvironment and R_NewHashedEnv are not yet part of
the public API, if I understand correctly.
Is it planned to add at least one of these functions to the public API in the
near future
On Wed, 15 Nov 2006, Seth Falcon wrote:
> Prof Brian Ripley <[EMAIL PROTECTED]> writes:
>> NewEnvironment is currently exposed as Rf_NewEnvironment.
>> R_NewHashedEnv is currrently hidden, but I'll unhide it. It does not
>> need a further prefix.
>
> Thank you. Could someone provide a bit more d
Prof Brian Ripley <[EMAIL PROTECTED]> writes:
> NewEnvironment is currently exposed as Rf_NewEnvironment.
> R_NewHashedEnv is currrently hidden, but I'll unhide it. It does not
> need a further prefix.
Thank you. Could someone provide a bit more detail on how to
determine if a given function in
On Tue, 14 Nov 2006, Seth Falcon wrote:
> Hi,
>
> I would like to be able to create new environments from package C
> code. AFAICT, this isn't allowed since both NewEnvironment and
> R_NewHashedEnv are declared in Defn.R.
NewEnvironment is currently exposed as Rf_NewEnvironment.
R_NewHashedEnv i
Hi,
I would like to be able to create new environments from package C
code. AFAICT, this isn't allowed since both NewEnvironment and
R_NewHashedEnv are declared in Defn.R.
If exposing this isn't controvertial, I would submit a patch.
However, I'm not sure where the declarations should go (Rdefin