I posted the query below on r-help, but perhaps r-devel is more
suitable... (I guess "r-devel" should be read as "those who develop
(i.e. write) programs in R" rather than "those who develop R"?)
-s
I would like to trace functions, displaying their arguments and return
value, but I h
A possible fix for this is to filter the 'unsused' list before
printing the error message and replacing the promises with
their PRCODE expressions.
Index: match.c
===
--- match.c (revision 48329)
+++ match.c (working copy)
@@
Hi all, and thanks for the responses.
As per Bill's suggestion, I tried:
x <- try(flowClust(tFrame, K=30, B=1000, varNames=c('CD4', 'CD8','KI67',
'CD45RO', 'CD28', 'CD57', 'CCR5', 'CD19','CD27', 'CCR7','CD127')),
silent=TRUE)
and it caught the error.
Indeed,
x <- try(res30 <- flowClust(tFr
> -Original Message-
> From: l...@stat.uiowa.edu [mailto:l...@stat.uiowa.edu]
> Sent: Thursday, April 16, 2009 9:27 AM
> To: William Dunlap
> Cc: Dirk Eddelbuettel; Kieran O'Neill; r-devel@r-project.org
> Subject: Re: [Rd] How can I catch errors thrown from c via
> the Rcpperror() functio
Something seems amiss in the process of generating the errormessage:
f <- function(x){}
f(y = print("foo"))
[1] "foo"
Error in f(y = print("foo")) : unused argument(s) (y = "foo")
The argument seems to be getting evaluated and its value is being used.
luke
On Thu, 16 Apr 2009, William Dunlap
ml-it-r-de...@epigenomics.com wrote:
> Hi,
>
> since a couple of days ago I see failures when using
> R CMD INSTALL -l lib path-to-src/pkg.tar.gz
>
> This occurs in automated library updating via a shell script and is caused by
> the
> immediate preceding call to leave an 00LOCK folder
> even t
Note that Kieren's example labelled the first
argument to try() with an improper label res30=,
not expr= (or is that a mailer turning something
into '30='?). If it really is an improper argument
tag then this could be showing a buglet in reporting
on wrongly named arguments:
> invisible(rm(x,y)
Hi,
since a couple of days ago I see failures when using
R CMD INSTALL -l lib path-to-src/pkg.tar.gz
This occurs in automated library updating via a shell script and is caused by
the
immediate preceding call to leave an 00LOCK folder
even though the package installation of that call succeeded.
On 4/16/2009 4:50 AM, j.w.a.jan...@uu.nl wrote:
> Full_Name: Jeroen Jansen
> Version: 2.7.2
> OS: Windows XP Pro
> Submission from: (NULL) (131.211.169.89)
>
>
> Allready with startup I get error message:
>R version 2.7.2 (2008-08-25)
That version is not current, but it looks to me as though
On 4/16/2009 4:50 AM, j.w.a.jan...@uu.nl wrote:
Full_Name: Jeroen Jansen
Version: 2.7.2
OS: Windows XP Pro
Submission from: (NULL) (131.211.169.89)
Allready with startup I get error message:
R version 2.7.2 (2008-08-25)
That version is not current, but it looks to me as though you've
corr
Greetings,
I just found out a bug in the function lmList of the package nlme with R
2.8.1 running under windows XP 32-bits. I have a data table with various
columns corresponding to continuous variables as well as treatment
variables taken on several years and several sites. Here is an example
Full_Name: Jeroen Jansen
Version: 2.7.2
OS: Windows XP Pro
Submission from: (NULL) (131.211.169.89)
Allready with startup I get error message:
R version 2.7.2 (2008-08-25)
Copyright (C) 2008 The R Foundation for Statistical Computing
ISBN 3-900051-07-0
R is free software and comes
12 matches
Mail list logo
