On Sat, Sep 5, 2009 at 6:15 AM, Andrew Piskorski wrote:
> On Fri, Sep 04, 2009 at 08:39:12AM -0500, Hadley Wickham wrote:
>
>> When developing a package, it's often useful to be able to reload it,
>> without re-installing, re-starting R and re-loading.
>
> Why would you ever need to restart R in su
On Fri, Sep 04, 2009 at 08:39:12AM -0500, Hadley Wickham wrote:
> When developing a package, it's often useful to be able to reload it,
> without re-installing, re-starting R and re-loading.
Why would you ever need to restart R in such a situation?
What I do is make the code change in my package
This is sufficiently useful that it would be nice to have it
as part of R itself. For the moment, perhaps you could
make a package of it on CRAN or contribute it to some
other existing CRAN package.
On Fri, Sep 4, 2009 at 9:39 AM, Hadley Wickham wrote:
> Hi all,
>
> When developing a package, it'
> Nice. I would guess many of us would have versions of this, it would be good
> to formalise it so that it could deal with :
> - namespaces, you might want your unexported functions to be separate from
> your exported functions. It looks like your function loads everything into
> .GlobalEnv
> - S4
On 09/04/2009 03:39 PM, Hadley Wickham wrote:
Hi all,
When developing a package, it's often useful to be able to reload it,
without re-installing, re-starting R and re-loading. To do this I've
written a little script that inspects the package description and
loads dependencies, data and code -
Hi all,
When developing a package, it's often useful to be able to reload it,
without re-installing, re-starting R and re-loading. To do this I've
written a little script that inspects the package description and
loads dependencies, data and code - http://gist.github.com/180883.
It's obviously no
