Re: [Rd] R for Windows FAQ

https://cran.r-project.org/bin/windows/base/old/ Tomas On 6/3/24 21:30, Rubiana Viana wrote: Hi! How can I get older versions of R software? Thank you! __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] Segfault when parsing UTF-8 text with srcrefs

On 5/28/24 20:41, Tomas Kalibera wrote: On 5/28/24 19:35, Hadley Wickham wrote: Hi all, When I run the following code, R segfaults: text <- "×" srcfile <- srcfilecopy("test.r", text) parse(textConnection(text), srcfile = srcfile) It doesn't segfault if text is

Re: [Rd] [External] Re: Segfault when parsing UTF-8 text with srcrefs

compiler_4.3.0 On Tue, May 28, 2024 at 7:42 PM Tomas Kalibera wrote: This email originated outside the University. Check before clicking links or attachments. On 5/28/24 19:35, Hadley Wickham wrote: > Hi all, > > When I run the following code, R seg

Re: [Rd] Segfault when parsing UTF-8 text with srcrefs

On 5/28/24 19:35, Hadley Wickham wrote: Hi all, When I run the following code, R segfaults: text <- "×" srcfile <- srcfilecopy("test.r", text) parse(textConnection(text), srcfile = srcfile) It doesn't segfault if text is ASCII, or it's not wrapped in textConnection, or srcfile isn't set.

Re: [Rd] FR: Customize background colour of row and column headers for the View output

I think we should do more than this trivial change. The two real dialogs used by the data editor would then also get the new background color (setting the cell width, the "variable" editor). Then, the code clearly distinguishes between cells for names (row, column) and cells for data, so

Re: [R-pkg-devel] Flex missing in win-builder

On 5/28/24 06:18, drc via R-package-devel wrote: Is it possible to get flex in the win-builder windows environment? It's present in the debian environment. My package depends on cmake, bison, and flex. Each of these are listed in the `SystemRequirments` field of my DESCRIPTION file but flex

Re: [Rd] Output pipes to TTY hang

On 5/20/24 07:36, Zafer Barutcuoglu wrote: Hi, I am seeing this on Linux as well as MacOS: Opening any output pipe from R 4.4.0 to TTY programs like "less"/"more" hangs, SIGINT-proof: $ R/4.4.0/bin/Rscript -e 'pipe("less", "w")' $ R/4.4.0/bin/Rscript -e 'cat("test", file="|less") $

Re: [R-pkg-devel] Fwd: using portable simd instructions

ire aligned operands (on the stack), aligned at 32-byte boundary. Tomas Op di 26 mrt 2024 om 15:51 schreef Tomas Kalibera : On 3/26/24 10:53, jesse koops wrote: Hello R-package-devel, I recently got inspired by the rcppsimdjson package to try out simd registers. It works fantastic on my computer bu

Re: [R-pkg-devel] using portable simd instructions

On 3/26/24 10:53, jesse koops wrote: Hello R-package-devel, I recently got inspired by the rcppsimdjson package to try out simd registers. It works fantastic on my computer but I struggle to find information on how to make it portable. It doesn't help in this case that R and Rcpp make

Re: [Rd] Tcl socket server (tcltk) does not work any more on R 4.3.2

On 2/21/24 08:01, webmail.gandi.net wrote: Thank you, Ivan for this investigation. I inspected the R changes file (https://cran.r-project.org/doc/manuals/r-devel/NEWS.html) and found nothing about this. I should inspect the sources too! It could possibly break other Tcl/Tk related stuff.

Re: [Rd] certain pipe() use cases not working in r-devel

On Thu, Feb 15, 2024 at 8:02 AM Tomas Kalibera wrote: On 2/14/24 23:43, Jennifer Bryan wrote: > Hello, > > I've noticed a specific type of pipe() usage that works in released R, but > not in r-devel. > > In 4.3.2 on macOS, I can write to a

Re: [Rd] certain pipe() use cases not working in r-devel

On 2/14/24 23:43, Jennifer Bryan wrote: Hello, I've noticed a specific type of pipe() usage that works in released R, but not in r-devel. In 4.3.2 on macOS, I can write to a connection returned by pipe(), i.e. "hello, world" prints here: R.version.string [1] "R version 4.3.2 (2023-10-31)"

Re: [Rd] certain pipe() use cases not working in r-devel

On 2/15/24 14:09, Ivan Krylov via R-devel wrote: В Wed, 14 Feb 2024 14:43:12 -0800 Jennifer Bryan пишет: But in r-devel on macOS, this is silent no-op, i.e. "hello, world" does not print: R.version.string [1] "R Under development (unstable) (2024-02-13 r85895)" con <- pipe("cat")

Re: [R-pkg-devel] New Package Removal because Shared Library Too Large from Debugging Symbols

On 1/22/24 15:42, Ivan Krylov via R-package-devel wrote: On Mon, 22 Jan 2024 12:30:46 +0100 Tomas Kalibera wrote: Thanks, ported now to R-patched. Thank you! Is it fine to mention problems like this one in the middle of an e-mail, or should I have left a note in the Bugzilla instead

Re: [R-pkg-devel] New Package Removal because Shared Library Too Large from Debugging Symbols

On 1/21/24 09:44, Ivan Krylov via R-package-devel wrote: В Sat, 20 Jan 2024 20:28:00 -0500 Johann Gaebler пишет: most likely there’s some error on my part in how I’ve set up cpp11, but it also seems possible that cpp11 should have detected that that header needs to be included and added it

Re: [R-pkg-devel] ERROR building MixAll on Windows platform

On 1/19/24 15:18, Serge wrote: This post is a continuation of the post *[R-pkg-devel] Does dependencies up to date on the pretest CRAN infrastructure* I made more (unsuccessful) tries: - I installed a Windows 11 version in a VM on my compuiter and try to buid the MixAll package using

Re: [R-pkg-devel] CMake on CRAN Systems

On 1/17/24 08:37, Sameh Abdulah wrote: Hi All, We recently encountered an installation issue with our package on CRAN. We've been depending on CMake, assuming it is readily available by default, but it appears to be only available on the M1mac system but not on the others. Should we

Re: [Rd] Choices to remove `srcref` (and its buddies) when serializing objects

: if by various tweaks, such as ensuring source references are off in your case, you achieve a state when false alarms are rare (identical objects have different hashes), and hence say unnecessary re-computation is rare, maybe it is good enough. Tomas On Jan 12, 2024, at 11:33 AM, Tomas Kalibera

Re: [R-pkg-devel] Additional Issues: Intel

On 1/17/24 09:41, Ivan Krylov via R-package-devel wrote: В Wed, 17 Jan 2024 10:30:36 +1100 Hugh Parsonage пишет: I am unable to immediately see where in the test suite this error has occurred. Without testthat, you would have gotten a line by line printout of the code, letting you

Re: [Rd] Choices to remove `srcref` (and its buddies) when serializing objects

On 1/12/24 06:11, Dipterix Wang wrote: Dear R devs, I was digging into a package issue today when I realized R serialize function not always generate the same results on equivalent objects when users choose to run differently. For example, the following code serialize(with(new.env(), {

Re: [R-pkg-devel] Issue with flang-new (segfault from C stack overflow)

Jisca On 18-12-2023 16:06, Tomas Kalibera wrote: On 12/18/23 15:09, Ivan Krylov wrote: В Mon, 18 Dec 2023 11:06:16 +0100 Jisca Huisman пишет: I isolated the problem in a minimal working example available here: https://github.com/JiscaH/flang_segfault_min_example . All that does is pas

Re: [R-pkg-devel] Issue with flang-new (segfault from C stack overflow)

On 12/18/23 15:09, Ivan Krylov wrote: В Mon, 18 Dec 2023 11:06:16 +0100 Jisca Huisman пишет: I isolated the problem in a minimal working example available here: https://github.com/JiscaH/flang_segfault_min_example . All that does is pass a vector of length N*N back and forth between R and

Re: [R-pkg-devel] Wrong mailing list: Could the 100 byte path length limit be lifted?

On 12/14/23 19:39, McGrath, Justin M wrote: At this point, the policy appears to have nothing to do with tar, contrary to the error message. Thus, replacing tar with zip wouldn't address CRAN's concern. The policy given in this thread (and seemingly unstated anywhere public) is that CRAN

Re: [R-pkg-devel] Wrong mailing list: Could the 100 byte path length limit be lifted?

On 12/13/23 15:59, Dirk Eddelbuettel wrote: On 13 December 2023 at 15:32, Tomas Kalibera wrote: | Please don't forget about what has been correctly mentioned on this | thread already: there is essentially a 260 character limit on Windows | (see | https://blog.r-project.org/2023/03/07/path

Re: [R-pkg-devel] Wrong mailing list: Could the 100 byte path length limit be lifted?

On 12/13/23 14:56, McGrath, Justin M wrote: Thanks. Pursuing this a bit further, from ?tar "Known problems": > The handling of file paths of more than 100 bytes. These > were unsupported in early versions of ‘tar’, and supported in > one way by POSIX ‘tar’ and in another by GNU

Re: [Rd] Request: documenting more specifically language objects in the R Language Definition document

On 12/13/23 11:27, Duncan Murdoch wrote: I doubt if anyone will take you up on this request.  Only R Core members can change those manuals, and it's hard work to write clear and correct documentation.  This probably won't make it high enough on their lists of priorities to actually be

Re: [R-pkg-devel] Update timing of machines on CRAN?

On 12/4/23 15:44, SHIMA Tatsuya wrote: Thanks for your answer. Unlike Windows Server, which has a long support period, Fedora's support period is usually about one year, so it is surprising that the old Fedora continues to be used. And, unlike Windows, Linux uses the distribution standard

Re: [R-pkg-devel] Canonical way to Rprintf R_xlen_t

On 11/29/23 19:30, Henrik Bengtsson wrote: On Tue, Nov 28, 2023 at 1:21 PM Tomas Kalibera wrote: On 11/28/23 21:50, Henrik Bengtsson wrote: Daniel, I get those compiler warnings for '%td" MS Windows. It works fine on Linux. Please let me clarify. %td works in R on Windows in R 4.3

Re: [R-pkg-devel] Canonical way to Rprintf R_xlen_t

On 11/28/23 22:21, Tomas Kalibera wrote: On 11/28/23 21:50, Henrik Bengtsson wrote: Daniel, I get those compiler warnings for '%td" MS Windows. It works fine on Linux. Please let me clarify. %td works in R on Windows in R 4.3 and R-devel, when using the recommended toolchain,

Re: [R-pkg-devel] Canonical way to Rprintf R_xlen_t

On 11/28/23 21:55, Daniel Kelley wrote: I hope it's okay to ask this on the present thread, rather than starting a new one... On this issue of the C format for various integer-type items, I am finding that checks made with devtools::check_win_devel() give different results than those made

Re: [R-pkg-devel] Canonical way to Rprintf R_xlen_t

On 11/28/23 20:51, Ivan Krylov wrote: On Wed, 29 Nov 2023 06:11:23 +1100 Hugh Parsonage wrote: Rprintf("%lld", (long long) xlength(x)); This is fine. long longs are guaranteed to be at least 64 bits in size and are signed, just like lengths in R. Right, this has been my choice for R-devel,

Re: [R-pkg-devel] Canonical way to Rprintf R_xlen_t

On 11/28/23 21:50, Henrik Bengtsson wrote: Daniel, I get those compiler warnings for '%td" MS Windows. It works fine on Linux. Please let me clarify. %td works in R on Windows in R 4.3 and R-devel, when using the recommended toolchain, which is Rtools43. It also worked with R 4.2 and

Re: [Rd] Rtools error

On 11/27/23 18:58, Rui Barradas wrote: Às 05:07 de 27/11/2023, Neha gupta escreveu: Hello, I want to download a package and it gives me the error: WARNING: Rtools is required to build R packages, but no version of Rtools compatible with R 4.2.0 was found. (Only the following incompatible

Re: [Rd] Rtools error

On 11/27/23 06:07, Neha gupta wrote: Hello, I want to download a package and it gives me the error: WARNING: Rtools is required to build R packages, but no version of Rtools compatible with R 4.2.0 was found. (Only the following incompatible version(s) of Rtools were found: 4.3.5550) This

Re: [Rd] More Detail on "Error : vector memory exhausted (limit reached?)"

On 11/27/23 05:42, ivo welch wrote: Would it be possible to enhance this error message? Could the message say how large the limit was that was reached? Is it that the limit for one particular vector has been exceeded (and to how much would it have grown vs. how much was allowed?), or is it

Re: [Rd] R-4.3 version list.files function could not work correctly in chinese

characters.     https://stackoverflow.com/q/77527167/12685768 Great, thanks! Tomas Mikael On 2023-08-17 6:00 am, r-devel-requ...@r-project.org wrote: Message: 5 Date: Wed, 16 Aug 2023 16:00:13 +0200 From: Tomas Kalibera To: Ivan Krylov Cc:"r-devel@r-project.org"  Subject: Re: [Rd]  R-4

Re: [Rd] system()/system2() using short paths of commands on Windows?

On 10/31/23 10:05, Duncan Murdoch wrote: On 31/10/2023 4:32 a.m., Tomas Kalibera wrote: On 10/30/23 19:07, Yihui Xie wrote: Sure. I'm not sure if it's possible to make it easier to reproduce, but for now the example would require installing TinyTeX (via tinytex::install_tinytex(), which can

Re: [Rd] Segmentation fault early in compilation of revision 85514

On 11/14/23 19:19, Joshua Ulrich wrote: On Mon, Nov 13, 2023 at 12:45 PM Avraham Adler wrote: On Mon, Nov 13, 2023 at 1:13 AM Dirk Eddelbuettel wrote: Avi, Might be toolchain-dependent, might be options-dependent--it built fine here. Easier for you to vary option two so maybe try that?

Re: [R-pkg-devel] Package submission issue - OMP reduction (flang-new)

On 11/13/23 19:18, Ivan Krylov wrote: On Mon, 13 Nov 2023 16:39:45 +0100 (CET) Romain Pierlot wrote: Here is the error message, and the adequate code part is joint in the mail : error:

Re: [R-pkg-devel] Package submission issue - OMP reduction (flang-new)

On 11/13/23 16:39, Romain Pierlot wrote: Hi everyone, I sent a first message a few weeks ago. I'm still in trouble for sending a package (Frailtypack) on the CRAN. It was removed because of reinforcement in CRAN requirements. We corrected the few issues, but more appeared, and one that I'm

Re: [Rd] configure output with flexiblas [was Re: About FlexiBLAS in the R-admin docs]

On 11/1/23 13:29, Iñaki Ucar wrote: On Wed, 1 Nov 2023 at 12:57, Tomas Kalibera wrote: On 10/31/23 10:45, Iñaki Ucar wrote: On Tue, 24 Oct 2023 at 12:53, Tomas Kalibera wrote: The output of session info is based on that flexiblas is used and on what flexiblas tells R is the backend

Re: [R-pkg-devel] Package bioOED has been removed from CRAN just for personal reasons

On 11/1/23 12:15, Alberto Garre wrote: Dear community, I feel dismay for having to write this email, but the issue must be brought up. On the 20th of October, I received an email from CRAN warning me of an issue with one of the packages I maintain (bioOED). The package depended on MEIGOR, a

[Rd] configure output with flexiblas [was Re: About FlexiBLAS in the R-admin docs]

On 10/31/23 10:45, Iñaki Ucar wrote: On Tue, 24 Oct 2023 at 12:53, Tomas Kalibera wrote: The output of session info is based on that flexiblas is used and on what flexiblas tells R is the backend it uses. R does not attempt to check that optimized LAPACK functions from the backend really end

Re: [Rd] system()/system2() using short paths of commands on Windows?

On 10/30/23 21:36, Yihui Xie wrote: > I have read about "system() not using a shell on Windows" on the help > page many times before but never understood what it means technically. > Please forgive my ignorance. I still do not understand it, but thanks > a lot for the explanation anyway! As the

Re: [Rd] system()/system2() using short paths of commands on Windows?

doesn't make sense. Best Tomas > > Regards, > Yihui > -- > https://yihui.org > > > On Mon, Oct 30, 2023 at 12:34 PM Tomas Kalibera > wrote: > > > On 10/30/23 17:18, Yihui Xie wrote: > > Hi, > > > > It may have been so for 20

Re: [Rd] system()/system2() using short paths of commands on Windows?

On 10/30/23 17:18, Yihui Xie wrote: Hi, It may have been so for 20+ years but I just discovered today that system() would always try to use the short path of a command on Windows: https://github.com/wch/r-source/blob/635a67/src/gnuwin32/run.c#L141 If that's true, I wonder if it could provide

Re: [Rd] About FlexiBLAS in the R-admin docs

On 10/11/23 23:12, George Ostrouchov wrote: I agree that the "R Installation and Administration" guide statement about FlexiBLAS needs an update. Standard R in CentOS Stream 9, which is now downstream from Fedora, gives the following result for Matrix products in sessionInfo():

Re: [Rd] FR: valid_regex() to test string validity as a regular expression

On 10/10/23 01:57, Michael Chirico via R-devel wrote: > It will be useful to package authors trying to validate input which is > supposed to be a valid regular expression. > > As near as I can tell, the only way we can do so now is to run any > regex function and check for the warning and/or

Re: [Rd] R-4.3 version list.files function could not work correctly in chinese

On 8/16/23 13:22, Ivan Krylov wrote: On Wed, 16 Aug 2023 09:42:09 +0200 Tomas Kalibera wrote: Fixed in R-devel (84960). Please let me know if you see any problem with the fix. Thank you for implementing the fix! I gave 叶月光 the link to the GitHub Action build of the r84960 installer

Re: [Rd] R-4.3 version list.files function could not work correctly in chinese

by choosing rather long names for individual files, one usually soon runs out of the limit for the full path. Best Tomas [1] - https://blog.r-project.org/2023/03/07/path-length-limit-on-windows/index.html > > Regards, > yu > > ---

Re: [Rd] R-4.3 version list.files function could not work correctly in chinese

On 8/15/23 16:00, Tomas Kalibera wrote: On 8/15/23 09:04, Ivan Krylov wrote: В Tue, 15 Aug 2023 08:38:11 +0200 Tomas Kalibera пишет: As this was reported to be regression in 4.3, it is entirely possible this change came with a regression (though a bit surprising we didn't catch it earlier

Re: [Rd] 答复: R-4.3 version list.files function could not work correctly in chinese

Dear 叶月光, as discussed on this thread, Ivan Krylov found a bug in R, which could be causing the problem you have run into. To confirm this is the cause, could you please check outside R (say in explorer) if you have any file with a very long name in the directory? And if so, does moving that

Re: [Rd] R-4.3 version list.files function could not work correctly in chinese

On 8/15/23 09:04, Ivan Krylov wrote: В Tue, 15 Aug 2023 08:38:11 +0200 Tomas Kalibera пишет: As this was reported to be regression in 4.3, it is entirely possible this change came with a regression (though a bit surprising we didn't catch it earlier by testing), so it would be a great help

Re: [Rd] R-4.3 version list.files function could not work correctly in chinese

On 8/13/23 13:16, Ivan Krylov wrote: Found it! Looks like a buffer length problem. This isn't limited to Chinese, just more likely to happen when a character takes three bytes to represent in UTF-8. (Any filename containing characters which take more than one byte to represent in UTF-8 may

Re: [Rd] a quick and dirty way to compile R on win arm64 using clangarm64

On 8/13/23 05:26, yu gong wrote: sorry forgot dynamic link ICU 1 svn checkout R-trunk and add USE_LLVM=YES and ICU_LIBS ?= -licuin -licuuc -licudt -lstdc++ in MKRules.dist or Mkrules.local For the record, if you are experimenting with building R-devel using msys2 toolchains, you should

Re: [Rd] a quick and dirty way to compile R on win arm64 using clangarm64

On 8/13/23 05:14, yu gong wrote: hello everyone: On this boring weekend, I tried compile R-trunk on windows 11 arm64 using clangarm64+msys2 on macbook m1 , it surprisingly easy to compiled and run. more investigation and test and code modify need to be done ,but IMO this is a good

Re: [Rd] Bug in perl=TRUE regexp matching?

On 7/25/23 03:13, Brodie Gaslam via R-devel wrote: On 7/24/23 4:10 AM, Duncan Murdoch wrote: On 23/07/2023 9:01 p.m., Brodie Gaslam wrote: On 7/23/23 4:29 PM, Duncan Murdoch wrote: The help page for `?gsub` says (in the context of performance considerations): "... just one UTF-8

Re: [R-pkg-devel] Feedback on "Using Rust in CRAN packages"

On 7/13/23 05:08, Hiroaki Yutani wrote: I actually use cargo vendor. https://github.com/yutannihilation/string2path/blob/main/src/rust/vendor.sh One thing to note is that, prior to R 4.3.0, the vendored directories hit the Windows' path limit so I had to put them into a TAR file. I haven't

Re: [Rd] Incorrect type in malloc in Rscript.c

On 7/13/23 00:26, Will McClennan wrote: I downloaded and compiled R-4.3.1 from cran.rstudio.com and on line 405 of Rscript.c in src/unix the line of code char *buf=(char*) malloc((size_t) (len+1)*sizeof(char *)); appears to be wrong to me. If an array of char* is being allocated then the

Re: [Rd] Installation of R-4.3.1 with intel 2022

On 6/20/23 18:47, Giuseppe Calò wrote: Hi all, I have the issue: icc -std=c99 -std=gnu11 -I../../src/extra -I../../src/extra/xdr -I. -I../../src/include -I../../src/include -I/usr/local/include -I../../src/nmath -DHAVE_CONFIG_H -fopenmp -fpic -g -O3 -wd188 -ip -mp -c eval.c -o eval.o

Re: [Rd] why does [A-Z] include 'T' in an Estonian locale?

On 5/30/23 17:45, Ben Bolker wrote: Inspired by this old Stack Overflow question https://stackoverflow.com/questions/19765610/when-does-locale-affect-rs-regular-expressions I was wondering why this is TRUE: Sys.setlocale("LC_ALL", "et_EE") grepl("[A-Z]", "T") TRE's documentation at

Re: [Rd] Building R from source always fails on tools:::sysdata2LazyLoadDB

On 5/30/23 22:09, Martin Morgan wrote: I build my own R from source on an M1 mac. I have a clean svn checkout in one directory ~/src/R-devel. I switch to ~/bin/R-devel and the first time run cd ~/bin/R-devel ~/src/R-devel/configure --enable-R-shlib 'CFLAGS=-g -O0'

Re: [Rd] How to locate references to an environment?

On 5/23/23 20:29, Peter Meilstrup wrote: R developers, I am trying to track down a memory leak in my R package. I have a complex object O which comprises a lot of closures and such. Among which, the object uses an environment E to perform computations and keep intermediate values in. When O

Re: [Rd] R-4.2.3 build from source on Windows (w Rtools42) - lto1.exe error

ols if needed (also covered in the documentation). You surely might be able to make it work even with other distribution of tools, but you'd be on your own, likely have to deal with technical issues. Best Tomas Greetings, Walter On Thu, 11 May 2023 at 09:06, Tomas Kalibera wrote: On 5

Re: [Rd] R-4.2.3 build from source on Windows (w Rtools42) - lto1.exe error

On 5/11/23 03:07, Gmail wrote: Windows 11 PRO Version  10.0.22621 Build 22621 Processor: Intel(R) Core(TM) i7-1065G7 "Icelake-client" ``` ​svn info Path: . Working Copy Root Path: /d/R_DEV/R-4/R42/R-4-2-branch URL: https://svn.r-project.org/R/branches/R-4-2-branch Relative URL:

Re: [Rd] Forcing a PROTECT Bug to Occur

rn(expr), restart) >  2: withOneRestart(expr, restarts[[1L]]) >  3: withRestarts({  .Internal(.signalCondition(simpleWarning(msg, > call), msg,     call))    .Internal(.dfltWarn(msg, call))}, > muffleWarning = function() NULL) >  4: .signalSimpleWarning("your C program does not return a

Re: [Rd] Forcing a PROTECT Bug to Occur

On 4/29/23 19:26, Michael Milton wrote: I'm trying to learn about R's PROTECT system. To that end I've tried to create an example of C code that doesn't protect anything. I was hoping it would either segfault from trying to access deallocated memory, or maybe print out nonsense results because

Re: [Rd] path to rtools not updated in R 4.2.3 - line 1: gcc: command not found

On 4/5/23 07:48, Patrick Giraudoux wrote: Dear listers, I have update to rtools43 and, using R 4.2.3 I have been surprised not to be able to compile packages needing compilation when updating. Looks like the path given in gcc  -I"C:/PROGRA~1/R/R-42~1.3/include" -DNDEBUG -DNTIMER

Re: [Rd] Breaking Change in Rcomplex Layout?

are visible on the Fortran side in a corresponding array of COMPLEX. Without knowing that, the link-time optimizer could remove say stores to the ".r" and ".i" when calling to Fortran, this is what has been actually seen to happen. Tomas > > On Tue, Apr 4, 2023 at 5:

Re: [Rd] Breaking Change in Rcomplex Layout?

g sure you don't re-introduce the problem that R had before this change, on your end. Tomas > > Cheers > > On Tue, Apr 4, 2023 at 12:15 AM Tomas Kalibera > wrote: > > > On 4/3/23 15:50, Michael Milton wrote: >> Okay, but I'm afraid this will only mean something to Ru

Re: [Rd] Breaking Change in Rcomplex Layout?

will get a NEWS entry when/if it gets ported to 4.3.0 branch, in the form it would have at that point. Best Tomas > > On Mon, Apr 3, 2023 at 11:39 PM Tomas Kalibera > wrote: > > > On 4/3/23 14:07, Michael Milton wrote: > > Hi all, > > > > The

Re: [Rd] Breaking Change in Rcomplex Layout?

On 4/3/23 14:07, Michael Milton wrote: Hi all, There seems to have been a breaking change in the R trunk caused by a fix to bug 18430 that relates to the layout of the Rcomplex typedef. Previously it was a struct, but now it's a union by

Re: [R-pkg-devel] How to identify what flags "Additional Issues" for UBSAN

On 3/22/23 16:51, Kenny, Christopher wrote: Hi folks, I'm the maintainer of the redist package (https://cran.r-project.org/web/checks/check_results_redist.html) which was flagged for additional issues with clang-UBSAN and gcc-UBSAN. Both of the 00check.log files say that the status is "OK"

Re: [Rd] Versioning Rtools ARP entries

On 3/13/23 17:57, Tomas Kalibera wrote: On 3/13/23 17:31, Daniel Possenriede wrote: Hi, If I am not mistaken, all Rtools 4.2 (and 4.3) revisions have the same ARP [1] entries, i.e. all report version 4.2.0.1 (or 4.3.0.1). This makes it difficult to determine the installed version

Re: [Rd] La_library() always returns "" on R-devel?

On 3/17/23 11:53, Gábor Csárdi wrote: Seems like this in 83986 [1] needs a fix in Lapack.c: if (dladdr((void *) F77_NAME(ilaver), _info)) { char buf[PATH_MAX+1]; char *res = realpath(dl_info.dli_fname, buf); if (res) { SEXP nfo

Re: [Rd] Versioning Rtools ARP entries

On 3/13/23 17:31, Daniel Possenriede wrote: Hi, If I am not mistaken, all Rtools 4.2 (and 4.3) revisions have the same ARP [1] entries, i.e. all report version 4.2.0.1 (or 4.3.0.1). This makes it difficult to determine the installed version (is it possible to determine the installed

Re: [Rd] On optimizing `R_NewEnv()`

On 2/8/23 21:51, Davis Vaughan via R-devel wrote: Hi all, I really like the addition of `R_NewEnv()` back in 4.1.0 https://github.com/wch/r-source/blob/625ab8d45f86f65561e53627e1f0c220bdc5f752/src/main/envir.c#L3619-L3630 I have a use case where I'm likely to call this function a large

Re: [Rd] scan(..., skip=1e11): infinite loop; cannot interrupt

On 2/11/23 09:33, Ivan Krylov wrote: On Fri, 10 Feb 2023 23:38:55 -0600 Spencer Graves wrote: I have a 4.54 GB file that I'm trying to read in chunks using "scan(..., skip=__)". It works as expected for small values of "skip" but goes into an infinite loop for "skip=1e11" and similar

Re: [R-pkg-devel] Sanitize Input Code for a Shiny App

On 3/1/23 07:35, Matthias Gondan wrote: For the record, here's the documentation of the Prolog sandbox, https://www.swi-prolog.org/pldoc/doc/_SWI_/library/sandbox.pl You get an idea of the implementation by clicking at the ":-" icons. It does not seem too complicated, but I might be too

Re: [Rd] Undocumented change of dirname("C:/") on R-devel on Windows

ive path [1]. So, I agree with you that > the basename > > of "C:/" should be "C:/". However, at the same time, I don't > feel this is > > worth a breaking change, so I think we can preserve the current > (R 4.2.2) > > behav

Re: [Rd] Possible NA Propagation Failure in RISC-V64 CPU?

On 2/24/23 00:39, Jane He wrote: Hi all, I am currently compiling R to RISC-V64 CPU and I think I have discovered a NA propagation failure. How R implements NA (not available) and NaN (not-a-number) is explained in detail here:

Re: [Rd] dyn.load loads libraries/symbols at high addresses.

On 2/22/23 23:05, Vanessa McHale wrote: Hello all, I am trying to write an interface for BQN and R However, even | dyn.load("/usr/local/lib/libcbqn.so"); .Call("bqn_init")| immediately fails on the BQN side, viz. |Failed to allocate memory for JIT 200

Re: [Rd] Undocumented change of dirname("C:/") on R-devel on Windows

On 2/23/23 03:27, Hiroaki Yutani wrote: Hi, I found dirname() behaves differently on R-devel on Windows. Since I'm not sure which behavior is right, let me ask here before filing this to R's Bigzilla. On R 4.2.2., we get > dirname("C:/") [1] "C:/" However, on R-devel (r83888), we

Re: [Rd] Robustifying R_CleanTempDir a bit more

On 2/16/23 15:43, Tomas Kalibera wrote: On 2/16/23 15:09, Ivan Krylov wrote: Hello, This is probably a very minor point, but R_CleanTempDir may still have a shell injection in it. I couldn't find a way to shoot the user in the foot in a significant way (by, say, accidentally removing

Re: [Rd] Robustifying R_CleanTempDir a bit more

On 2/16/23 15:09, Ivan Krylov wrote: Hello, This is probably a very minor point, but R_CleanTempDir may still have a shell injection in it. I couldn't find a way to shoot the user in the foot in a significant way (by, say, accidentally removing ~), thanks to R disallowing spaces in the path,

Re: [Rd] Question on non-blocking socket

On 2/15/23 16:44, Ben Engbers wrote: Hi Op 15-02-2023 om 14:38 schreef Tomas Kalibera: On 2/15/23 01:24, Ben Engbers wrote: Hi, December 27, 2021 I started a thread asking for help troubleshooting non-blocking sockets. .. I have two questions. The first is where I can find R

Re: [Rd] Question on non-blocking socket

in this process between sending the credentials to the server and requesting the status. Tomas Kalibera put me on the right track by drawing my attention to the 'socketSelect' function. I don't know exactly the purpose of this function is (the function itself is documented, but I can't find any information

Re: [R-pkg-devel] Unable to load Windows NETIO.SYS and WINSPOOL.DRV DLLs

On 2/14/23 13:26, David Sterratt wrote: On Mon, 2023-02-13 at 19:08 +0100, Tomas Kalibera wrote: For reference, there is an old patch for RGtk2 package that I had created when working on Rtools42, though I am not very optimistic it will help in this case: https://svn.r-project.org/R-dev-web

Re: [Rd] long path names (more than 260 chars) not working under Windows OS, longPathAware missing in exe manifests?

On 2/14/23 12:11, Roman Hille wrote: Can you help please? All file und dir funktions and also basename() do not work in R under Windows OS if the path is longer than 260 characters. The problem seems to be, that the manifest for all R executables do not have the longPathAware switch in the

Re: [R-pkg-devel] Unable to load Windows NETIO.SYS and WINSPOOL.DRV DLLs

On 2/12/23 17:37, David Sterratt wrote: On Sat, 2023-02-11 at 18:11 +0300, Ivan Krylov wrote: On Sat, 11 Feb 2023 11:19:42 + David Sterratt wrote: WinDbg output reveals errors loading "NETIO.SYS" and "WINSPOOL.DRV" when running "library(RGtk2)": 0c64:0640 @ 44312812 -

Re: [Rd] Small typo in Writing R Extensions

On 2/8/23 21:33, Davis Vaughan via R-devel wrote: Hi all, Writing R Extensions describes `R_NewEnv()` as: ``` At times it may also be useful to create a new environment frame in C code. R_NewEnv is a C version of the R function new.env: SEXP R_NewEnv(SEXP enclos, int hash, ins size) ```

Re: [Rd] Sys.getenv(): Error in substring(x, m + 1L) : invalid multibyte string at '' if an environment variable contains \xFF

On 1/31/23 14:37, peter dalgaard wrote: On 31 Jan 2023, at 12:51 , Tomas Kalibera wrote: On 1/31/23 11:50, Martin Maechler wrote: hmm.., that's a pity; I had hoped it was a pragmatic and valid strategy, but of course you are right that type stability is really a valid goal

Re: [Rd] Sys.getenv(): Error in substring(x, m + 1L) : invalid multibyte string at '' if an environment variable contains \xFF

On 1/31/23 11:50, Martin Maechler wrote: Tomas Kalibera on Tue, 31 Jan 2023 10:53:21 +0100 writes: > On 1/31/23 09:48, Ivan Krylov wrote: >> Can we use the "bytes" encoding for such environment variables invalid >> in the current locale? The

Re: [Rd] Sys.getenv(): Error in substring(x, m + 1L) : invalid multibyte string at '' if an environment variable contains \xFF

On 1/31/23 09:48, Ivan Krylov wrote: Can we use the "bytes" encoding for such environment variables invalid in the current locale? The following patch preserves CE_NATIVE for strings valid in the current UTF-8 or multibyte locale (or non-multibyte strings) but sets CE_BYTES for those that are

Re: [Rd] Sys.getenv(): Error in substring(x, m + 1L) : invalid multibyte string at '' if an environment variable contains \xFF

if we want to make specific checks, we should make them conditional - even if the default is to add them. Again, the error is due to the implementation of Sys.getenv() breaking in R-devel, not due to any design decision. The key design decision (and common one) behind is that environment va

Re: [Rd] Sys.getenv(): Error in substring(x, m + 1L) : invalid multibyte string at '' if an environment variable contains \xFF

On 1/30/23 23:01, Henrik Bengtsson wrote: /Hello. SUMMARY: $ BOOM=$'\xFF' LC_ALL=en_US.UTF-8 Rscript --vanilla -e "Sys.getenv()" Error in substring(x, m + 1L) : invalid multibyte string at '' $ BOOM=$'\xFF' LC_ALL=en_US.UTF-8 Rscript --vanilla -e "Sys.getenv('BOOM')" [1] "\xff" BACKGROUND:

Re: [R-pkg-devel] Inconsistent R CMD Check results

On 1/23/23 17:51, Ying Li via R-package-devel wrote: Dear all, Hope you are well! Recently, in the check before a re-submission, I got an unexpected note when doing R CMD Check using rhub::check_for_cran(), saying that "Examples with CPU (user + system) or elapsed time > 5s". I didn't expect

Re: [R-pkg-devel] If you had to choose one binary to preserve for a pkg, which would it be?

On 1/22/23 22:36, Uri Simonsohn wrote: This is not a perfect list for this question, but possibly a good list. I think this is a good match. I maintain 'groundhog', a package that seeks to simplify reproducibility of R code based on R packages. It has so far relied on MRAN for binaries of

Re: [R-pkg-devel] strange errors (non-ascii symbols) on win-builder R-devel

On 1/23/23 17:30, Maxim Nazarov wrote: Hello all, I am submitting a minor update to one of my CRAN package (BIGL), and get strange errors on R-devel on win-builder - https://win-builder.r-project.org/incoming_pretest/BIGL_1.6.7_20230119_225109/Windows/00check.log and

Re: [Rd] Object are not destroy while using error (Rf_error)

On 1/21/23 16:55, Antoine Lucas wrote: Dear all, I try to understand why on my computer I do not clear all data with this code: #include static int count = 0; class A { public: A(){ printf("c %d\n", count); count++; } ~A(){count--; printf("d %d\n", count); } }; extern

  1   2   3   4   5   6   >