Displaying 5 results from an estimated 5 matches for "iiiii".
Did you mean:
iiii
2025 Jan 15
2
Weird and changed as.roman() behavior
...ted bahavior:
>> as.roman(strrep("I", 1:5))
> [1] I II III IV V
> Current behavior:
>> as.roman(strrep("I", 1:5))
> [1] I II III IV <NA>
> Warning message:
> In .roman2numeric(x) : invalid roman numeral: IIIII
> as.roman() doesn't handle "IIIII" -> "V" anymore and thus 'make check'
> fails when building any 4.3.x or 4.4.x versions from the sources.
Not yet.
For me, (on Linux Fedora 40),
on current R-4.4.2, R-patched and R-devel I get the same good
resu...
2025 Jan 14
1
Weird and changed as.roman() behavior
...ron is the
latest development version of Mageia Linux.
Expected bahavior:
> as.roman(strrep("I", 1:5))
[1] I II III IV V
Current behavior:
> as.roman(strrep("I", 1:5))
[1] I II III IV <NA>
Warning message:
In .roman2numeric(x) : invalid roman numeral: IIIII
as.roman() doesn't handle "IIIII" -> "V" anymore and thus 'make check'
fails when building any 4.3.x or 4.4.x versions from the sources.
Any hints?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: applicati...
2009 Jun 01
3
Problem EXCEPTION_ACCESS_VIOLATION (0xc0000005)
...10k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [comctl32.dll+0x86ec4]
C [comctl32.dll+0x8cdb5]
C [user32.dll+0xa8f1a]
C [user32.dll+0xa936a]
C [user32.dll+0xad2d2]
C [swt-win32-3452.dll+0x220a]
J org.eclipse.swt.internal.win32.OS.CallWindowProcW(IIIII)I
J org.eclipse.swt.internal.win32.OS.CallWindowProc(IIIII)I
j org.eclipse.swt.widgets.Tree.callWindowProc(IIII)I+580
J org.eclipse.swt.widgets.Control.windowProc(IIII)I
j org.eclipse.swt.widgets.Tree.windowProc(IIII)I+1609
J org.eclipse.swt.widgets.Display.windowProc(IIII)I
v ~StubRout...
2025 Jan 16
2
Weird and changed as.roman() behavior
...understand and that {,3} is not needed, and {0,3} is clearer,
whereas {3,} is not easy to re-express ( '{0,inf}' or similar
would make the code considerably more complicated and probably slower..)
Actually, to remain back compatible (see Jani's original report:
he'd like "IIIII" to work, as it did for many/most of us),
we should replace {,4} by {0,5}.
But there's more: our current help page
https://search.r-project.org/R/refmans/utils/html/roman.html
says
> Only numbers between 1 and 3999 have a unique representation
> as roman numbers, and hence o...
2025 Jan 15
1
Weird and changed as.roman() behavior
Well, the real issue then seems to be that .roman2numeric uses an invalid regular expression:
>> grepl("^M{,3}D?C{,4}L?X{,4}V?I{,4}$", cc)
> [1] TRUE TRUE TRUE TRUE TRUE
or
>> grepl("^I{,2}$", c("II", "III", "IIII"))
> [1] TRUE TRUE FALSE
Both the TRE and the PCRE specification only allow repetition quantifiers of the