Re: [Rd] conflicting imports despite using importFrom in NAMESPACE

2013-06-05 Thread Jombart, Thibaut
Hi Martin, thanks, this is reassuring - I'm assuming it is just a problem on my computer then. Thanks for pointing out the exportPattern("."). For some purposes I actually ended up needing to export some hidden functions, but I guess I could just not export these and reference to them explic

Re: [Rd] conflicting imports despite using importFrom in NAMESPACE

2013-06-05 Thread Martin Morgan
On 06/05/2013 11:59 AM, peter dalgaard wrote: I'd suspect that the Imports: line in DESCRIPTION imports the full namespaces, including conflicting items, on top of importFrom items. Does it not help to use Depends: instead? I think of Imports: and Depends: as different -- presumably the end u

Re: [Rd] conflicting imports despite using importFrom in NAMESPACE

2013-06-05 Thread peter dalgaard
I'd suspect that the Imports: line in DESCRIPTION imports the full namespaces, including conflicting items, on top of importFrom items. Does it not help to use Depends: instead? -pd On Jun 5, 2013, at 18:48 , Jombart, Thibaut wrote: > > Dear all, > > It is my understanding that using 'impo

[Rd] conflicting imports despite using importFrom in NAMESPACE

2013-06-05 Thread Jombart, Thibaut
Dear all, It is my understanding that using 'importFrom' in the NAMESPACE of a package allows to avoid conflicts between different packages defining objects with identical names. However, I can still see conflicts while loading the package using 'library'. Here is a toy example, with a packa

Re: [Rd] strange value in .Last.value

2013-06-05 Thread Duncan Murdoch
On 05/06/2013 10:18 AM, Vitalie Spinu wrote: >> Duncan Murdoch >> on Wed, 5 Jun 2013 07:59:54 -0400 wrote: [...] >> As I take it, it is. Thus, ess/orgmode -- which relies on .Last.value >> for results handling and does not expect that $visible element -- should >> adapt and ignore

Re: [Rd] strange value in .Last.value

2013-06-05 Thread Vitalie Spinu
>> Duncan Murdoch >> on Wed, 5 Jun 2013 07:59:54 -0400 wrote: [...] >> As I take it, it is. Thus, ess/orgmode -- which relies on .Last.value >> for results handling and does not expect that $visible element -- should >> adapt and ignore that explicitly? > I think you'll need to ask on

Re: [Rd] strange value in .Last.value

2013-06-05 Thread Duncan Murdoch
On 13-06-05 3:35 AM, Andreas Leha wrote: Hi Winston, Winston Chang writes: This is the result of the withVisible() function, which is called by source(). This should illustrate what it does: withVisible(1+1) $value [1] 2 $visible [1] TRUE withVisible(invisible(1+1)) $value [1] 2 $vis

Re: [Rd] strange value in .Last.value

2013-06-05 Thread Andreas Leha
Hi Winston, Winston Chang writes: > This is the result of the withVisible() function, which is called by > source(). This should illustrate what it does: > >> withVisible(1+1) > $value > [1] 2 > > $visible > [1] TRUE > > >> withVisible(invisible(1+1)) > $value > [1] 2 > > $visible > [1] FALSE >