Hi, On Saturday 10 March 2012, meik michalke wrote: > is this solvable at all?
yes, but it will be somewhat difficult to do this cleanly.
One pretty reliable way of telling whether the code is really, really running
in an rkward session is
is.loaded("rk.do.generic.request")
So it would be possible to simply test for that condition inside rkward::q(),
and call base::q(), if it is not met. In fact, I guess for q(), adding this
check is really a good idea. (While at it, it might also make sense to add a
similar check to .onAttach(), and issue a warning, when loading the package
outside an rkward session).
It may be tempting to add this test to .rk.do.plain.call(), which would cover
most uses of .Call() in rkward. However, I'm not sure about the performance
implications of this (I have not done measurements).
> spontanously, the only way i can think of would be
> some sort of marker like an object value in the package namespace, to
> indicate whether the package was loaded by a starting RKWard session or
> not. it could then be checked by RKWard's q()/quit() functions.
Or simply add it as a function:
rk.inside.rkward.session() <- is.loaded("rk.do.generic.request")
Regards
Thomas
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________ RKWard-devel mailing list RKWard-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkward-devel
