Re: [Rd] encoding argument of source() in 3.5.0

> peter dalgaard > on Sun, 3 Jun 2018 23:51:24 +0200 writes: > Looks like this actually comes from readLines(), nothing > to do with source() as such: In current R-devel (still): >> f <- file("http://home.versanet.de/~s-berman/source2.R";, encoding="UTF-8") >> readLi

Re: [Rd] encoding argument of source() in 3.5.0

It's not Windows-specific, though. My example was on a Mac... I hope we can sort this out before 3.5.1. -pd > On 4 Jun 2018, at 10:44 , Martin Maechler wrote: > > So it seems as if the bug is in the file() [or url()] C code .. > But then we also have to consider Windows .. where I think most c

Re: [Rd] encoding argument of source() in 3.5.0

On Mon, 4 Jun 2018 10:44:11 +0200 Martin Maechler wrote: >> peter dalgaard >> on Sun, 3 Jun 2018 23:51:24 +0200 writes: > > > Looks like this actually comes from readLines(), nothing > > to do with source() as such: In current R-devel (still): > > >> f <- file("http://ho

Re: [Rd] encoding argument of source() in 3.5.0

On R 3.5.0 (Mac) The issue appears when using the default (libcurl) method and specifying the encoding Note that using method='internal' causes a segfault if used in conjunction with encoding. (and works when encoding is not set) urlR <- "http://home.versanet.de/~s-berman/source2.R"; # wor

Re: [Rd] aic() component in GLM-family objects

> Ben Bolker > on Sun, 3 Jun 2018 17:33:18 -0400 writes: > Is it generally known/has it been previously discussed here that the > $aic() component in GLM-family objects (e.g. results of binomial(), > poisson(), etc.) does not as implemented actually return the AIC, but

[Rd] Byte-compilation failure on different architectures / low-memory systems

As you may know, I look after the R package for Debian. My fellow Debianers make me follow a specific protocol -- a so-called "transition" in which all dependent packages on an identified potential breakge are rebuilt under the new (potentially breaking) change. We started adding an r-api-3.4 tag

Re: [Rd] Byte-compilation failure on different architectures / low-memory systems

I believe a reproducible example is to simply have a very large object defined literally (i.e. through structure() etc) in ./R/ . For example, fBasics has a couple of files test-jbLM.R and test-jbTable.R which are about 500 KB. For a given amount of RAM, I believe any sufficiently large file will a

Re: [Rd] Byte-compilation failure on different architectures / low-memory systems

Hi Dirk, thanks for the report. Access to the test system is not necessary, the memory requirements of the byte-code compiler are usually platform-independent and specifically with this package I can reproduce they are very high. We'll have a look what we can do, certainly there should at lea

Re: [Rd] user macros with multi-line arguments in Rd (was Re: Rd parser throws error for user macros invoked with empty argument)

Now in R-devel, Best, Tomas On 06/01/2018 11:33 AM, Tomas Kalibera wrote: Thanks for the report, I am testing a patch that will allow multi-line arguments to user macros. Best Tomas On 05/25/2018 04:45 PM, Georgi Boshnakov wrote: While on the topic of Rd macro arguments, it seems that  if a

Re: [Rd] Understanding the sequence of events when calling the R dpois function

Hi Jason, Duncan Temple Lang answered a similar question for me last year and wrote up the method here: http://dsi.ucdavis.edu/Notes/R/FindingNativeCodeInR.html Basically the C level debugger can be very helpful for figuring out what's happening. Best, Clark On Fri, Jun 1, 2018 at 4:47 AM, Jaso