[Rd] Depending on many packages: another best practice question

2007-02-23 Thread hadley wickham
Dear all, ggplot currently requires 13 packages (grid, reshape, RColorBrewer, proto, splines, MASS, Hmisc, boot, butler, hexbin, mapproj, quantreg, sm). Some of these are absolutely necessary (eg. proto), but most are used for one or two specific tasks (eg. boot is only used to get plogis, used f

Re: [Rd] Depending on many packages: another best practice question

2007-02-24 Thread Dirk Eddelbuettel
On 23 February 2007 at 19:38, hadley wickham wrote: | ggplot currently requires 13 packages (grid, reshape, RColorBrewer, | proto, splines, MASS, Hmisc, boot, butler, hexbin, mapproj, quantreg, | sm). Some of these are absolutely necessary (eg. proto), but most are | used for one or two specific

Re: [Rd] Depending on many packages: another best practice question

2007-02-24 Thread Prof Brian Ripley
On Fri, 23 Feb 2007, hadley wickham wrote: > Dear all, > > ggplot currently requires 13 packages (grid, reshape, RColorBrewer, > proto, splines, MASS, Hmisc, boot, butler, hexbin, mapproj, quantreg, > sm). Some of these are absolutely necessary (eg. proto), but most are > used for one or two spec

Re: [Rd] Depending on many packages: another best practice question

2007-02-24 Thread hadley wickham
> > ggplot currently requires 13 packages (grid, reshape, RColorBrewer, > > proto, splines, MASS, Hmisc, boot, butler, hexbin, mapproj, quantreg, > > sm). Some of these are absolutely necessary (eg. proto), but most are > > used for one or two specific tasks (eg. boot is only used to get > > plogi

Re: [Rd] Depending on many packages: another best practice question

2007-02-24 Thread Prof Brian Ripley
On Sat, 24 Feb 2007, hadley wickham wrote: >> > ggplot currently requires 13 packages (grid, reshape, RColorBrewer, >> > proto, splines, MASS, Hmisc, boot, butler, hexbin, mapproj, quantreg, >> > sm). Some of these are absolutely necessary (eg. proto), but most are >> > used for one or two specif

Re: [Rd] Depending on many packages: another best practice question

2007-02-25 Thread hadley wickham
On 2/24/07, Prof Brian Ripley <[EMAIL PROTECTED]> wrote: > On Sat, 24 Feb 2007, hadley wickham wrote: > > >> > ggplot currently requires 13 packages (grid, reshape, RColorBrewer, > >> > proto, splines, MASS, Hmisc, boot, butler, hexbin, mapproj, quantreg, > >> > sm). Some of these are absolutely n

Re: [Rd] Depending on many packages: another best practice question

2007-02-25 Thread Gabor Grothendieck
You can use if(require(myPackage)) { ... } or \dontrun{ ... } or make them demos in the myPackage/demo directory since demos are not checked. On 2/25/07, hadley wickham <[EMAIL PROTECTED]> wrote: > On 2/24/07, Prof Brian Ripley <[EMAIL PROTECTED]> wrote: > > On Sat, 24 Feb 2007, hadley wickh

Re: [Rd] Depending on many packages: another best practice question

2007-02-25 Thread Seth Falcon
"Gabor Grothendieck" <[EMAIL PROTECTED]> writes: > You can use > > if(require(myPackage)) { ... } Probably you will want: if (suppressWarnings(require("somePkg"))) { ... } This way, you won't get a lot of noise when somePkg isn't installed. Running the examples at least some of the time seem

Re: [Rd] Depending on many packages: another best practice question

2007-02-26 Thread hadley wickham
> You can use > > if(require(myPackage)) { ... } Yes, but the problem with this is that I now have the fact that this function requires that package stated in two places - in the body of the function, and in the examples - adding redundancy which makes maintenance harder. I guess what I really wa