Re: [Rd] stopifnot() does not stop at first non-TRUE argument

<- function(...) >> { >> n <- length(match.call()) - 1 >> for (i in 1:n) >> { >> nm <- as.name(paste0("..",i)) >> if (!eval(nm)) stop("not all true") >> } >> } >> Stopifnot(2+2==4)

Re: [Rd] problem running test on a system without /etc/localtime

> Henrik Bengtsson > on Tue, 16 May 2017 20:49:02 -0700 writes: > On Tue, May 16, 2017 at 5:35 PM, Kirill Maslinsky wrote: >> Hi all, >> >> A problem with tests while building R. >> >> I'm packaging R for

Re: [Rd] stopifnot() does not stop at first non-TRUE argument

>>>>> <luke-tier...@uiowa.edu> >>>>> on Tue, 16 May 2017 09:49:56 -0500 writes: > On Tue, 16 May 2017, Martin Maechler wrote: >>>>>>> Hervé Pagès <hpa...@fredhutch.org> >>>>>>> on Mon, 15 May

Re: [Rd] stopifnot() does not stop at first non-TRUE argument

H, as mentioned above, the creation of good error messages has been an important design goal of stopifnot() and hence I'm willing to accept the extra complexity of "patching up" the call used in the error / warning messages. Also, as a change to what I posted yesterday, I now plan to follow

Re: [Rd] [bug] droplevels() also drop object attributes (comment…)

> Serge Bibauw > on Mon, 15 May 2017 11:59:32 -0400 writes: > Hi, > Just reporting a small bug… not really a big deal, but I don’t think that is intended: droplevels() also drops all object’s attributes. Yes. The help page for droplevels (or the simple

Re: [Rd] stopifnot() does not stop at first non-TRUE argument

>>>>> Serguei Sokol <so...@insa-toulouse.fr> >>>>> on Mon, 15 May 2017 16:32:20 +0200 writes: > Le 15/05/2017 à 15:37, Martin Maechler a écrit : >>>>>>> Serguei Sokol <so...@insa-toulouse.fr> >>>>

Re: [Rd] stopifnot() does not stop at first non-TRUE argument

uot;,i)) > if (!eval(nm)) stop("not all true") > } > } > Stopifnot(2+2==4) > Stopifnot(2+2==5, print("Hey!!!") == "Hey!!!") > Stopifnot(2+2==4, print("Hey!!!") == "Hey!!!") > Stopifnot(T,T,T,T,T,T,T,T,T,T,T,T,T,

Re: [Rd] stopifnot() does not stop at first non-TRUE argument

ount of (implicit) evaluations was >> already done in the current version: >> >>> source("stopifnot_new.R") >>> stopifnot_new(3 == 5, as.integer(2^32), a <- 12) >> Error: 3 == 5 is not TRUE >>> a >>

Re: [Rd] stopifnot() does not stop at first non-TRUE argument

> Hervé Pagès > on Wed, 3 May 2017 12:08:26 -0700 writes: > On 05/03/2017 12:04 PM, Hervé Pagès wrote: >> Not sure why the performance penalty of nonstandard evaluation would >> be more of a concern here than for something like switch(). > which

Re: [Rd] tempdir() may be deleted during long-running R session

> Dirk Eddelbuettel > on Wed, 26 Apr 2017 08:40:38 -0500 writes: > On 26 April 2017 at 08:29, Duncan Murdoch wrote: > | This seems like the wrong approach. The problem occurs as soon as the > | tempdir() gets cleaned up: there could be information in

Re: [Rd] tempdir() may be deleted during long-running R session

> > on Tue, 25 Apr 2017 21:13:59 -0700 writes: > On Tue, Apr 25, 2017 at 02:41:58PM +, Cook, Malcolm wrote: >> Might this combination serve the purpose: >> * R session keeps an open handle on the tempdir it creates, >> * whatever tempdir

Re: [Rd] tempdir() may be deleted during long-running R session

>>>>> Jeroen Ooms <jeroeno...@gmail.com> >>>>> on Tue, 25 Apr 2017 15:05:51 +0200 writes: > On Tue, Apr 25, 2017 at 1:00 PM, Martin Maechler > <maech...@stat.math.ethz.ch> wrote: >> As I've found it is not at all h

Re: [Rd] tempdir() may be deleted during long-running R session

> Dirk Eddelbuettel > on Sun, 23 Apr 2017 09:15:18 -0500 writes: > On 21 April 2017 at 10:34, frede...@ofb.net wrote: > | Hi Mikko, > | > | I was bitten by this recently and I think some of the replies are > | missing the point. As I understand

Re: [Rd] c() documentation after change; 'recursive' in "base" methods

> Suharto Anggono Suharto Anggono via R-devel > on Wed, 19 Apr 2017 22:50:41 + writes: > In R 3.4.0 RC, argument list of 'c' as S4 generic function has become > (x, ...) . > However, "S4 methods" section in documentation of 'c' (c.Rd) is not

Re: [Rd] "table(droplevels(aq)$Month)" in manual page of droplevels

ickham's "Advanced R". > But note that droplevels(aq)["Month"] and > droplevels(aq)$Month are _not_ the same. The first returns > a data.frame (with just one vector), the latter returns a > vector. To return just a vector you could also

Re: [Rd] Bug report: POSIX regular expression doesn't match for somewhat higher values of upper bound

> > on Tue, 4 Apr 2017 08:45:30 + writes: > Dear Sirs, > while >> regexpr('(.{1,2})\\1', 'foo') > [1] 2 > attr(,"match.length") > [1] 2 > attr(,"useBytes") > [1] TRUE > yields the correct match, an

Re: [Rd] Very hard to reproduce bug (?) in R-devel

> Winston Chang > on Tue, 4 Apr 2017 15:29:40 -0500 writes: > I've done some more investigation into the problem, and it is very > difficult to pin down. What it looks like is happening is roughly like this: > - `p` is an environment and `p$e` is

Re: [Rd] Potential bug in utils::citation()

>>>>> Martin Maechler <maech...@stat.math.ethz.ch> >>>>> on Mon, 3 Apr 2017 10:22:52 +0200 writes: >>>>> Zhian Kamvar <zkam...@gmail.com> >>>>> on Sun, 2 Apr 2017 16:26:37 -0500 writes: >> Hi, I believe th

Re: [Rd] complex NA's match(), etc: not back-compatible change proposal

> Suharto Anggono Suharto Anggono via R-devel > on Sat, 1 Apr 2017 14:10:06 + writes: > I am raising this again. > With > z <- complex(real = c(0,NaN,NaN), imaginary = c(NA,NA,0)) , > results of > sapply(z, match, table = z)

Re: [Rd] Potential bug in utils::citation()

es reproduce the new bug and that is due to a change by me, and I had started investigation on Friday (but not with your package and not having seen a straighforward example yet). This will be fixed ASAP, i.e., within hours. Martin Maechler > Background: > My package poppr suddenly starte

Re: [Rd] `[` not recognized as a primitive in certain cases.

> Joris Meys > on Tue, 28 Mar 2017 15:19:14 +0200 writes: > Thank you gents, I overlooked the subtle differences. > On Tue, Mar 28, 2017 at 2:49 PM, Lukas Stadler > wrote: >> “typeof” is your friend here: >>

Re: [R-pkg-devel] multiple bibentry()s in CITATION

time for 3.4.0. Martin > Best, > John >> -Original Message- >> From: Martin Maechler [mailto:maech...@stat.math.ethz.ch] >> Sent: Monday, January 16, 2017 10:02 AM >> To: Fox, John <j...@mcmaster.ca> >> Cc: r-packag

Re: [Rd] Documentation of model.frame() and get_all_vars()

on? (Or it's a bug > - I don't really know.) I would not want to change model.frame.default() currently as it's too important a building block and it may be wise to require that its callers should have done recycling. > Thanks in advance for your consideration. Thank you Thomas f

Re: [Rd] Error in documentation for ?legend

did not understand Peter: He *did* agree with you that there's no 'title.cex' argument and explained why the oddity probably has happened in the distant past ..) Martin Maechler ETH Zurich and R Core Team (as Peter Dalgaard) > From: peter dalgaard <pda...@gmail.com> > Se

Re: [Rd] A question on stats::as.hclust.dendrogram

following question has become irrelevant now, but yes, dendrograms *are* implemented as nested lists. Martin Maechler ETH Zurich and R core team > The line in question is at line 128 of dendrogram.R in R-3.3.3, at stats::as.hclust.dendrogram: > stopifnot(length(s) == 2L, all( vapp

Re: [Bioc-devel] The story of tracing a derfinder bug on OSX that sometimes popped up, sometimes it didn't. Related to IRanges/S4Vectors '$<-'

> Andrzej Oleś > on Wed, 22 Mar 2017 10:29:57 +0100 writes: > Just for the record, on R-3.3.2 Herve's code fails with the following error: > Error in x[TRUE] <- new("A") : > incompatible types (from S4 to logical) in subassignment type fix yes,

Re: [Rd] IO error when writing to disk

would there be a way to create a small, say 1 MB, temporary file system as a non-root user? In that case, we could do all the testing from inside R .. Best, Martin Maechler > Thanks, > Jean-Sébastien Bevilacqua > 2017-03-20 10:24 GMT+01:00 realitix <reali...@gmail.com>:

Re: [Rd] Hyperbolic tangent different results on Windows and Mac

- and we should use it (by "#undef HAVE_CTAN" (or better by a configure check, using ctanh("500 + 0i"), as I see that on Windows, R> -1i * tan((500+0i)*1i) gives [1] 1+0i as it should for tanh(500+0i) --- but does not on Windows. Martin Maechler ETH Zurich and R Core __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] outer not applying a constant function

ll Dunlap > TIBCO Software > wdunlap tibco.com You are right, thank you! Such a "convenience change" would not be a good idea. Martin Maechler ETH Zurich > On Mon, Mar 20, 2017 at 6:36 AM, Martin Maechler > <maech...@stat.math.ethz.ch> wrote: >

Re: [Rd] outer not applying a constant function

> Gebhardt, Albrecht > on Sun, 19 Mar 2017 09:14:56 + writes: > Hi, > the function outer can not apply a constant function as in the last line of the following example: >> xg <- 1:4 >> yg <- 1:4 >> fxyg <- outer(xg, yg,

Re: [Rd] Support for user defined unary functions

> Jim Hester > on Thu, 16 Mar 2017 12:31:56 -0400 writes: > Gabe, > The unary functions have the same precedence as normal SPECIALS > (although the new unary forms take precedence over binary SPECIALS). > So they are lower precedence than

Re: [R-pkg-devel] Extending an S3 method, but putting the package in Suggests?

ror prone and can be resolved by correct imports as those mentioned. Martin > David > On Tue, 14 Mar 2017 at 09:06, Martin Maechler <maech...@stat.math.ethz.ch> > wrote: >> >>>>> David Hugh-Jones <davidhughjo...@gmail.com> &g

Re: [R-pkg-devel] Extending an S3 method, but putting the package in Suggests?

> David Hugh-Jones > on Tue, 14 Mar 2017 02:46:35 + writes: > David Hugh-Jones > on Tue, 14 Mar 2017 02:46:35 + writes: > Hi, > Cross-posted from SO: >

Re: [Rd] named arguments in formula and terms

Dear Achim, > Achim Zeileis > on Fri, 10 Mar 2017 15:02:38 +0100 writes: > Hi, we came across the following unexpected (for us) > behavior in terms.formula: When determining whether a term > is duplicated, only the order of the arguments in

Re: [Rd] Bug in nlm()

quot;hessian") <- h(x1, x2) return(res) } nlm.fgh <- nlm(fgh, c(-1.2,1)) I have almost finished a more detailed bug report, which I would like to submit. Best, Marie Boehnstedt >>>>> Martin Maechler <maech...@stat.math.ethz.ch> >>>>> on Fri,

Re: [Rd] Please add me to bugzilla

atch for non-recursive > implementations. Very well done, thank you a lot! [and I will add you to bugzilla .. so you can use it for the next bug .. ;-)] Best, Martin > Regards, Bradley > On Mon, Mar 6, 2017 at 3:50 AM, Martin Maechler > <maech...@stat.math.eth

Re: [Rd] Control statements with condition with greater than one should give error (not just warning) [PATCH]

. until the flip is switched for all. or have I overlooked an issue? Martin > On Sat, Mar 4, 2017 at 12:04 PM, Martin Maechler > <maech...@stat.math.ethz.ch >> wrote: >> >>>>> Henrik Bengtsson <henrik.bengts...@gmail.com> >>>>

Re: [Rd] Please add me to bugzilla

rts of the 'R bugs' web page above). Posting to all 1000 R-devel readers with no content about what you consider a bug is a waste of bandwidth for at least 99% of these readers. [Yes, I'm also using their time ... in the hope to *improve* the quality o

Re: [Rd] Control statements with condition with greater than one should give error (not just warning) [PATCH]

> Henrik Bengtsson > on Fri, 3 Mar 2017 10:10:53 -0800 writes: > On Fri, Mar 3, 2017 at 9:55 AM, Hadley Wickham > wrote: >>> But, how you propose a warning-to-error transition >>> should be made without wreaking havoc?

Re: [Rd] Control statements with condition with greater than one should give error (not just warning) [PATCH]

y to hell " Here: The way to R hell starts (or "widens", your choice) by introducing options() that influence basic language semantics !! For robust code you will start to test all code of R for all different possible combinations of these options set I am sure y

Re: [Rd] Bug in nlm()

edback from "the public". Of course, I could be wrong.. and happy if you explain / tell me why. Best, Martin Maechler > Thank you in advance. > Kind regards, > Marie B�hnstedt > Marie B�hnstedt, MSc > Research Scientist > Max Planck Institute

Re: [R-pkg-devel] tryCatch defensive programming guidance

> Berry Boessenkool > on Wed, 1 Mar 2017 14:52:10 + writes: > Hi Glenn, > Better late than never: > couldn't you simply use try? > result <- try( log("a") ) > The printing is horrible: people will think an error > occured

Re: [Rd] stats::median

>>>>> Martin Maechler <maech...@stat.math.ethz.ch> >>>>> on Mon, 27 Feb 2017 10:42:19 +0100 writes: >>>>> Rob J Hyndman <rob.hynd...@monash.edu> >>>>> on Wed, 15 Feb 2017 21:48:56 +1100 writes: >> The

Re: [Rd] Test suite failures in R-devel_2017-02-25_r72256

>>>>> Martin Maechler <maech...@stat.math.ethz.ch> >>>>> on Mon, 27 Feb 2017 16:08:40 +0100 writes: >>>>> Peter Simons <sim...@nospf.cryp.to> >>>>> on Mon, 27 Feb 2017 10:30:39 +0100 writes: >> Hi, I

Re: [Rd] Test suite failures in R-devel_2017-02-25_r72256

> Peter Simons > on Mon, 27 Feb 2017 10:30:39 +0100 writes: > Hi, I tried compiling the latest pre-release for R 3.3.3 > for the NixOS Linux distribution [1], but the build fails > during the "make check" phase because of the following 2 >

Re: [Rd] stats::median

as "breaking any code". In spite of all that *and* the perennial drawback that a '...' will allow argument name typos to go unnoticed I agree you have a good argument nowadays, that median() should be the same as many similar "basic statistics" R functions and

Re: [Rd] rep/rep.int: in NEWS, but not yet ported from trunk

report, and your proposal to make the simple case rep(s, list(7)) work as previously seems ok to me. However, for all this, we will concentrate on R-devel (to become R 3.4.0). Best regards, Martin Maechler __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] Update copyright year in manuals

> On Thu, Feb 23, 2017 at 03:23:10PM +0100, Martin Maechler wrote: > > >>>>> Mikko Korpela <mikko.korp...@helsinki.fi> > > >>>>> on Thu, 23 Feb 2017 14:02:58 +0200 writes: > > > > > With new R releases soon to come,

Re: [Rd] Update copyright year in manuals

> Mikko Korpela > on Thu, 23 Feb 2017 14:02:58 +0200 writes: > With new R releases soon to come, I suggest updating the > Rcopyright macro in "doc/manual/R-defs.texi" to use year > 2017. Now this is an e-mail that *REALLY* does not fit to the

Re: [Rd] possible improvement to ?with examples

> Ben Bolker > on Thu, 16 Feb 2017 15:37:13 -0500 writes: > A querent on StackOverflow asked about the with() function > http://stackoverflow.com/questions/42283479/why-when-to-use-with-function#42283479 > and asked about the example in ?with >

Re: [Rd] Wish List: Extensions to the derivatives table

> > The issue is that without an extensible derivative table or the proposed > extensions, it is not possible to automatically produce (without manual > modification of the deriv3 output) a function that avoids catastrophic > cancellation regardless of the working range. > Manual modification

Re: [Rd] another fix for R crashes under enable-strict-barrier, lto, trunk@72156

> Hin-Tak Leung > on Sat, 11 Feb 2017 19:30:26 + writes: > I haven' t touched R for some 18 months, and so I have no > idea if this is a recent problems or not; but it certainly > did not segfault two years ago. Since it has been >

Re: [Rd] Grapics Device Resolution Limits

eproduce the problem in their versions of R provide (concise and not hard to read) patches to the source of R, we'd probably gratefully accept them.. Martin Maechler >> sessionInfo() > R version 3.3.2 Patched (2017-02-07 r72138) > Platform: i386-w64-mingw32/i386 (32-bit) &

Re: [Rd] R CMD check error (interfacing to C API of other pkg)

> Therneau, Terry M , Ph D > on Thu, 9 Feb 2017 12:56:17 -0600 writes: > Martyn, > No, that didn't work. > One other thing in the mix (which I don't think is the issue) is that I call one of the > C-entry points of expm. So the DESCRIPTION file

Re: [Rd] Ancient C /Fortran code linpack error

--- Last but not least : If you are not afraid of +/- Inf, but really only of NA/NaN's (as the OP said), then note that "THE manual" (= "Writing R Extensions") does mention ISNAN(.) almost in the same place as the first occurence of R_FINITE(.). Best regards, Martin Maechler, ETH Zurich __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] Lack of 'seq_len' in 'head' in 'stopifnot'

> Suharto Anggono Suharto Anggono via R-devel > on Sat, 4 Feb 2017 10:18:33 + writes: > Function 'stopifnot' in R devel r72104 has this. > head <- function(x, n = 6L) ## basically utils:::head.default() > x[if(n < 0L) max(length(x) +

Re: [Rd] RFC: tapply(*, ..., init.value = NA)

age mode (0 for raw) is automatically used." After some thought (and experiments), I have reverted and no longer use if(missing). You are right that it is not needed (and even potentially confusing) here. Changes are in svn c72106. Martin Maechler > --

Re: [Rd] Typos in manuals

> Mikko Korpela > on Wed, 1 Feb 2017 12:16:49 +0200 writes: > I found some trivial typos, mostly unmatched parentheses, in the R > manuals. More information and suggested fixes are in the attached diff file. Thank you very much! They have been

Re: [Rd] Unexpected EOF in R-patched_2017-01-30

> Avraham Adler > on Tue, 31 Jan 2017 16:07:20 -0500 writes: > On Tue, Jan 31, 2017 at 3:30 PM, peter dalgaard wrote: >> >>> On 31 Jan 2017, at 18:56 , Avraham Adler wrote: >>> >>> Hello.

Re: [Rd] RFC: tapply(*, ..., init.value = NA)

> Suharto Anggono Suharto Anggono via R-devel > on Tue, 31 Jan 2017 15:43:53 + writes: > Function 'aggregate.data.frame' in R has taken a different route. With drop=FALSE, the function is also applied to subset corresponding to combination of grouping

Re: [R-pkg-devel] no visible global function definition for ‘par’

t;median", "model.tables", > | "na.action", "na.omit", "pf", "ts", "var") > | importFrom("utils", "read.table", "str", "tail", "write.table") > |

Re: [Rd] RFC: tapply(*, ..., init.value = NA)

>>>>> Henrik Bengtsson <henrik.bengts...@gmail.com> >>>>> on Fri, 27 Jan 2017 09:46:15 -0800 writes: > On Fri, Jan 27, 2017 at 12:34 AM, Martin Maechler > <maech...@stat.math.ethz.ch> wrote: >> >> > On Jan

Re: [Rd] RFC: tapply(*, ..., init.value = NA)

> Suharto Anggono Suharto Anggono via R-devel > on Fri, 27 Jan 2017 16:36:59 + writes: > The "no factor combination" case is distinguishable by 'tapply' with simplify=FALSE. >> D2 <- data.frame(n = gl(3,4), L = gl(6,2, labels=LETTERS[1:6]), N=3)

Re: [Rd] Undefined behavior of head() and tail() with n = 0

cations, and in my view, your advantages are not even getting close to counter-weigh the drawbacks. > On 26 January 2017 at 16:51, William Dunlap <wdun...@tibco.com> wrote: >> In addition, signed zeroes only exist for floating point numbers - the >> bit patt

Re: [Rd] RFC: tapply(*, ..., init.value = NA)

if(length(ans)) as.vector(NA, mode=storage.mode(ans[[1]])) else NA . A colleague proposed to use the shorter argument name 'default' instead of 'init.value' which indeed maybe more natural and still not too often used as "non-first" argument in FUN(.). Thank

[Rd] RFC: tapply(*, ..., init.value = NA)

Last week, we've talked here about "xtabs(), factors and NAs", -> https://stat.ethz.ch/pipermail/r-devel/2017-January/073621.html In the mean time, I've spent several hours on the issue and also committed changes to R-devel "in two iterations". In the case there is a *Left* hand side part to

Re: [Rd] Undefined behavior of head() and tail() with n = 0

ke to start differentiating it here... but of course we can continue discussing here if you like. Martin Maechler ETH Zurich and R Core > and the R head() and tail() functions are modeled after > their GNU counterparts, I would expect the R functions to > distinguish between +0 an

Re: [Rd] xtabs(), factors and NAs

>>>>> Milan Bouchet-Valat <nalimi...@club.fr> >>>>> on Thu, 19 Jan 2017 13:58:31 +0100 writes: > Hi all, > I know this issue has been discussed a few times in the past already, > but Martin Maechler suggested in a bug report [1] that I raise it

Re: [R-pkg-devel] multiple bibentry()s in CITATION

, e.g., > options(citation.bibtex.max = 1); citation(package = "copula") To cite the R package copula in publications use: Marius Hofert, Ivan Kojadinovic, Martin Maechler and Jun Yan (2017). copula: Multivariate Dependence with Copulas. R package version 0.999-16 URL https://CRAN.R-pro

Re: [Rd] accelerating matrix multiply

cite above, the current implementation was triggered by a nasty BLAS bug .. actually also showing up only on some platforms, possibly depending on runtime libraries in addition to the compilers used. Do you have R code (including set.seed(.) if relevant) to show on how to generate the large

Re: [Rd] seq.int/seq.default

>>>>> Martin Maechler <maech...@stat.math.ethz.ch> >>>>> on Thu, 5 Jan 2017 12:39:29 +0100 writes: >>>>> Mick Jordan <mick.jor...@oracle.com> >>>>> on Wed, 4 Jan 2017 08:15:03 -0800 writes: >> On 1/4/17 1:

Re: [Rd] seq.int/seq.default

> Mick Jordan > on Wed, 4 Jan 2017 12:49:41 -0800 writes: > On 1/4/17 8:15 AM, Mick Jordan wrote: > Here is another difference that I am guessing is unintended. >> y <- seq.int(1L, 3L, length.out=2) >> typeof(y) > [1] "double" >> x <-

Re: [Rd] seq.int/seq.default

>>>>> Mick Jordan <mick.jor...@oracle.com> >>>>> on Wed, 4 Jan 2017 08:15:03 -0800 writes: > On 1/4/17 1:26 AM, Martin Maechler wrote: >>>>>>> Mick Jordan <mick.jor...@oracle.com> >>>>>>> on

Re: [Rd] seq.int/seq.default

od not implemented for type 'symbol' which I find a very appropriate and helpful message > seq.int(to=quote(b), by=2) > Error in seq.int(to = quote(b), by = 2) : > 'to' cannot be NA, NaN or infinite which is true, as well, and there's no "default met

Re: [Rd] utils::ls.str(): Partial argument name 'digits' to seq() (should be digits.d?)

You are right (though picky). I have updated it now. Thank you Henrik! Martin > Should utils::ls.str() be updated as: > svn diff src/library/utils/R/str.R > Index: src/library/utils/R/str.R > === > --- src/library/utils/R/str.R

[Rd] structure(NULL, *) is deprecated [was: Unexpected I(NULL) output]

>>>>> Martin Maechler <maech...@stat.math.ethz.ch> >>>>> on Thu, 22 Dec 2016 10:24:43 +0100 writes: >>>>> Florent Angly <florent.an...@gmail.com> >>>>> on Tue, 20 Dec 2016 13:42:37 +0100 writes: >>

Re: [Rd] colnames for data.frame could be greatly improved

ic that do.NULL = FALSE is relatively slow? Shorter code *is* nicer than longer code, so I need a bit more conviction why we should add more code for that special case .. Martin Maechler, ETH Zurich > On 20 December 2016 at 01:27, Jan Gorecki <j.gore...@wit.edu.pl> wrote: > >

Re: [Rd] Unexpected I(NULL) output

actically noticeable. A last option would be 3/ The help page for I() could note what happens in the NULL case. That would be the least work for everyone, but at the moment, I tend to agree that '1/' is worth the pain to have R's structure() become more consistent. Martin Maechler ETH Zur

Re: [Rd] Very small numbers in hexadecimal notation parsed as zero

> Florent Angly > on Tue, 20 Dec 2016 13:26:36 +0100 writes: > Hi all, > I have noticed incorrect parsing of very small hexadecimal numbers > like "0x1.dp-987". Such a hexadecimal representation can > can be produced by sprintf()

Re: [Rd] Request: Increasing MAX_NUM_DLLS in Rdynload.c

at convincing to me... in so far as the general feeling is that memory should be cheap and limits should not be low. (In spite of Brian Ripleys good reasons against it, I'd still aim for a *dynamic*, i.e. automatically increased list here). Martin Maechler > Regards, > Steve Bronder

Re: [Rd] print.POSIXct doesn't seem to use tz argument, as per its example

> Jennifer Lyon > on Thu, 15 Dec 2016 09:33:30 -0700 writes: > On the documentation page for DateTimeClasses, in the Examples section, > there are the following two lines: > > format(.leap.seconds) # the leap seconds in your time zone >

Re: [Rd] New leap second end of 2016 / beginning 2017 (depending on TZ)

>>>>> Martin Maechler <maech...@stat.math.ethz.ch> >>>>> on Wed, 14 Dec 2016 17:04:22 +0100 writes: > As R is sophisticated enough to track leap seconds, > ?.leap.seconds > we'd need to update our codes real soon now again:

[Rd] New leap second end of 2016 / beginning 2017 (depending on TZ)

As R is sophisticated enough to track leap seconds, ?.leap.seconds we'd need to update our codes real soon now again: https://en.wikipedia.org/wiki/Leap_second (and those of you who want second precision in R in 2017 need to start working with 'R patched' or 'R devel' ...)

Re: [Rd] Strange behavior when using progress bar (Fwd: Re: [R] The code itself disappears after starting to execute the for loop)

Please Windows users .. this is possibly only for you! Note that I do *not* see problems on Linux (in ESS; did not try RStudio). Please also indicate in which form you are running R. Here it does depend if this is inside RStudio, ESS, the "Windows GUI", the "Windows terminal&qu

Re: [Rd] segfault with POSIXlt zone=NULL zone=""

> Joshua Ulrich > on Tue, 6 Dec 2016 09:51:16 -0600 writes: > On Tue, Dec 6, 2016 at 6:37 AM, wrote: >> Hi all, >> >> I ran into a segfault while playing with dates. >> >> $ R --no-init-file >> ... >> >

Re: [Rd] problem with normalizePath()

and why shouldn't Microsoft be the institution who can best judge how to do that, now that they sell a "Microsoft R" ?? !??!?!??!?!??!? (trying again with BCC; next time, I'll use CC). (a slowly increasingly frustrated) Martin Maechler ETH Zurich > Best, > Evan &

Re: [Rd] Different results for cos,sin,tan and cospi,sinpi,tanpi

>>>>> Martin Maechler <maech...@stat.math.ethz.ch> >>>>> on Thu, 1 Dec 2016 09:36:10 +0100 writes: >>>>> Ei-ji Nakama <nak...@ki.rim.or.jp> >>>>> on Thu, 1 Dec 2016 14:39:55 +0900 writes: >> Hi, >&g

Re: [Rd] Different results for cos,sin,tan and cospi,sinpi,tanpi

much Ei-ji Nakama, for this valuable contribution to make R better! Martin Maechler, ETH Zurich > -- > Best Regards, > -- > Eiji NAKAMA > "\u4e2d\u9593\u6804\u6cbb" __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] ifelse() woes ... can we agree on a ifelse2() ?

s 1 or is the same as the length of the result. For subassignment with value of length 1, recycling happens by itself and NA in index is OK. > It limits 'NA.' to be of length 1, considering 'NA.' just as a label for NA. > Cases where the last version above or 'ifelse2 or 'ifelseHW' in i

Re: [Rd] ifelse() woes ... can we agree on a ifelse2() ?

> Related to the length of 'ifelse' result, I want to say that "example of > different return modes" in ?ifelse led me to perceive a wrong thing in the > past. > ## example of different return modes: > yes <- 1:3 > no <- pi^(0:3) > typeof(ifelse(NA,yes, no)) # logical >

Re: [Rd] shared libraries: missing soname

l. To the issue: I also don't see what your point is. R works with these so libraries as intended in all cases as far as we know, and so I don't understand why anything needs to be changed. All these libraries "belong to R" and are tied to a specific version of R and are not be

Re: [Rd] ifelse() woes ... can we agree on a ifelse2() ?

ent proposal works for objects of class "Date", "POSIXct", "POSIXlt", "factor", "mpfr" (pkg 'Rmpfr') and hopefully for "sparseVector" (in a next version of the 'Matrix' pkg). Martin > On Tue, Nov 15, 2016 at 3:58 AM, Martin Mae

Re: [R-pkg-devel] Question about configure file and system requirements

me logic that you should not list 'Depends', 'Imports', 'Suggests', etc of those packages. Martin Maechler ETH Zurich > Asking this because the "configure" and system > requirements are already present in the imported packages, > so my configuration check

Re: [Rd] problem with normalizePath()

st such bugs and bug fixes? --> I'm BCC'ing this to one place at least. Best, Martin Maechler ETH Zurich > On Thu, Nov 17, 2016 at 2:28 PM, Laviolette, Michael < > michael.laviole...@dhhs.nh.gov> wrote: >> The packages "readxl" and "haven"

Re: [Rd] ifelse() woes ... can we agree on a ifelse2() ?

lt"), factors, and "mpfr" (the arbitrary-precision numbers in my package "Rmpfr") Also if you are not on github, you can quickly get to the ifelse2() definition : https://gist.github.com/mmaechler/9cfc3219c4b89649313bfe6853d87894#file-ifelse-def-r-L168 > Al

Re: [Rd] Missing objects using dump.frames for post-mortem debugging of crashed batch jobs. Bug or gap in documentation?

ce is that the global variable "g" is visible > within the function "f" in the first version, but not in the second > version. > > If I dump to a file and load and debug it then the search path through > the > frames is not the same during run time vs. debug ti

Re: [Rd] Missing objects using dump.frames for post-mortem debugging of crashed batch jobs. Bug or gap in documentation?

> nospam@altfeld-im de > on Sun, 13 Nov 2016 13:11:38 +0100 writes: > Dear R friends, to allow post-mortem debugging In my > Rscript based batch jobs I use >tryCatch( , error = function(e) { > dump.frames(to.file = TRUE) }) > to write

Re: [Rd] Memory leak with tons of closed connections

> Gábor Csárdi > on Sun, 13 Nov 2016 20:49:57 + writes: > Using dup() before fdopen() (and calling fclose() on the connection > when it is closed) indeed fixes the memory leak. > Thank you, Gábor! Yes I can confirm that this fixes the memory leak. I'm

Re: [Rd] Memory leak with tons of closed connections

> Gergely Daróczi > on Thu, 10 Nov 2016 16:48:12 +0100 writes: > Dear All, > I'm developing an R application running inside of a Java daemon on > multiple threads, and interacting with the parent daemon via stdin and > stdout. > Everything

Re: [Rd] Running package tests and not stop on first fail

>>>>> Hervé Pagès <hpa...@fredhutch.org> >>>>> on Mon, 7 Nov 2016 14:37:15 -0800 writes: > On 11/05/2016 01:53 PM, Martin Maechler wrote: >>>>>>> Oliver Keyes <ironho...@gmail.com> >>>>>>>

<    3   4   5   6   7   8   9   10   11   12   >