From murdoch.duncan at gmail.com  Wed Jul  6 15:42:33 2011
From: murdoch.duncan at gmail.com (Duncan Murdoch)
Date: Wed, 06 Jul 2011 09:42:33 -0400
Subject: [Rd] Recent and upcoming changes to R-devel
In-Reply-To: <CAC2h7uujLLQQCzQBgfCmbaFg-UeQqMzntQfXD8YhyjSRQpAWDw@mail.gmail.com>
References: <alpine.OSX.1.00.1107041124460.59432@tystie.local>
	<CAC2h7uujLLQQCzQBgfCmbaFg-UeQqMzntQfXD8YhyjSRQpAWDw@mail.gmail.com>
Message-ID: <4E146649.7080909@gmail.com>

On 11-07-06 9:25 AM, Kasper Daniel Hansen wrote:
> On Mon, Jul 4, 2011 at 8:08 AM, Prof Brian Ripley<ripley at stats.ox.ac.uk>  wrote:
>> In the near future all packages will have a name space.  If the sources do
>> not contain one, a default NAMESPACE file will be added. This again will
>> simplify the descriptions and also a lot of internal code.  Maintainers of
>> packages without name spaces (currently 42% of CRAN) are encouraged to add
>> one themselves.
>
> This is great.  However, it would also be great if a user could
> disable this for a given package at install time, for example with a
> command line argument to R CMD INSTALL.  Use case: in the early stages
> of package development I find it incredible useful to not have a
> NAMESPACE.  This is of course before I release it to anyone else;
> purely for development.
>
> My guess is that this has already been anticipated, but in case not, I
> wanted to raise the issue.

I think the idea is to completely remove support for the bad search 
order you get when you don't have a namespace.  That search order is a 
mixed blessing in debugging:  it makes it easy to replace functions with 
new versions, but it also makes it very easy to execute the wrong code 
if you happen to have something sitting in the global environment that 
has a conflicting name.

It seems like something a front end could do to make assignInNamespace 
easier to use to make working with namespaces easier.

Duncan Murdoch



[Rd] Recent and upcoming changes to R-devel
Duncan Murdoch