Hi,
I was wondering if this is expected behavior for active bindings in
attached environments, or if this is a bug:
> e <- new.env()
> makeActiveBinding('x',function() 'foo',e)
> ls(e)
[1] "x"
> attach(e)
> search()
[1] ".GlobalEnv""e" "package:graphics"
[4] "package:gr
Simon Urbanek wrote:
Jeff,
On Oct 1, 2009, at 12:37 , Jeff Horner wrote:
Jeff Horner wrote:
Martin Becker wrote:
Dear developers,
is it possible to create environments in C code of packages?
Simply using
SEXP env;
PROTECT (env = allocSExp(ENVSXP));
and assigning the enclosing environment
Jeff Horner wrote:
Martin Becker wrote:
Dear developers,
is it possible to create environments in C code of packages?
Simply using
SEXP env;
PROTECT (env = allocSExp(ENVSXP));
and assigning the enclosing environment with SET_ENCLOS seems to be
insufficient.
Best wishes,
Here
Martin Becker wrote:
Dear developers,
is it possible to create environments in C code of packages?
Simply using
SEXP env;
PROTECT (env = allocSExp(ENVSXP));
and assigning the enclosing environment with SET_ENCLOS seems to be
insufficient.
Best wishes,
Here's a function I use in rapache t
Simon Urbanek wrote:
[...]
I don't have konqueror at hand, so I have tested and fixed the lynx case
(lynx is acting as an HTTP/1.0 client and expects non-persistent
connection). With some luck the fix may solve the konqueror issue as
well (although I'd be a bit surprised if konqueror was not 1.