Re: [Rd] Silently loading and Depends: versus NAMESPACE imports

2012-02-24 Thread Suraj Gupta
Ok...I think I see the confusion. I thought that having a package in my Imports is supposed to automatically suppress startup messages so that library( my_package ) only shows info for packages that are attached, not those that are loaded because they are imported. I didn't realize that some folk

Re: [Rd] Silently loading and Depends: versus NAMESPACE imports

2012-02-24 Thread Uwe Ligges
On 24.02.2012 18:53, Uwe Ligges wrote: On 24.02.2012 18:52, Suraj Gupta wrote: My problem is the same problem that Dirk first asked about. I want to reduce the verbose noise. I want my Imports to not show any startup messages when I load my own package. Are you going to pull me? Use suppre

Re: [Rd] Silently loading and Depends: versus NAMESPACE imports

2012-02-24 Thread Uwe Ligges
On 24.02.2012 18:52, Suraj Gupta wrote: My problem is the same problem that Dirk first asked about. I want to reduce the verbose noise. I want my Imports to not show any startup messages when I load my own package. Are you going to pull me? Use suppressPackageStartupMessages()! Uwe Ligges

Re: [Rd] Silently loading and Depends: versus NAMESPACE imports

2012-02-24 Thread Suraj Gupta
My problem is the same problem that Dirk first asked about. I want to reduce the verbose noise. I want my Imports to not show any startup messages when I load my own package. 2012/2/24 Uwe Ligges > > > On 24.02.2012 18:48, Suraj Gupta wrote: > >> Correct, nothing happens in terms of startup me

Re: [Rd] Silently loading and Depends: versus NAMESPACE imports

2012-02-24 Thread Uwe Ligges
On 24.02.2012 18:48, Suraj Gupta wrote: Correct, nothing happens in terms of startup messages. No messages are shown. library( my package ) # Performance Analytics message shown search() # PerformanceAnalytics is not in the search list since its in my Imports, not Depends suppressPackageStar

Re: [Rd] Silently loading and Depends: versus NAMESPACE imports

2012-02-24 Thread Suraj Gupta
Also, if I just startup a fresh copy of R and I don't load my package then suppressPackageStartupMessages**( library("PerformanceAnalytics"**)) also does not produce any messages. On Fri, Feb 24, 2012 at 12:48 PM, Suraj Gupta wrote: > Correct, nothing happens in terms of startup messages. No m

Re: [Rd] Silently loading and Depends: versus NAMESPACE imports

2012-02-24 Thread Suraj Gupta
Correct, nothing happens in terms of startup messages. No messages are shown. library( my package ) # Performance Analytics message shown search() # PerformanceAnalytics is not in the search list since its in my Imports, not Depends suppressPackageStartupMessages**( library("PerformanceAnalytics

Re: [Rd] Silently loading and Depends: versus NAMESPACE imports

2012-02-24 Thread Uwe Ligges
On 24.02.2012 18:02, Suraj Gupta wrote: Sorry, let me provide the details: My package has a .onAttach function (not a .onLoad). The .onAttach constructs a startup message and delivers it via packageStartupMessage(). I've pasted the code below. My package has a number of other packages in De

Re: [Rd] Silently loading and Depends: versus NAMESPACE imports

2012-02-24 Thread Suraj Gupta
Sorry, let me provide the details: My package has a .onAttach function (not a .onLoad). The .onAttach constructs a startup message and delivers it via packageStartupMessage(). I've pasted the code below. My package has a number of other packages in Depends and Imports. Some of the packages in I

Re: [Rd] function remains loaded in the search space after detaching the package

2012-02-24 Thread Uwe Ligges
On 24.02.2012 16:55, Joris Meys wrote: Maybe I should rephrase: As mentioned by Martin, by you and by TFM (which I read), unloadNamespaces does not remove registered S3 methods. I got the message before. As to why it has to be this way, the people that WTFM didn't really add much information t

Re: [Rd] function remains loaded in the search space after detaching the package

2012-02-24 Thread Joris Meys
Maybe I should rephrase: As mentioned by Martin, by you and by TFM (which I read), unloadNamespaces does not remove registered S3 methods. I got the message before. As to why it has to be this way, the people that WTFM didn't really add much information to TFM for those who RTFM (nor do they have

Re: [Rd] function remains loaded in the search space after detaching the package

2012-02-24 Thread Prof Brian Ripley
fortunes::fortune('WTFM') applies. As already pointed out, ?detach says If a package has a namespace, detaching it does not by default unload the namespace (and may not even with ‘unload=TRUE’), and detaching will not in general unload any dynamically loaded compiled code (D

Re: [Rd] function remains loaded in the search space after detaching the package

2012-02-24 Thread Joris Meys
2012/2/24 Prof Brian Ripley : > > As > > getS3method('print', 'object_size') > > would have confirmed the expectations of a 'one' with a less sketchy > understanding of R. > Yes, getS3method() sends you -not very surprisingly- to the one from gdata. I realized, as print(object.size(iris)) gets that

Re: [Rd] function remains loaded in the search space after detaching the package

2012-02-24 Thread Prof Brian Ripley
On Fri, 24 Feb 2012, Joris Meys wrote: Indeed, when trying : detach('package:gdata',unload=TRUE) print(object.size(iris),units='Kb') [1] 6424 However, when I do : unloadNamespace('gdata') gc() used (Mb) gc trigger (Mb) max used (Mb) Ncells 380471 10.2 667722 17.9 597831 16.0

Re: [Rd] Silently loading and Depends: versus NAMESPACE imports

2012-02-24 Thread Dirk Eddelbuettel
On 24 February 2012 at 00:27, Suraj Gupta wrote: | I don't think that is it.  My startup message is currently in .onAttach and I | still see startup message from packages that I have moved from Imports to | Depends. | Dirk? There are / were are few issues intertwined in my case, and yours may dif

Re: [Rd] function remains loaded in the search space after detaching the package

2012-02-24 Thread Joris Meys
Indeed, when trying : > detach('package:gdata',unload=TRUE) > print(object.size(iris),units='Kb') [1] 6424 However, when I do : > unloadNamespace('gdata') > gc() used (Mb) gc trigger (Mb) max used (Mb) Ncells 380471 10.2 667722 17.9 597831 16.0 Vcells 353363 2.7 905753 7.0

Re: [Rd] function remains loaded in the search space after detaching the package

2012-02-24 Thread Prof Brian Ripley
On 24/02/2012 11:20, Martin Maechler wrote: Joris Meys on Fri, 24 Feb 2012 11:24:35 +0100 writes: > I ran into some very irritating behaviour I don't > understand. Let me illustrate with the package gdata() > and the function print.object_size() : >> print(object.

Re: [Rd] Silently loading and Depends: versus NAMESPACE imports

2012-02-24 Thread Uwe Ligges
On 24.02.2012 07:45, Hervé Pagès wrote: On 01/28/2012 08:15 AM, Dirk Eddelbuettel wrote: On 28 January 2012 at 16:52, Uwe Ligges wrote: | | | On 27.01.2012 15:57, Dirk Eddelbuettel wrote: |> |> On 12 January 2012 at 12:12, Hervé Pagès wrote: |> | Hi Dirk, |> | |> | On 01/11/2012 11:42 AM, Dir

Re: [Rd] function remains loaded in the search space after detaching the package

2012-02-24 Thread Joris Meys
Aaargh... I should RTFM more closely. Thanks for pointing this out. On Fri, Feb 24, 2012 at 12:20 PM, Martin Maechler wrote: >> Joris Meys >>     on Fri, 24 Feb 2012 11:24:35 +0100 writes: > >    > I ran into some very irritating behaviour I don't >    > understand.  Let me illustrate w

Re: [Rd] function remains loaded in the search space after detaching the package

2012-02-24 Thread Martin Maechler
> Joris Meys > on Fri, 24 Feb 2012 11:24:35 +0100 writes: > I ran into some very irritating behaviour I don't > understand. Let me illustrate with the package gdata() > and the function print.object_size() : >> print(object.size(iris),units='Kb') > 6.3 Kb >>

[Rd] function remains loaded in the search space after detaching the package

2012-02-24 Thread Joris Meys
I ran into some very irritating behaviour I don't understand. Let me illustrate with the package gdata() and the function print.object_size() : > print(object.size(iris),units='Kb') 6.3 Kb > getAnywhere(print.object_size) A single object matching ‘print.object_size’ was found It was found in the