Hi everyone,
I've noticed new behavior in `regexpr(..., perl = TRUE)` on Windows with
R4.0 and above with Unicode characters. Here's a minimal example where I'd
expect to see a start value of `5` (as R 3.6.2 and below gives), but R
4.0.0 (and R 4.0.1) now returns:
```
> regexpr("b", "foo\U0001F93
Dear Jeroen,
With the caveat that I've tested only a few of the Rcmdr dialogs (a full test
takes hours and must be done manually), everything seems to be working fine
again.
Thank you for addressing this problem so quickly.
John
-
John Fox, Professor Emeritus
On Mon, Jun 8, 2020 at 12:03 AM wrote:
>
> I've committed the change to use Free instead of free in tcltk.c and
> sys-std.c (r78652 for R-devel, r78653 for R-patched).
Thank you! I can confirm that the example from above no longer crashes
in R--patched.
John, can you confirm that everything seem
Well...
The first rule of release management is not to have the same version number on
different releases.
I see three possibilities
(1) Tell users to use 4.0.1-patched if they need tcltk on Windows
(2) A "vendor patch release": Windows maintainer reissues the binary after
applying the critica
