search for: rangenum

...>> sparse matrices, ... > >> >> > >> >> To keep such methods all internally consistent with > >> >> range.default(), I could envision something like this > >> >> > >> >> > >> >> .rangeNum <- function(..., na.rm = FALSE, finite = FALSE, > isNumeric) > >> >> { > >> >> x <- c(..., recursive = TRUE) > >> >> if(isNumeric(x)) { > >> >> if(finite) x <- x[is.finite(x)] > >> >> else if(...

...t;DT_with_Inf>, finite = TRUE) now work for objects of class "Date", "POSIXct", and "POSIXlt" with infinite entries, analogously to range.default(), as proposed by Davis Vaughan on R-devel. Other range()-methods can make use of new function .rangeNum(). * New .internalGenerics object complementing .S3PrimitiveGenerics, for documentation and low-level book-keeping. * grid() now invisibly returns the x- and y- coordinates at which the grid-lines were drawn. * norm(., type) now also works for complex matrices. * kap...

...t;DT_with_Inf>, finite = TRUE) now work for objects of class "Date", "POSIXct", and "POSIXlt" with infinite entries, analogously to range.default(), as proposed by Davis Vaughan on R-devel. Other range()-methods can make use of new function .rangeNum(). * New .internalGenerics object complementing .S3PrimitiveGenerics, for documentation and low-level book-keeping. * grid() now invisibly returns the x- and y- coordinates at which the grid-lines were drawn. * norm(., type) now also works for complex matrices. * kap...