Re: [Rd] Documentation tweak for ?traceback

gt; 1: foo(2) > The attached trivial patch cleans up the example so that the above > looks like it would have under r<70207. Indeed, thanks a lot, Brodie! There was a bit more to change -- the options() setting is also mentioned in the main tex

Re: [Rd] Format printing inside a matrix

s", i.e., function calls with them as arguments is "forbidden" / "undefined" ... .. but your users will not follow what you told them, e.g., if your objects look closely like other R objects they already know very well ... } So, I'm convinced good programmer

Re: [Rd] Addition of a meta viewport tag to HTML manuals

rovided a small patch for using those instead of perl, I don't see a reason not to be grateful and apply it to the sources. Thank you once more Martin -- *) perl is mentioned twice in the "R Administration and Installation" manual: 1. maybe needed for 'install-info

Re: [Rd] Convert STRSXP or INTSXP to factor

> Gabriel Becker > on Mon, 15 Jul 2019 13:29:28 -0700 writes: > Hi Morgan, > So if the goal is output identical to calling factor, one thing youc an > do is construct and evaluate a call to the R-level factor function. That > would work and be guaranteed to meet y

Re: [Rd] Unexpected behaviour when comparing (==) long quoted expressions

sider that implementation of '==' which indeed does about the same thing as deparse {which also truncates at some point by default; something very very reasonable for error messages, but undesirable in other cases}. But I think it's fair expectation that comparing calls [&q

Re: [Rd] Minor typo in R-exts

t; directives". Results of a diff between R-exts.texi at SVN revision > 76864 and a corrected version are copied below. Thank you, Josh. Fixed in the sources now. Martin __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] Underscores in package names

27;s offer to find and provide patches for all places this is used in the R sources, we've convinced ourselves that there is much more code "out there", notably 'devops' code in scripts, which currently relies on the current package naming rules and which could break, often on

Re: [Rd] Conventions: Use of globals and main functions

functionality I'd rather have with a function that has several arguments and this behavior was switchable via = TRUE/FALSE , rather than with `<<-` which has always exactly 2 arguments. [This is my personal opinion only; other R Core members may well think differently about this]

Re: [Rd] '==' operator: inconsistency in data.frame(...) == NULL

t to treat NULL as if it was a zero-length atomic object (of "arbitrary" type/mode). 2b) data.frame()s "should typically" behave like matrices in many situations, notably when indexed {and that rule is violated (on purpose) by tibbles .. ("drop=FALSE"

[Rd] NiceBayes filtered "[ALTREP] ... return value ..."

ot;ham" message among the many dozens of spam ones only a day ago, and released it.. Martin Maechler ETH Zurich __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] head.matrix can return 1000s of columns -- limit to n or add new argument?

Gabe's proposal already back in July but was busy and/or vacationing then ... If you submit this with a patch (that includes changes to both *.R and *.Rd , including some example) as "wishlist" item to R's bugzilla, I'm willing/happy to check and commit this to R-devel.

Re: [Rd] Error: package or namespace load failed for ‘utils

n TRUE or FALSE, nothing else. > and if the case this would mean that R itself is an > unstable state (something at the C level that should not > have happened has happened) but this was not caught > earlier. yes.. something like that... My current d

Re: [Rd] head.matrix can return 1000s of columns -- limit to n or add new argument?

e() returning a character object, brief() returning the principal argument invisibly, the same as any "correct" print() method..} >From the above, I think it may make sense to entertain both a generalization of head() and one such a glance() / brief() /.. function which for a matrix s

Re: [Rd] '==' operator: inconsistency in data.frame(...) == NULL

" " identical(m01., m01. == NULL) # " " " identical(m01, m01 == 1) # < 0 x 1 matrix> w/o dimnames identical(m01, m01 == logical(0)) # < 0 x 1 matrix> identical(m01, m01 == NULL) # < 0 x 1 matrix> ##--- Best regards, Martin __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] '==' operator: inconsistency in data.frame(...) == NULL

>>>>> Martin Maechler >>>>> on Wed, 18 Sep 2019 10:35:42 +0200 writes: >>>>> Hilmar Berger >>>>> on Sat, 14 Sep 2019 13:31:27 +0200 writes: >> Dear all, >> I did some more tests regarding the ==

Re: [Rd] '==' operator: inconsistency in data.frame(...) == NULL

>>>>> Hilmar Berger >>>>> on Tue, 24 Sep 2019 19:31:51 +0200 writes: > Dear Martin, > thanks a lot for looking into this. Of course you were right that the > fix was not complete - I apologize for not having tested what I believed >

Re: [Rd] depending on orphaned packages?

])), but your proposal seems a "uniformly not worse" change ((and I have very much liked delving into parts of Gordon Smyth's textbook on GLMs as a really nice mixture / in-between of rigorous math and applied stats)) Martin Maechler ETH Zurich and R Core __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] missing imports not detected by 'R CMD check' (?)

the R CMD check tools have never warned me about (and so they are not in Matrix/NAMESPACE because Matrix may be older than namespaces, and even if not, originally, one did not import the the things from "Depends:" packages, where 'methods' had been for a long time in Ma

Re: [Rd] Improvement in hist command documentation

"histogram" object is constructed with a plot method, etc. Please look at the source code the development of which code is always visible here https://svn.r-project.org/R/trunk/src/library/graphics/R/hist.R But you are right that the \item{main, xlab, ylab

Re: [Rd] Wrong explanation on 'ylab' in hist.Rd

> suharto anggono--- via R-devel > on Sun, 6 Oct 2019 12:14:23 + writes: > Description of arguments main, xlab, ylab in hist.Rd in current R devel and R patched ends with this. > the default \code{ylab} is \code{"Frequency"} iff \code{probability} is true > In fact,

Re: [Rd] Strange "no-echo" in place of "slave"

resumably, "worker > thread" (or thereabouts) would be a better replacement. > -pd Yes indeed, thank you, Suharto, Gabe and Peter. I've updated the 2nd example (using "worker") Martin >> On 6 Oct 2019, at 14:00 , Gabriel Becker >> wrote:

Re: [Rd] head.matrix can return 1000s of columns -- limit to n or add new argument?

> Gabriel Becker > on Tue, 29 Oct 2019 12:43:15 -0700 writes: > Hi all, > So I've started working on this and I ran into something that I didn't > know, namely that for x a multi-dimensional (2+) array, head(x) and tail(x) > ignore dimension completely, treat x as an

Re: [Rd] head.matrix can return 1000s of columns -- limit to n or add new argument?

>>>>> Pages, Herve >>>>> on Thu, 31 Oct 2019 21:02:07 + writes: > On 10/30/19 04:29, Martin Maechler wrote: >>>>>>> Gabriel Becker >>>>>>> on Tue, 29 Oct 2019 12:43:15 -0700 writes: >>

Re: [Rd] head.matrix can return 1000s of columns -- limit to n or add new argument?

gt; attribute. ["of course", the word "prints" above should be replaced by "returns" ! ] > 7. 'unclass' returns (a copy of) its argument with its class > attribute removed. (It is not allowed for objects which cannot be > copied, na

[Rd] class() |--> c("matrix", "arrary") [was "head.matrix ..."]

nce bad and you should very often not replace class(x) by class(x)[1] but really use the "only truly correct" ;-) inherits(x, "...") or is(x, "") # if you're advanced/brave enough (:-) to # use formal classes (S4) Martin Maechler ETH Zurich and R Core Team __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] class() |--> c("matrix", "arrary") [was "head.matrix ..."]

>>>>> Duncan Murdoch >>>>> on Sun, 10 Nov 2019 11:48:26 -0500 writes: > On 10/11/2019 9:17 a.m., Bryan Hanson wrote: >> >> >>> On Nov 10, 2019, at 3:36 AM, Martin Maechler wrote: >>> >>>&g

Re: [Rd] class() |--> c("matrix", "arrary") [was "head.matrix ..."]

>>>>> Pages, Herve >>>>> on Thu, 14 Nov 2019 19:13:47 + writes: > On 11/14/19 05:47, Hadley Wickham wrote: >> On Sun, Nov 10, 2019 at 2:37 AM Martin Maechler >> wrote: >>> >>>>>>

[Rd] _R_CHECK_LENGTH_1_LOGIC2_ setting and Rstudio ..

>>>>> Martin Maechler >>>>> on Fri, 15 Nov 2019 17:31:15 +0100 writes: > as ((strongly recommended by me for package developers !)) > _R_CHECK_LENGTH_1_CONDITION_=true > _R_CHECK_LENGTH_1_LOGIC2_=verbose Apropos, for many months no

Re: [Rd] BUG?: A copy of base::`+` (primitive) is not a clone but a "pointer"

> Henrik Bengtsson > on Sun, 17 Nov 2019 14:31:07 -0800 writes: > $ R --vanilla R version 3.6.1 (2019-07-05) -- "Action of > the Toes" Copyright (C) 2019 The R Foundation for > Statistical Computing Platform: x86_64-pc-linux-gnu > (64-bit) ... >> str(base::`+`)

Re: [Rd] Suggestion: Make _R_CHECK_LENGTH_1_LOGIC2_=warn the default for R 3.6.2

of the upcoming class() |--> c("matrix", "array") change --- has actually *not* been part of the '--as-cran' checks, nor (AFAIK, but I don't really know) of extra CRAN incoming checks. I'm proposing to add _R_CHECK_LENGTH_1_CONDITION_=true to the --as

Re: [Rd] BUG?: A copy of base::`+` (primitive) is not a clone but a "pointer"

>>>>> Tomas Kalibera >>>>> on Mon, 18 Nov 2019 09:36:14 +0100 writes: > On 11/18/19 9:18 AM, Martin Maechler wrote: >>>>>>> Henrik Bengtsson >>>>>>> on Sun, 17 Nov 2019 14:31:07 -0800 writes: >

Re: [Rd] Inappropriate class(o)[!inherits(o,"AsIs")] in get_all_vars

inherits(o,"AsIs")] removes all elements of class(o), giving character(0). Thank you, Suharto ! You are obviously right, and I'm a bit embarrassed by my overzealousness to follow my own recommendations in the R Blog http://bit.ly/R_blog_class_think_2x {*wrongly*: The recommendati

Re: [Rd] Inappropriate class(o)[!inherits(o,"AsIs")] in get_all_vars

>>>>> Martin Maechler >>>>> on Mon, 18 Nov 2019 12:15:38 +0100 writes: >>>>> suharto anggono--- via R-devel >>>>> on Sun, 17 Nov 2019 10:34:31 + writes: >> SVN revision 77401 changes >> x[isM

[Rd] class() |--> c("matrix", "arrary") -- and S3 dispatch

TLDR: This is quite technical, still somewhat important: 1) R 4.0.0 will become a bit more coherent: a matrix is an array 2) Your package (or one you use) may be affected. >>>>> Martin Maechler >>>>> on Fri, 15 Nov 2019 17:31:15 +0100 writes: &g

Re: [Rd] BUG?: A copy of base::`+` (primitive) is not a clone but a "pointer"

> Benjamin Tyner > on Mon, 25 Nov 2019 22:34:33 -0500 writes: > For what it's worth, the current behavior seems to have begun starting > with version 3.6.0. If I run in version 3.5.3: >> p1 <- .Primitive('+') ; p2 <- p1 ; attr(p1, "myattr") <- 1 ; p2 > function (e1,

Re: [Rd] Troubles using numeric in s4 class union

ass.R, line 809 > 3. Why should the class union I defined interfere with the inner workings > of a separate package? There is no good reason ... > 4. Is this a bug in Base or Methods? This is a bug in "base R", in package 'methods'. The R core team had taken the issue up, already two weeks ago, but unfortunately did not get to address this in a definitive way. ==> I'll remind us about it ! Martin Maechler ETH Zurich and R Core > Thank you for your time! > > Sincerely, > Ezra __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] head.matrix can return 1000s of columns ..

r" attributes: inherits(print(t.ij <- M[(n-2):n, 2:3] ), class(M)) ## now, the "foo" attribute of M[i,j] is gone! is.null(attr(t.ij, "foo")) }) } chkMat(treeS) chkMat(as.matrix(treeS)) --- And (

Re: [Rd] Inappropriate class(o)[!inherits(o,"AsIs")] in get_all_vars

anch/src/library/stats/R/models.R). It > was ported to R patched by r77402. You are right.... it's no longer now, thank you very much, Suharto! Martin > On Monday, 18 November 2019, 8:12:10 PM GMT+7, Martin Maechler > wrote: >>>>>> Marti

Re: [Rd] long vector support

take much effort; my first try seems to work already .. and may just a bit more safeguarding .. So thank you, Will, for the reminder! Martin Maechler ETH Zurich and R Core Team > x <- raw(2^31) > writeBin(x, con = nullfile()) > # Error in writeBin(x, con = nullfi

Re: [Rd] Inconsistencies in wilcox.test

> Karolis Koncevičius > on Sat, 7 Dec 2019 20:55:36 +0200 writes: > Hello, > Writing to share some things I've found about wilcox.test() that seem a > a bit inconsistent. > 1. Inf values are not removed if paired=TRUE > # returns different results (Inf is removed

Re: [Rd] What should dnorm(0, 0, -Inf) return?

f(!R_FINITE(x) && mu == x) return ML_NAN;/* x-mu is NaN */ > if (sigma == 0) >return (x == mu) ? ML_POSINF : R_D__0; > x = (x - mu) / sigma; > (Ping Martin...) I think you are spot on, Peter. All of this code has a longish history, with incremental bo

Re: [Rd] Inconsistencies in wilcox.test

x.test() printouts would slightly change, e.g., > w0 <- wilcox.test( 1:5, 4*(0:4), paired=TRUE) Wilcoxon signed rank exact test data: 1:5 and 4 * (0:4) V = 1, p-value = 0.125 alternative hypothesis: true location shift is not equal to 0 where before (in R <= 3.6.x) it

Re: [Rd] Build failure on powerpc64

OUBLE && (SIZEOF_LONG_DOUBLE > SIZEOF_DOUBLE) connections.c4514:#if HAVE_LONG_DOUBLE && (SIZEOF_LONG_DOUBLE > SIZEOF_DOUBLE) connections.c4592:#if HAVE_LONG_DOUBLE && (SIZEOF_LONG_DOUBLE > SIZEOF_DOUBLE) format.c250:#if defined(HAVE_LONG_DOUBLE) && (SIZEOF_LONG_DOUB

Re: [Rd] Inconsistencies in wilcox.test

>>>>> Martin Maechler >>>>> on Thu, 12 Dec 2019 17:20:47 +0100 writes: >>>>> Karolis Koncevičius >>>>> on Mon, 9 Dec 2019 23:43:36 +0200 writes: >> So I tried adding Infinity support for all cases. And it &

Re: [Rd] Build failure on powerpc64

_DOUBLE > SIZEOF_DOUBLE) +# ifdef __PPC64__ + // PowerPC 64 (when gcc has -mlong-double-128) fails constant folding with LDOUBLE +# define q_1_eps (1 / LDBL_EPSILON) +# else static LDOUBLE q_1_eps = 1 / LDBL_EPSILON; +# endif #else static double q_1_eps = 1 / DBL_EPSILON; #endif - ---

Re: [Rd] head/tail breaking change

Indeed, Gabe's explanation is right-on-spot: With the generalization of head() / tail(), we really found it undesirable to stay "internally inconsistent". We do have to grab the chance for not-quite-back-compatible improvements -- when the costs look comparably small -- for R

Re: [Rd] best way to build from Git

> Gábor Csárdi > on Thu, 26 Dec 2019 08:23:10 + writes: > Hi Frederick, I know some non R-core people use this > workflow to keep local patches in git branches: > https://bookdown.org/lionel/contributing/ > Best, Gabor Thank you, Gabor, and notably, Lionel, for p

[Rd] Another wish (?) for R 4.0.0: print(*, width = )

e work myself, I'd quickly wanted to hear opinions / caveats / .. about this. wishing you all a Happy New Year, Martin Martin Maechler ETH Zurich and R Core Team __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] Another wish (?) for R 4.0.0: print(*, width = )

I'm not proposing to touch show(). Very often when working with S4 objects, I devise a sophisticated print() method, with defaults, (often times "smart", i.e. depending on other arguments) for all but the first argument and then the show() method just calls that print method. Best,

Re: [Rd] as-cran issue ==> set _R_CHECK_LENGTH_1_* settings!

> Ben Bolker > on Mon, 13 Jan 2020 11:49:09 -0500 writes: > From R NEWS (changes in 3.6.0) > Experimentally, setting environment variable _R_CHECK_LENGTH_1_LOGIC2_ > will lead to warnings (or errors if the variable is set to a ‘true’ > value) when && or || encounter an

Re: [Rd] as-cran issue ==> set _R_CHECK_LENGTH_1_* settings!

e software, say, Emacs, or Rstudio) on Windows. I do want to entice people to have a long look beyond closed source OS into the world of Free Software where not only R is FOSS (Free and Open Source Software) but (all / almost) all the tools you use are of that same spirit. Best, Martin &g

Re: [Rd] [External] Re: rpois(9, 1e10)

ould be considerably larger than double.max unless on Windows, where the wise men at Microsoft decided to keep their workload simple by defining "long double := double" - as 'long double' unfortunately is not well defined by C standards) Martin > On 2020-01-19 21:0

Re: [Rd] Minor bug in error message in datetime.c

error(_("invalid '%s' argument"), "x"); > + error(_("invalid '%s' argument"), "format"); > One could spend quite some time figuring out what is wrong with his “x”, when the problem is with “format” :) Thank you

Re: [Rd] [External] Re: rpois(9, 1e10)

>>>>> Benjamin Tyner >>>>> on Mon, 20 Jan 2020 08:10:49 -0500 writes: > On 1/20/20 4:26 AM, Martin Maechler wrote: >> Coming late here -- after enjoying a proper weekend ;-) -- >> I have been agreeing (with Spencer, IIUC) on this for a

Re: [Rd] [External] Re: rpois(9, 1e10)

at down and implemented it .. and it seemed to work perfectly: Returning the same random numbers as now, but switching to use double (instead of returning NAs) when the values are too large. I'll probably commit that to R-devel quite soonish. Martin > On 2020-01-20 12:33 p.m., Martin Maechler

Re: [Rd] as-cran issue ==> set _R_CHECK_LENGTH_1_* settings!

are) but (all / almost) all the >> tools you use are of that same spirit. >> >> Best, >> Martin > I've reconsidered. > You're 100% correct. Thank you. > I'm planning to try ReactOS. > (Hope it works...) >

Re: [Rd] [External] Re: rpois(9, 1e10)

>>>>> Martin Maechler >>>>> on Tue, 21 Jan 2020 09:25:19 +0100 writes: >>>>> Ben Bolker >>>>> on Mon, 20 Jan 2020 12:54:52 -0500 writes: >> Ugh, sounds like competing priorities. > indeed. >> * ma

Re: [Rd] [External] Re: rpois(9, 1e10)

>>>>> Martin Maechler >>>>> on Tue, 21 Jan 2020 09:25:19 +0100 writes: >>>>> Ben Bolker >>>>> on Mon, 20 Jan 2020 12:54:52 -0500 writes: >> Ugh, sounds like competing priorities. > indeed. >> * ma

Re: [Rd] Memory error in the libcurl connection code

); > > Best, > Gabor Thanks a lot, Gábor! I can reproduce the problem (on Linux Fedora 30) and confirm that your patch works. Even more, the patch looks "almost obvious", because ctxt->current = ctxt->buf happens earlier in rcvData() after a change to ctxt->buf and so should be updated if buf is. An even slightly "better" patch just moves that statement down to after the if(add) { .. } clause. I'll patch the sources, and will port to 'R 3.6.2 patched'. Martin __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] [External] Re: rpois(9, 1e10)

>>>>> Benjamin Tyner >>>>> on Thu, 23 Jan 2020 08:16:03 -0500 writes: > On 1/20/20 12:33 PM, Martin Maechler wrote: >> >> It's really something that should be discussed (possibly not >> here, .. but then I'v

Re: [Rd] class() |--> c("matrix", "arrary") -- and S3 dispatch

>>>>> Pages, Herve >>>>> on Tue, 21 Jan 2020 17:33:01 +0000 writes: > Dear Martin, > What's the ETA for _R_CLASS_MATRIX_ARRAY_=TRUE to become the new > unconditional behavior in R devel? Thanks! > H. Thank you, Hervé, for

Re: [Rd] matplot.Date & matplot.POSIXct

- Users of matplot() {& matlines() & matpoints()} who may have to adopt their calls to these functions {I'm pretty sure all three would have to change for consistency}. - and then, there are quite a few other changes, bug assignments to which I have committed which shoul

Re: [Rd] matplot.Date & matplot.POSIXct

>>>>> Spencer Graves >>>>> on Tue, 28 Jan 2020 17:24:14 -0600 writes: > On 2020-01-28 05:13, Martin Maechler wrote: >>>>>>> Spencer Graves >>>>>>> on Mon, 27 Jan 2020 23:02:28 -0600 writes: >

Re: [Rd] Stroring and extracting AICs from an ARIMA model using a nested loop

lease do *NOT* misuse it for R-help questions in the future: These should go to the R-help mailing list instead! Best, Martin Maechler >> On Feb 3, 2020, at 3:47 AM, Rui Barradas wrote: >> >> Hello, >> >> You can solve the problem in two dif

[Rd] round(x, dig) [was "Development version of R fails tests .."]

t version of the vignette is also available as https://stat.ethz.ch/~maechler/R/Rounding.html You can install and load the devel version of 'round' by remotes::install_gitlab("mmaechler/round") require("round") and then look a bit at the different versions of round(.) using example(roundX) i.e. using round::roundX(x, digits, version) For those who read so far: I'm really interested in getting critical (constructive) feedback and comments about what I've written there (in the bugzilla report, and the package vignette). It seems almost nobody till now has had much interest and time to delve into the somewhat intriguing issues. Best regards, Martin Maechler ETH Zurich and R Core team __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] dimnames incoherence?

if you confirm you'd want in a private e-mail). > Best, > Serguei. > PS the same apply for dimnames(a)[[2]]<-. (of course) NB *and* importantly, the buglet is still in current versions of R Best, Martin >> sessionInfo() > R version 3.6

Re: [Rd] dimnames incoherence?

>>>>> Martin Maechler >>>>> on Wed, 19 Feb 2020 18:06:57 +0100 writes: >>>>> Serguei Sokol >>>>> on Wed, 19 Feb 2020 15:21:21 +0100 writes: >> Hi, >> I was bitten by a little incoherence in dimnames assignm

[Rd] capabilities(), was [R-pkg-devel] ... No protocol specified (OS X only)

n(e) FALSE) } } z } and as an afterthought rather improve the argument's default, from Xchk = TRUE to Xchk = is.null(what) || any(c("X11", "jpeg", "png", "tiff") %in% what) (or similar smart defaults). Then, e.g

Re: [Rd] trivial typo in man page Quote.Rd

de{...} any character > sequence, except that it must not contain the closing sequence > - \samp{)"}. The delimiter pairs \code{[]} and \code{\{\}} ran also be > + \samp{)"}. The delimiter pairs \code{[]} and \code{\{\}} can also be > Thank you, Ben.

Re: [Rd] dimnames incoherence?

would be another good thing about the change. > I have seen users use [[<- where [<- is more appropriate in cases like > this. Should there be a way to generate warnings about the change in > behavior as you've done with other syntax changes? Well, good question

[Rd] Change 77844 breaking pkgs [Re: dimnames incoherence?]

>>>>> Martin Maechler >>>>> on Sat, 22 Feb 2020 20:20:49 +0100 writes: >>>>> William Dunlap >>>>> on Fri, 21 Feb 2020 14:05:49 -0800 writes: >> If we change the behavior NULL--[[--assignment from

Re: [Rd] tcl problem with R-3.6.3?

[9] LC_ADDRESS=C LC_TELEPHONE=C [11] LC_MEASUREMENT=de_CH.UTF-8 LC_IDENTIFICATION=C attached base packages: [1] graphics grDevices datasets stats utils methods base other attached packages: [1] fortunes_1.5-4 sfsmisc_1.1-5 loaded vi

Re: [Rd] dput()

ot; so new "all" is current c("all", "digits17") {in a way such that c("all", "hexNumeric") implicitly removes "digits17" (as it's in contradiction with "hexNumeric"). 2) add a new option "AllHex"

Re: [Rd] dput()

>>>>> Duncan Murdoch >>>>> on Mon, 2 Mar 2020 04:43:53 -0500 writes: > On 02/03/2020 3:24 a.m., Martin Maechler wrote: >>>>>>> robin hankin >>>>>>> on Sun, 1 Mar 2020 09:26:24 +1300 writes: >>

Re: [Rd] dput()

>>>>> Martin Maechler >>>>> on Mon, 2 Mar 2020 15:36:51 +0100 writes: >>>>> Duncan Murdoch >>>>> on Mon, 2 Mar 2020 04:43:53 -0500 writes: >> On 02/03/2020 3:24 a.m., Martin Maechler wrote: >>&

Re: [Rd] findInterval Documentation Suggestion

of the question. Extending that very long first sentence "Given length(v)'. by adding some helper words or other means may be fine and indeed an improvement, .. so I'm happy for another try. Martin > Obviously you would be right to question whether someone who

Re: [Rd] help with rchk warnings on Rf_eval(Rf_lang2(...))

> Ben Bolker > on Mon, 23 Mar 2020 17:07:36 -0400 writes: > Thanks, that's really useful. One more question for you, or someone > else here: > const ArrayXd glmLink::linkFun(const ArrayXd& mu) const { > return as(::Rf_eval(::Rf_lang2(as(d_linkFun), > as(Rcpp::Nu

Re: [Rd] Build failure on powerpc64

>>>>> Martin Maechler >>>>> on Tue, 17 Dec 2019 11:25:31 +0100 writes: >>>>> Tom Callaway >>>>> on Fri, 13 Dec 2019 11:06:25 -0500 writes: >> An excellent question. It is important to remember two key &g

Re: [Rd] contribution to package graphics::barplot

mail software from the rare group where you *can* specify the MIME type, I attach it here, for you and all readers. Best regards, Martin Maechler > Thanks in advance, > Best regards # File src/library/graphics/R/barplot.R # Part of the R package, https://www.R-project.org # # Cop

Re: [Rd] unstable corner of parameter space for qbeta?

pbetaI(). Yes, it's intriguing ... and I'll look into your special findings a bit later today. > Should I report this on the bug list? Yes, please. Not all problem of pbeta() / qbeta() are part yet, of R's bugzilla data base, and maybe this will help to draw more good applied

Re: [Rd] unstable corner of parameter space for qbeta?

led working of the function whose zero(s) are sought, i.e., pbeta() > Ben: Do you have an idea of parameter region where approximation is poor? > I think that it would be smart to focus on that to start with. Rmpfr matrix-/vector - products:

Re: [Rd] unstable corner of parameter space for qbeta?

___ > From: R-devel on behalf of J C Nash > Sent: Thursday, March 26, 2020 10:40:05 AM > To: Martin Maechler > Cc: r-devel@r-project.org > Subject: Re: [Rd] unstable corner of parameter space for qbeta? > Despite the need to focus on pbeta, I'm still

Re: [Rd] Plotmath on Fedora 31 broken with with pango >= 1.44 - workarounds?

> Paul Murrell > on Tue, 31 Mar 2020 09:41:30 +1300 writes: > Hi > On 30/03/20 10:43 pm, Iñaki Ucar wrote: >> On Mon, 30 Mar 2020 at 04:24, Paul Murrell wrote: >>> >>> Hi >>> >>> I have created an R branch that contains a potential fix ... >>>

[Rd] Help useRs to use R's own Time/Date objects more efficiently

27;t be hard for useRs themselves to see how to do... But then I see that "everybody" uses extension packages instead, even in the many situations where there's no gain doing so, but rather increases the dependency-complexity of the data analysis unnecessarily. Martin Maechler ETH Zurich and R Core Team. __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] missing binaries in R-devel windows snapshot 78175

> Jeroen Ooms > on Fri, 10 Apr 2020 08:54:39 +0200 writes: > On Fri, Apr 10, 2020 at 2:42 AM Bravington, Mark (Data61, > Hobart) wrote: >> >> > On Thu, Apr 9, 2020 at 12:44 PM Bravington, Mark >> (Data61, Hobart) > >> wrote: >> > > >> > > The "r-deve

Re: [Rd] stringsAsFactors

). Is this intentional? No! Thanks a lot for testing R 4.0.0 alpha/beta, noticing and alerting us about it. This will be changed ASAP. ... and it will benefit the whole R user community if quite a few good R users (as most readers of 'R-devel') would sta

Re: [Rd] Long model specification causes aov() to abort with error

I'll look at the cases etc and will use your proposals. (The only question for now: why did you not take the extra step and ask for R-bugs registration and do a regular bug report -> https://www.r-project.org/bugs.html ) Thanks again, Martin Maechler ETH Zurich and R Core Team

Re: [Rd] stringsAsFactors

>>>>> Hugh Parsonage >>>>> on Mon, 13 Apr 2020 21:20:26 +1000 writes: > Further, in addition to the `val <- FALSE` patch a few hours ago by > Martin, the line after should also be changed > - if(!is.logical(val) || is.na(val) || len

Re: [Rd] stringsAsFactors and type.convert()

ction, for a long time has ended with Since this is a helper function, the caller should always pass an appropriate value of 'as.is'. If useRs and package authors have followed this advice, they won't be bitten at all. Best regards, Martin __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] stringsAsFactors and type.convert()

>>>>> Arni Magnusson >>>>> on Mon, 20 Apr 2020 16:50:16 +0000 writes: > Dear Martin, > Thank you for the well-reasoned response. I realized I was rather late to make this suggestion for 4.0.0, changing a somewhat low-level function that can indee

Re: [Rd] paste(character(0), collapse="", recycle0=FALSE) should be ""

# is character(0) paste(c("4", "5"), "th", sep = "", collapse = ", ", recycle0 = FALSE) # is "4th, 5th" paste(c("4" ), "th", sep = "", collapse = ", ", recycle0 = FALSE) # is "4th" paste(c(), "th", sep = "", collapse = ", ", recycle0 = FALSE) # is "th" ## paste(c("4", "5"), "th", sep = "", collapse = ", ", recycle0 = TRUE) # is "4th, 5th" paste(c("4" ), "th", sep = "", collapse = ", ", recycle0 = TRUE) # is "4th" paste(c(), "th", sep = "", collapse = ", ", recycle0 = TRUE) # is character(0) There must be a lapsus / misunderstanding somewhere. I don't see any problem in the new behavior for now. Best regards, Martin __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] defining r audio connections

g the version of the API, as advised in the header file!) Martin Morgan On 5/6/20, 2:26 PM, "R-devel on behalf of Duncan Murdoch" wrote: On 06/05/2020 1:09 p.m., frede...@ofb.net wrote: > Dear R Devel, > > Since Linux moved away from using a file-system interfac

Re: [Rd] defining r audio connections

ages I personally would implement a connection. (I mistakenly thought this was a more specialized mailing list; I wouldn't have posted to R-devel on this topic otherwise) Martin Morgan On 5/6/20, 4:12 PM, "Gábor Csárdi" wrote: AFAIK that API is not allowed on CRAN. It triggers

Re: [Rd] S3 method dispatch for methods in local environments

still prints: [1] "1.0" "2.0" "3.0" "4.0" > But since R 4.0.0, this no longer words and the above prints: > $y > [1] 1 2 3 4 > attr(,"class") > [1] "myclass" > Is this intended? y

Re: [Rd] justify hard coded in format.ftable

ings are more exciting - we have not used ftable much/at all and are not interested. Even though the first 2 apply to me, I'll have a 2nd look into your post now, and may end up well agreeing with your proposal. Martin Maechler ETH Zurich and R Core team >> Dear all, >>

Re: [Rd] edit() doubles backslashes when keep.source=TRUE

prise such as Rstudio (viz the bug report 17800 above), but also others could really help by starting to use the "next version" of R on a routine basis ... Still: Thank you, of course, Bill Dunlap, and Sebastian and Jonathan (PR 17800) Martin > Am 15.05.20 um 03:50 sch

[Rd] ftable <-> data.frame etc {was "justify hard coded in format.ftable"}

1] as.data.frame as.matrix as.table formathead print [7] tail see '?methods' for accessing help and source code > methods(class = "table") [1] [ aperm as.data.frame Axis coerce initialize [7] li

Re: [Rd] failed check in reg-tests-1b.R

es sense to disregard R_LIBS in such situations. For building (and checking!) R itself from the sources, it may seem to make sense indeed if such environment variables would be temporarily unset (by one of the Makefiles, say). Martin __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] paste(character(0), collapse="", recycle0=FALSE) should be ""

ld only ever apply to the action of 'sep' but not the action of 'collapse'. 1) Bill and Hervé (I think) propose that 'recycle0' should have no effect whenever 'collapse = ' 2) Gabe proposes that 'collapse = ' and 'recycle0 = TRUE'

Re: [Rd] Should 0L * NA_integer_ be 0L?

> Michael Chirico > on Sat, 23 May 2020 18:08:22 +0800 writes: > I don't see this specific case documented anywhere (I also tried to search > the r-devel archives, as well as I could); the only close reference > mentions NA & FALSE = FALSE, NA | TRUE = TRUE. And there's al

<    1   2   3   4   5   6   7   8   9   10   >