I’m trying to repair my SparseM package to meet new CRAN rules. The fun part
was rewriting the arithmetic-ifs in cholesky.f — to conform with new fortran
rules. (This struck me as a bit like updating “the wine dark seas” in Homer.)
Now, my remaining trouble is that I have several functions d
В Mon, 27 May 2024 10:52:26 +
"Koenker, Roger W" пишет:
> that have been fine until now and on my fresh R version 4.4.0
> (2024-04-24) are still ok with R CMD check —as-cran
This extra check requires the environment variable
_R_CHECK_S3_METHODS_SHOW_POSSIBLE_ISSUES_ to be set to TRUE to show
Dear list,
The following behavior in base R is unexpected to me:
a <- as.hexmode("99ac")
b <- as.hexmode("9ce5")
v <- c(a,b)
v
#> [1] 39340 40165
class(v)
#> [1] "integer"
Is there a good reason why v should not be of class "hexmode"?
I can see that this is exactly as documented. The help for `
On 2024-05-27 11:49 a.m., Schuhmacher, Dominic wrote:
Dear list,
The following behavior in base R is unexpected to me:
a <- as.hexmode("99ac")
b <- as.hexmode("9ce5")
v <- c(a,b)
v
#> [1] 39340 40165
class(v)
#> [1] "integer"
Is there a good reason why v should not be of class "hexmode"?
I ca
