[Rd] prompt () and backticks for default arguments

2010-08-17 Thread Claudia Beleites
Dear all, I just noticed, that prompt () looses backticks that protect default arguments: f <- function (FUN = `*`) {} cat (prompt (f, NA)$usage) yields: \usage{ f(FUN = *) } %- maybe also 'usage' for other objects documented here. without the backticks, which is of course found by R CMD check

Re: [Rd] parent.frame(1) of a S4 method is not a calling environment.

2010-08-17 Thread Duncan Murdoch
Vitaly S. wrote: Martin Morgan writes: So, can I be sure that for such functions parent.frame(2) will always work? What are the additional rules? callNextMethod() will cause additional problems; the idea that you'll grab things from somewhere other than function arguments doesn't se

Re: [Rd] prompt () and backticks for default arguments

2010-08-17 Thread Prof Brian Ripley
On Tue, 17 Aug 2010, Claudia Beleites wrote: Dear all, I just noticed, that prompt () looses backticks that protect default arguments: f <- function (FUN = `*`) {} cat (prompt (f, NA)$usage) yields: \usage{ f(FUN = *) } %- maybe also 'usage' for other objects documented here. without the b

[Rd] DetachedEval Issues

2010-08-17 Thread Martin Kerr
Hello everyone, I have been attempting to make use of the newly implemented detachedEval functionality and I am having a few teething issues. My code works fine when tested with both the Client and the Server on a single machine, but issues arise when I run them separately.Possibly because the l

Re: [Rd] prompt () and backticks for default arguments

2010-08-17 Thread Claudia Beleites
Thanks, that works. Are there any drawbacks to doing that in general? If not, I suggest the following patch for utils/prompt.R 87c87,88 < paste(deparse(argls[[i]], width.cutoff= 500L), --- > paste(deparse(argls[[i]], width.cutoff= 500L

[Rd] Problems building own package (Error: "package has been build before R-2.10.0")

2010-08-17 Thread Janko Thyson
Dear List, I’m doing my first baby steps towards developing own R Packages and ran into the following problem: R CMD check mypackage works fine (no errors, no warnings) R CMD build mypackage works fine (no errors, no warnings) R CMD INSTALL –library=”C:\R\R-2.11.1\library” “something\mypa

Re: [Rd] [R] Problems building own package (Error: "package has been build before R-2.10.0")

2010-08-17 Thread Uwe Ligges
On 17.08.2010 20:36, Janko Thyson wrote: Dear List, I’m doing my first baby steps towards developing own R Packages and ran into the following problem: First baby step: Do not cross-post on several lists. R CMD check mypackage works fine (no errors, no warnings) R CMD build mypackage

Re: [Rd] [R] Problems building own package (Error: "package has been build before R-2.10.0")

2010-08-17 Thread Janko Thyson
> -Ursprüngliche Nachricht- > Von: Uwe Ligges [mailto:lig...@statistik.tu-dortmund.de] > Gesendet: Dienstag, 17. August 2010 22:00 > An: Janko Thyson > Cc: r-de...@r-project. org > Betreff: Re: [R] Problems building own package (Error: "package has > been build before R-2.10.0") > > > >

Re: [Rd] [R] Problems building own package (Error: "package has been build before R-2.10.0")

2010-08-17 Thread Uwe Ligges
Then, you have the package installed under another libarry that is first on your search path. Uwe Ligges On 17.08.2010 22:07, Janko Thyson wrote: -Ursprüngliche Nachricht- Von: Uwe Ligges [mailto:lig...@statistik.tu-dortmund.de] Gesendet: Dienstag, 17. August 2010 22:00 An: Janko Thyso

Re: [Rd] DetachedEval Issues

2010-08-17 Thread Simon Urbanek
On Aug 17, 2010, at 9:32 AM, Martin Kerr wrote: > > Hello everyone, > I have been attempting to make use of the newly implemented detachedEval > functionality and I am having a few teething issues. I presume you're talking about Rserve? Please use the proper mailing list rosuda-stats-devel fo

Re: [Rd] parent.frame(1) of a S4 method is not a calling environment.

2010-08-17 Thread Vitaly S.
Duncan Murdoch writes: > Vitaly S. wrote: >> Martin Morgan writes: >> So, can I be sure that for such functions parent.frame(2) will always work? What are the additional rules? >>> callNextMethod() will cause additional problems; the idea that you'll >>> grab thin

Re: [Rd] parent.frame(1) of a S4 method is not a calling environment.

2010-08-17 Thread Hadley Wickham
On Tuesday, August 17, 2010, Vitaly S. wrote: > Duncan Murdoch writes: > >> Vitaly S. wrote: >>> Martin Morgan writes: >>> > So,  can I be sure that for such functions parent.frame(2) will always > work? > What are the additional rules? > callNextMethod() will cause additio