Thanks Romain for that elegant solution.
Best,
Gregor
On Wed, 22 Jan 2014 20:23:10 +0100
Romain François wrote:
> Hello,
>
> The problem is that you have logic in both your mother and child packages.
> IMO, you should only have logic in the mother package.
>
> I’ve done this in a number of
On Wed, Jan 22, 2014 at 10:55 AM, Brian Lee Yung Rowe wrote:
> Hello,
>
> I'm writing a script that automates the testing of reverse dependencies of
> a package. I found the function testInstalledPackage in the tools package,
> which seems to do what I want. However, when I use it for a source pac
Winston,
Thanks for the pointer. Hadley made the same suggestion. One thing I was
looking to do though was have something like this automated, so it would be
nice to have a return value instead of just results written to files. That's
one nice thing about the testInstalledPackage function, desp
Hi all,
what is the supported way to get the package namespace from C? I want to
call a non-exported R function from C, and did not find anything in the
docs.
Thanks,
Gabor
[[alternative HTML version deleted]]
__
R-devel@r-project.org mailing
Gabor,
You can evaluate R code from C, so it should be pretty straightforward to
construct a call to :::
::: looks like it just uses get, so you could probably do that as well.
~G
On Mon, Jan 27, 2014 at 7:30 PM, Gábor Csárdi wrote:
> Hi all,
>
> what is the supported way to get the package n
Indeed, thanks.
Btw. is it by design, that if I do EVAL(lang3(install(), ...)) from a
package, it is not evaluated in the package's namespace?
Anyway, this is how I did it in some old code of mine:
PROTECT(rho = EVAL(lang2(install("getNamespace"),
ScalarString(mkChar
