[Rd] Circumventing code/documentation mismatches ('R CMD check')

n the user- exposed documentation and using ... \usage{test2(Argument1=NA)} ... leads to a warning reagrding a code/documentation mismatch. Is there any way to prevent that? Sincerely, Joh Prof Brian Ripley wrote: > On Mon, 4 Jul 2011, Johannes Graumann wrote: > >> Hello, >&g

[Rd] Incorporating single functions from other packages: rules and regulations?

Hi, In a little pkg I'm developing I am in need of the functionality provided by plotrix::listDepth. I am loath of having the depend on and import the whole package just for that purpose. What is an acceptable way of integrating this functionality into my own package? Just copying the functio

[Rd] Package Directory Hierarchy: Recursive inclusion of *.R possible?

Hello, I would like to organize the "R" directory in my home-grown package into sub-directories, but "R CMD --build" doesn't seem to find *.R files below the actual source directory. Is there any way around that? Thanks, Joh __ R-devel@r-project.org

[Rd] Package Building and Name Space

... sorry for reposting this in a more appropriate forum than r.general ... Hello, I just don't get this and would appreciate if someone could write a line or two: I'm trying to build this package and it stops installing after I add the following to the NAMESPACES file: >importFrom(gsubfn,strapp

Re: [Rd] Package Building and Name Space

On Wednesday 23 January 2008 17:25:38 Duncan Murdoch wrote: > On 1/23/2008 11:11 AM, Johannes Graumann wrote: > > ... sorry for reposting this in a more appropriate forum than r.general > > ... > > > > Hello, > > > > I just don't get this and would app

Re: [Rd] Package Building and Name Space

On Wednesday 23 January 2008 18:24:15 Duncan Murdoch wrote: > On 1/23/2008 11:31 AM, Johannes Graumann wrote: > > On Wednesday 23 January 2008 17:25:38 Duncan Murdoch wrote: > >> On 1/23/2008 11:11 AM, Johannes Graumann wrote: > >> > ... sorry for reposting this in

[Rd] R CMD check and postscript fonts

Hello, I came across this by using R cmd check - otherwise I would probably not have noticed. One of my functions does something like this: # postscript() # plot(1, xlim = c(0, 10), ylim = c(0, 4), type = "n", ann = FALSE, axes = FALSE) # text(1:10, 2, c("a","b"), cex = seqcex, family="mono",font=

[Rd] Plot definition for custom class

Hi, Is there any way to trick R CMD check into not throwing this error after I created a dedicated "plot" incarnation for my custom function? * checking S3 generic/method consistency ... WARNING plot: function(x, ...) plot.MQUSpecMatch: function(x, mozlabel, labelcex) Thanks again, Joh

Re: [Rd] R CMD check and postscript fonts

Prof Brian Ripley stats.ox.ac.uk> writes: > > On Thu, 24 Jan 2008, Johannes Graumann wrote: > > > Hello, > > I came across this by using R cmd check - otherwise I would probably not > > have > > noticed. > > One of my functions does something like t

Re: [Rd] Plot definition for custom class

Kurt Hornik wu-wien.ac.at> writes: > > >>>>> Johannes Graumann writes: > > > Hi, > > Is there any way to trick R CMD check into not throwing this error after I > > created a dedicated "plot" incarnation for my custom function? >

Re: [Rd] R CMD check and postscript fonts

Prof Brian Ripley wrote: > On Thu, 24 Jan 2008, Johannes Graumann wrote: > >> Prof Brian Ripley stats.ox.ac.uk> writes: >> >>> >>> On Thu, 24 Jan 2008, Johannes Graumann wrote: >>> >>>> Hello, >>>> I came across this

Re: [Rd] R CMD check and postscript fonts

Johannes Graumann wrote: > Prof Brian Ripley wrote: > >> On Thu, 24 Jan 2008, Johannes Graumann wrote: >> >>> Prof Brian Ripley stats.ox.ac.uk> writes: >>> >>>> >>>> On Thu, 24 Jan 2008, Johannes Graumann wrote: >>>&g