search for: numeric_version

I've noticed something in R devel which seems a little off and not the behavior I see in 4.4.0 or earlier versions. With numeric_versions that have long (>8 digit) final components max and min return the first element and not the max or min: In devel: > max(numeric_version(c("1.0.1.100000000", "1.0.3.100000000", "1.0.2.100000000"))) [1] ?1.0.1.100000000? > max(numeric_version(c("1.0.1.100...

? Sat, 27 Apr 2024 13:56:58 -0500 Jonathan Keane <jkeane at gmail.com> ?????: > In devel: > > max(numeric_version(c("1.0.1.100000000", "1.0.3.100000000", > "1.0.2.100000000"))) > [1] ?1.0.1.100000000? > > max(numeric_version(c("1.0.1.10000000", "1.0.3.10000000", > "1.0.2.10000000"))) > [1] ?1.0.3.10000000? Thank you Jon for spot...

I mean the `numeric_version` object not a numeric (double/int). Basically to protect me from myself I'd prefer not to have to remember to wrap `getNamespaceVersion()` with `as.package_version()`. I suspect a grep of CRAN may highlight others who are erroneously comparing character objects rather than a comparison betw...

Dear R devs, I installed the recent devel R to test a package error when I intercept this warning when loading packages: ``` Warning in .make_numeric_version(x, strict, .standard_regexps()$valid_numeric_version) : invalid non-character version specification 'x' (type: double) ``` After a long debugging, I realize that `numeric_version` in base does not support numerical input x by default now. A reproducible example: R 4.4 ``` > numer...

On 17/10/2024 13:42, Tim Taylor wrote: > I mean the `numeric_version` object not a numeric (double/int). > Basically to protect me from myself I'd prefer not to have to remember > to wrap `getNamespaceVersion()` with `as.package_version()`. > > I suspect a grep of CRAN may highlight others who are erroneously > comparing character objects rath...

On 17 October 2024 at 12:38, Tim Taylor wrote: | Would R-Core be receptive to having getNamespaceVersion() return a | numeric_version object instead of a named character? Is this good enough? What's your actual issue a 'numeric' would address? > as.package_version(getNamespaceVersion("base")) < "4.5.0" [1] TRUE > > as.package_version(getNamespaceVersion("Rcpp"))...

Would R-Core be receptive to having getNamespaceVersion() return a numeric_version object instead of a named character? Tim

...lt" [39] "unique.character" "$.packageDescription2" [41] "$.default" ">=.R_system_version" [43] "Ops.R_system_version" ">=.package_version" [45] "Ops.package_version" ">=.numeric_version" [47] ">=.package_version" "Ops.package_version" [49] ">=.numeric_version" "unlist.R_system_version" [51] "unlist.package_version" "unlist.numeric_version" [53] "unlist.default" "un...

...lt" [39] "unique.character" "$.packageDescription2" [41] "$.default" ">=.R_system_version" [43] "Ops.R_system_version" ">=.package_version" [45] "Ops.package_version" ">=.numeric_version" [47] ">=.package_version" "Ops.package_version" [49] ">=.numeric_version" "unlist.R_system_version" [51] "unlist.package_version" "unlist.numeric_version" [53] "unlist.default" "un...

...(c("1.0.3","1.0.4","1.0.5"))) ## [1] ?1.0.5? I've looked at ?package_version , to no avail. Since max() goes to .Primitive("max") I'm having trouble figuring out where it goes from there: I **think** this is related to ?xtfrm , which goes to .encode_numeric_version, which is doing something I really don't understand (it's in base/R/version.R ...) .encode_numeric_version(pp1) ## [1] 1 1 1 ## attr(,"base") ## [1] 99999912 ## attr(,"lens") ## [1] 3 3 3 ## attr(,".classes") ## [1] "package_version" "numeric_ve...

> is.na(strptime("5/2/1992", format="%m/%d/%Y")) [1] FALSE > is.na(strptime("5/3/1992", format="%m/%d/%Y")) [1] TRUE Any idea what's going on with this? Running strptime against all dates from around 1946, only 5/3/1992 was converted as "NA". Even stranger, it still seems to have a value associated with it (even though is.na thinks

...9;)) report(is.name(res)) > res <- try(as.null( x ), silent = TRUE) > if(!inherits(res, 'try-error')) report(is.null(res)) [1] TRUE > res <- try(as.numeric( x ), silent = TRUE) > if(!inherits(res, 'try-error')) report(is.numeric(res)) [1] TRUE > res <- try(as.numeric_version( x ), silent = TRUE) > if(!inherits(res, 'try-error')) report(is.numeric_version(res)) [1] TRUE > res <- try(as.ordered( x ), silent = TRUE) > if(!inherits(res, 'try-error')) report(is.ordered(res)) [1] TRUE > res <- try(as.package_version( x ), silent = TRUE) >...

In R 3.4.0 RC, argument list of 'c' as S4 generic function has become (x, ...) . However, "S4 methods" section in documentation of 'c' (c.Rd) is not updated yet. Also, in R 3.4.0 RC, 'c' method of class "Date" ('c.Date') is still not explicitly documented.

...list_extract.c -o sublist_extract.o gcc -std=gnu99 -shared -L/usr/local/lib64 -o Biobase.so anyMissing.o envir.o matchpt.o Rinit.o rowMedians.o sublist_extract.o ** R ** data ** inst ** preparing package for lazy loading Loading required package: tools Error : could not find function "numeric_version" Error: unable to load R code in package 'Biobase' Execution halted ERROR: lazy loading failed for package 'Biobase' ** Removing '/usr/local/lib/R/library/Biobase' It is choking at not finding a function "numeric_version". Has anybody seen this before an...

Hi Kurt, On 25 April 2024 at 08:07, Kurt Hornik wrote: | >>>>> Herv? Pag?s writes: | | > Hi Kurt, | > Is it intended that numeric_version() returns an error by default on | > non-character input in R 4.4.0? | | Dear Herve, yes, that's the intention. | | > It seems that I can turn this into a warning by setting | > _R_CHECK_STOP_ON_INVALID_NUMERIC_VERSION_INPUTS_=false but I don't | > seem to be able to find any...

>>>>> Herv? Pag?s writes: > Hi Kurt, > Is it intended that numeric_version() returns an error by default on > non-character input in R 4.4.0? Dear Herve, yes, that's the intention. > It seems that I can turn this into a warning by setting > _R_CHECK_STOP_ON_INVALID_NUMERIC_VERSION_INPUTS_=false but I don't > seem to be able to find any of this menti...

...; Error in if (R_version_built_under < "3.0.0") stop(gettextf("package %s was built before R 3.0.0: please re-install it", : missing value where TRUE/FALSE needed I've tried debugging this, and the bad lines are these, in loadNamespace: R_version_built_under <- as.numeric_version(built$R) if (R_version_built_under < "3.0.0") stop(gettextf("package %s was built before R 3.0.0: please re-install it", sQuote(basename(pkgpath))), call. = FALSE, domain = NA) These are in the src/library/base/R/namespace.R file, around line 379. If I stop it before th...

...an object that's not a data frame, specifically 1:10, causes segmentation fault. Context ======= We can subscript with a number of different notations: > (1:10)[3] [1] 3 > do.call(get("[",pos="package:base"),list(1:10,3)) [1] 3 > do.call(get("[.numeric_version",pos="package:base"),list(1:10,3)) [1] 3 Problem ======= If we mistakenly believe the object is a data frame (as we did in a much more complicated real situation), this happens: > do.call(get("[.data.frame",pos="package:base"),list(1:10,3)) Error in...

...= package_version('3.0'))) This should fail (package2 has version 0.3, not 3.0) but instead it seems to load package2, version 0.3 OK. Reading the code of loadNamespace, there is some code which says if (length(z <- versionCheck) == 3L && !do.call(z$op, list(as.numeric_version(version), z$version))) stop(gettextf("namespace %s %s is being loaded, but %s %s is required", sQuote(package), version, z$op, z$version), domain = NA) I think it is the length(z <- versionCheck) == 3L part of the if test that is allowing the incorrect versio...

Hi Kurt, Is it intended that numeric_version() returns an error by default on non-character input in R 4.4.0? It seems that I can turn this into a warning by setting _R_CHECK_STOP_ON_INVALID_NUMERIC_VERSION_INPUTS_=false but I don't seem to be able to find any of this mentioned in the NEWS file. Thanks, H. On 4/1/24 05:28, Kurt Hor...