Hi all
I am not sure this question is better suitted for the R-devel or R-help,
but here it goes anyway
I am not a software developer but I have produced a personal set of
functions that I would like now to combine in a package.
I am finding this really hard to do only by following the manuals
hhc is the Microsoft Help compiler. Make sure its on your path.
Info on it is here:
http://www.murdoch-sutherland.com/Rtools/#ldbug
Also batchfiles:
http://cran.r-project.org/contrib/extra/batchfiles/
contains a Windows XP batch file, rfind.bat, that you can run without arguments
that will try t
When I saw the subject of the original message on
R-help, I was 95% confident that I knew the answer
(before I had seen the question).
This made me think that perhaps for some functions
there should be a 'Troubleshooting' section in the help
file.
The current help file for 'integrate' does say, a
If an expression is passed to stopifnot() which contains missing values,
then the resulting error message is somewhat baffling until you are used
to it, e.g.
> x <- y <- rep(TRUE, 10)
> y[7] <- NA
> stopifnot(x, y)
Error in if (!(is.logical(r <- eval(ll[[i]])) && all(r)))
stop(paste(deparse(mc[
Wouldn't it be better to do something like
stopifnot(all(!is.na(x)), all(!is.na(y)), x, y)
rather than have stopifnot() go checking for NAs? I agree the message is
strange but if having non-NA values is really a condition, then why not just
put
it in the call to stopifnot()?
-roger
Dan Davi
On Wed, 1 Mar 2006, Roger D. Peng wrote:
> Wouldn't it be better to do something like
>
> stopifnot(all(!is.na(x)), all(!is.na(y)), x, y)
>
> rather than have stopifnot() go checking for NAs? I agree the message is
> strange but if having non-NA values is really a condition, then why not just
>
Hi,
This is essentially a reposting of
http://tolstoy.newcastle.edu.au/R/devel/05/11/3305.html
which had no responses, and the behaviour reported there persists in
r-devel as of yesterday.
(1) sort() with non-null partial
> x = rnorm(10)
> keep = as.integer(ppoints(1) * 10)
> syste
Hi,
Even though R is a functional language and it's common to have
functions as arguments to other functions (notably lapply and
friends), it is not possible to manipulate functions as easily as
other objects. I particularly miss
1. An operator to combine functions (analogous to %*%), e.g.
"%of%
stopifnot() is not intended for use by end-users, but for tests in
packages. If the writers of package tests are not aware of the perils of
using == or != with numbers, then it is good that they get reminded.
And we do have isTRUE for use with it.
On Wed, 1 Mar 2006, Dan Davison wrote:
> On
> "BDR" == Prof Brian Ripley <[EMAIL PROTECTED]>
> on Thu, 2 Mar 2006 06:45:39 + (GMT) writes:
BDR> stopifnot() is not intended for use by end-users, but for tests in
BDR> packages.
and additionally for "function writers" aka 'programmeRs'.
I think we have argued that
10 matches
Mail list logo
