From seth at userprimary.net  Fri Mar 19 21:47:17 2010
From: seth at userprimary.net (Seth Falcon)
Date: Fri, 19 Mar 2010 13:47:17 -0700
Subject: [Rd] Suggestion: Not having to export .conflicts.OK in name
	spaces
In-Reply-To: <59d7961d1003170911o38814b59h3fdb4de42e21b723@mail.gmail.com>
References: <59d7961d1003170911o38814b59h3fdb4de42e21b723@mail.gmail.com>
Message-ID: <4BA3E2D5.5050305@userprimary.net>

On 3/17/10 9:11 AM, Henrik Bengtsson wrote:
> Currently library() and attach() fail to locate an existing
> '.conflicts.OK' in a package wit name space, unless it is exported.
> Since there should be little interest in exporting '.conflicts.OK'
> otherwise, one may argue that those methods should look for
> '.conflicts.OK' even if it is not exported.

I guess I agree that there is no real value in forcing .conflicts.OK to 
be exported.  OTOH, this seems like a dubious feature to begin.  When is 
it a good idea to use it?

+ seth

-- 
Seth Falcon | @sfalcon | http://userprimary.net/



[Rd] Suggestion: Not having to export .conflicts.OK in name spaces
Seth Falcon