Peter Dalgaard's reply made me wonder if you were looking for a
precise answer to
what will actually happens at build and load time?
The best way to answer such questions is to read the source code (and
now this is all in R, it should be accessible to all).
Nothing happens at 'build time',
On Jun 15, 2011, at 16:22 , Prof Brian Ripley wrote:
>
> So your example creates an object 'x' in the package or name space. Which is
> perfectly legal, but maybe not intentional. For example, R's base package
> does
> ...
Yes. Nothing illegal about it, but might be worth noticing that if La
On Tue, 14 Jun 2011, Stephen Ellison wrote:
I'm sure i've seen the answer to this, but can't find it:
If there is executable code in an R package .R file that does not
return a function (that is, something like x <- rnorm(5), outside
any function body ), what will actually happens at build an
I'm sure i've seen the answer to this, but can't find it:
If there is executable code in an R package .R file that does not return a
function (that is, something like x <- rnorm(5), outside any function body ),
what will actually happens at build and load time?
And (more importantly, so I can p
