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

2010-03-27 Thread Henrik Bengtsson
Hi. On Mon, Mar 22, 2010 at 5:36 PM, Seth Falcon s...@userprimary.net wrote: On 3/22/10 3:57 AM, Martin Maechler wrote: SF == Seth Falcons...@userprimary.net     on Fri, 19 Mar 2010 13:47:17 -0700 writes:     SF  On 3/17/10 9:11 AM, Henrik Bengtsson wrote:      Currently library() and

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

2010-03-22 Thread Martin Maechler
SF == Seth Falcon s...@userprimary.net on Fri, 19 Mar 2010 13:47:17 -0700 writes: SF 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

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

2010-03-22 Thread Seth Falcon
On 3/22/10 3:57 AM, Martin Maechler wrote: SF == Seth Falcons...@userprimary.net on Fri, 19 Mar 2010 13:47:17 -0700 writes: SF 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

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

2010-03-19 Thread Seth Falcon
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

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

2010-03-17 Thread Henrik Bengtsson
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.