differences
Differences between Spotfire Enterprise Runtime for R and open-source R
Description
This file contains a compilation of the differences between Spotfire
Enterprise Runtime for R and open-source R.
General
Spotfire Enterprise Runtime for R issues a warning if a function is exported
more than once from a package NAMESPACE file. R provides no
such warning. (Duplicate exports in packages occur in a number of places
in the CRAN repository.)
abbreviate
In open-source R, the "use.classes" argument is silently ignored and treated as TRUE.
In some cases, this causes Spotfire Enterprise Runtime for R and open-source R to produce different results:
Example
abbreviate(c('a foobr','a foobar'))
# R: "a foobr" "afoobar"
# TERR: "afoobr" "afoobar"
Bessel
colMeans
- Spotfire Enterprise Runtime for R accepts vectors, but open-source R does not.
- In Spotfire Enterprise Runtime for R, rowMeans/colMeans return NaN if there are no values; open-source R returns NA:
rowMeans(matrix(NA), na.rm=T)
- colVars, colStdevs, rowVars, and rowStdevs are not supported by open-source R, but they are in Spotfire Enterprise Runtime for R.
- colSums, rowSums, colMeans and rowMeans are implemented both in open-source R and Spotfire Enterprise Runtime for R,
but there are more arguments in the Spotfire Enterprise Runtime for R implementation (for example, weights, freq and n. All of these might not be presented).
- colSums, rowSums, colMeans and rowMeans are NOT generic functions in open-source R.
connections
- In open-source R, when the engine is run in
non-interactive mode with the script specified via -f,
readLines(stdin()) reads lines from the script file.
In Spotfire Enterprise Runtime for R, in that case, readLines(stdin()) returns character(0).
- In Spotfire Enterprise Runtime for R, the "internal" method of the url function is an alias for "libcurl".
data.matrix
The function numerical.matrix is not implemented in open-source R.
deparse
- Spotfire Enterprise Runtime for R has the extra control parameter noSplitLines.
- In Spotfire Enterprise Runtime for R, deparse currently supports only the control parameters 'keepInteger', 'keepNA', 'showAttributes', 'useSource', and (the Spotfire Enterprise Runtime for R-specific) 'noSplitLines'.
difftime
Differences exist between Spotfire Enterprise Runtime for R and open-source R in the results for calculating difftime near DST;
the Spotfire Enterprise Runtime for R results appear more reasonable than those of open-source R.
Example
## The start of DST in USA 2013 is 2013-03-10 2:00AM
> difftime("2013-03-10 03:00:00", "2013-03-10 02:00:00", tz = "America/New_York")
# Time difference of 2 hours (open-source R)
# Time difference of 0 secs (TERR)
> difftime("2013-03-10 03:00:00", "2013-03-10 02:59:00", tz = "America/New_York")
# Time difference of 2 hours (open-source R)
# Time difference of -59 mins (TERR)
The differences are caused by the differences in as.POSIXct, i.e.,
> as.POSIXct("2013-03-10 02:00:00", tz = "America/New_York")
# [1] "2013-03-10 EST" (open-source R)
# [1] "2013-03-10 03:00:00 EDT" (TERR)
> as.POSIXct("2011-03-13 02:59:59", tz = "America/New_York")
# [1] "2013-03-10 EST" (open-source R)
# [1] "2013-03-10 03:59:59 EDT" (TERR)
.deparseOpts
The "noSplitLines" option is available only in Spotfire Enterprise Runtime for R.
dput
See deparse for similar differences.
dQuote
Currently, in Spotfire Enterprise Runtime for R, if the option useFancyQuotes is TRUE,
directional Unicode quotation marks are used, whether or not these characters are supported by the current locale encoding.
Encoding
General warning: Spotfire Enterprise Runtime for R might not
choose the same string encoding as open-source R in all cases. Indeed,
open-source R does not use the same string encoding consistently between
different platforms and locales. Spotfire Enterprise Runtime for R was
designed to be more consistent between different platforms.
- Spotfire Enterprise Runtime for R always uses the UTF-8 character set for the "unknown"
encoding, whereas open-source R uses the native string encoding for
the particular OS where it is running, perhaps because it relies on
native OS routines that depend on that encoding.
- In open-source R, the Encoding<- will not change a string's encoding in
some cases. For example, if a string consists totally of simple ASCII
characters, it seems to have its encoding stuck at "unknown". In
Spotfire Enterprise Runtime for R, Encoding<- will always change the encoding.
- In open-source R, comparing a string with 'bytes' encoding to a string with
'latin1' or 'UTF-8' encoding gives an error. Comparing xb (a
'bytes' string) with xu (a 'unknown' string) does not give an
error, but it acts weird: in some cases, xb==xu, xb<xu,
and xb>xu all return FALSE. Spotfire Enterprise Runtime for R is more consistant: any
'bytes' string is not equal and sorts as less than any non-'bytes'
string.
- Spotfire Enterprise Runtime for R supports automatically converting string encodings on input and
output to the console. See getConsoleEncoding. Open-source R does not support this.
- Spotfire Enterprise Runtime for R provides the function getNativeEncoding for
reading the name of the "native" encoding. Open-source R does not support this.
- It is possible to construct strings with the "UTF-8" encoding that are
not valid UTF-8 byte sequences. In open-source R, attempting to manipulate these
strings can give errors such as "invalid multibyte string". Spotfire Enterprise Runtime for R
internally converts any string to a valid UTF-8 string when doing
string manipulation, so this error should not occur in Spotfire Enterprise Runtime for R. Note
that Spotfire Enterprise Runtime for R does not actually change the bytes in an invalid UTF-8
string (as viewed with charToRaw), but rather converts
the invalid UTF-8 bytes to a valid UTF-8 sequence when needed (see
getValidUtf8).
file.info
In Spotfire Enterprise Runtime for R, 'uid', 'gid', 'uname' and 'grname' fields are never included.
The 'exe' field is provided on all platforms, but says only "no" or "yes". In open-source R on Windows,
it says "no", "win64", or "win32".
format
Calling format.data.frame with zero columns returns a zero-column data.frame
with the same row names (hence number of rows) as the input data.frame. In open-source R,
this call returns an error.
getNativeSymbolInfo
In open-source R, getNativeSymbolInfo returns the address of the routine's entry point or its registration record
(if withRegistrationInfo is TRUE) in the address field. In Spotfire Enterprise Runtime for R, the field always
contains NA. The name of the third field of the return value is a package in open-source R, but it is a DLL in Spotfire Enterprise Runtime for R,
where it is compatible with information returned by getDLLRegisteredRoutines (where open-source R names the field DLL).
grep
grep calls the regexpr function in Spotfire Enterprise Runtime for R implementation.
However, both grep and grepl do not directly call the regexpr function in
open-source R implementation. Internal C functions other than regexpr are called respectively.
iconv
- In open-source R, iconv does not accept the string "native.enc" to
specify the native encoding like other functions.
- Like Spotfire Enterprise Runtime for R, open-source R ignores upper/lower case differences in encoding names,
but open-source R does not ignore characters other than letters and digits. Thus,
open-source R accepts "latin1" but not "latin-1".
- In open-source R, the to argument must exactly match the strings
"latin1" or "UTF-8" for these string encodings
to be marked when mark=TRUE. In Spotfire Enterprise Runtime for R, we also detect aliases
of these encodings.
- In open-source R, if an unconvertable character is found, and sub is not an
NA, the string sub is substituted once for every byte
in the original string character. Spotfire Enterprise Runtime for R substitutes it only once
for the entire unconvertable character.
- In Spotfire Enterprise Runtime for R, the sub string can have only a limited number of
characters (10), or an error is generated.
library.dynam
In open-source R, .dynLibs is used to set the internal list of "DLLInfo" objects,
which is an object with class "DLLInfoList", if new is specified.
Otherwise, it just returns this internal list if new is missing.
In Spotfire Enterprise Runtime for R, .dynLibs is equivalent to getLoadedDLLs, except the DLLInfoList
structure it returns carries no names. The new parameter is ingored.
list.files
Both Spotfire Enterprise Runtime for R and open-source R sort files depending on locale. In the "C" locale
(e.g., Sys.setlocale(locale='C')), characters are
sorted by their ascii codes. As a result, in Spotfire Enterprise Runtime for R, the list.files function lists
all files starting with upper case before listing files starting with lower case.
In open-source R, list.files lists files ignoring the case.
Logic
In open-source R, the negation (!) operator is not a group member of Logic.
Math.Date
Tests using the trunc.POSIXt(x, units = "secs") in open-source R appear to demonstrate problems
with dates after 2038-01-18 19:14:06.
For example:
R> pct <- as.POSIXct(c("2038-01-18 19:14:06.5", "2038-01-18 19:14:07.5"))
R> trunc(pct, "secs")
[1] "2038-01-18 19:14:06 PST" "2038-01-18 19:14:08 PST"
TERR> pct <- as.POSIXct(c("2038-01-18 19:14:06.5", "2038-01-18 19:14:07.5"))
TERR> trunc(pct, "secs")
{[1] "2038-01-18 19:14:06 PST" "2038-01-18 19:14:07 PST"}
nchar
In open-source R, nchar generates an error (or returns NA if
allowNA is TRUE) if the string contains an invalid
multi-byte character sequence and the type argument is "chars" or "width".
norm
Open-source R does not handle complex matrices.
numeric_version
The Spotfire Enterprise Runtime for R functions S_system_version() and getSversion() are non-existent in open-source R,
but they are similar to open-source R functions R_system_version() and getRversion().
OlsonNames
- In open-source R, the time zone database is stored as files within the R distribution (R_HOME/share/zoneinfo, although some platforms will check system-specific locations). Spotfire Enterprise Runtime for R ships with a copy of the time zone database within the distribution for compatibility with R, but does not use it, preferring an internal database of time zones.
- In open-source R, the location of the time zone database can be defined using the environment variable TZDIR. Spotfire Enterprise Runtime for R uses an internal database, and cannot be overriden.
path.expand
In open-source R, path.expand() appears to save the value used for "~" the first time it is called.
Even if the environment variables R_USER, and so on, are changed, further calls to path.expand do not use these environment variables
to determine the value for "~".
In contrast, Spotfire Enterprise Runtime for R reads the current values for R_USER, and so on, whenever path.expand is called.
qr
- In open-source R, LAPACK as.qr always returns an error.
- In open-source R, when x is a matrix of complex data, the QR factorization is always computed
with the LAPACK function ZGEQP3, regardless of the argument LAPACK.
When x is a matrix of non-complex data, and LAPACK is FALSE,
the QR factorization is computed with a particular LINPACK subroutine
DQRDC2 (modified from LINPACK code DQRDC).
When LAPACK is TRUE, the returned qr contains a logical
attribute useLAPACK, set to TRUE.
- The implementation in Spotfire Enterprise Runtime for R has the linear model version of the QR for
complex matrices. Thus using LAPACK = TRUE assigns useLAPCK for
complex matrices, and qrcomplexmatrix may differ from qrcomplex, matrix, LAPACK = TRUE.
- Open-source R ignores the tolerance argument tol when LAPACK = TRUE and rank is
always equal to min(dim(X)) in this case. In Spotfire Enterprise Runtime for R, we have added a rank estimate
based on the tolerance and LAPACK routine dlaic1 (zlaic1).
qr.coef
- In Spotfire Enterprise Runtime for R, the argument k for qr.fitted is not supported and returns an error if used.
- In open-source R, qr.solve returns a vector of zeros when y contains NAs. In Spotfire Enterprise Runtime for R, an
error is returned.
- In open-source R, qr.coef computes the coefficients with the LAPACK
function qr_coef_cmplx for complex data, regardless if qr's
attribute useLAPACK is TRUE or FALSE. For non-complex data, it computes
with the LAPACK function qr_coef_real when useLAPACK is TRUE
and the LINPACK function DQRCF when useLAPACK is FALSE.
- In open-source R, qr.fitted does not support LAPACK QR. It calls the LINPACK function DQRXB.
- In open-source R, qr.resid does not support LAPACK QR. It calls the LINPACK function DQRRSD.
- In open-source R, qr.qy computes the result with LAPACK
function qr_qy_cmplx for complex data, regardless if qr's
attribute useLAPACK is TRUE or FALSE. For non-complex data, it computes
with the LAPACK function qr_qy_real when useLAPACK is TRUE
and the LINPACK function DQRQY when useLAPACK is FALSE.
- In open-source R, qr.qty computes the result with the LAPACK
function qr_qy_cmplx for complex data regardless if qr's
attribute useLAPACK is TRUE or FALSE. For non-complex data, it computes
with the LAPACK function qr_qy_real when useLAPACK is TRUE
and the LINPACK function DQRQTY when useLAPACK is FALSE.
- In open-source R, qr.solve returns the result of qr.coef(a, b), if a is not an object of class qr;
the QR decomposition is computed first, then qr.coef is called.
readBin
- In open-source R, the useBytes argument to writeBin specifies
whether to write encoded strings in a form that can be printed. For
example, if R cannot display Unicode characters, writeBin("\u30A4",f,useBytes=FALSE) would write the bytes for
the string "a<U+30A4>;b", whereas
writeBin("\u30A4",f,useBytes=TRUE) would write the bytes
contained in the string as produced by charToRaw.
- Spotfire Enterprise Runtime for R ignores the useBytes argument, and always writes the
string bytes as produced by charToRaw.
reg.finalizer
The argument e can be any type of object in Spotfire Enterprise Runtime for R.
row.names
Unlike Spotfire Enterprise Runtime for R, open-source R has no function rowIds.
save
- The RFormat argument is Spotfire Enterprise Runtime for R-specific.
- The argument precheck are not supported in Spotfire Enterprise Runtime for R.
seq.Date
-
If from is the last day of the month and by is either "months" or "years",
in Spotfire Enterprise Runtime for R the elements of the resulting sequence always adjust to the last day of month
and no month is skipped or duplicated.
Example
R> seq(as.Date("2000-01-31"), by = "months", length = 12)
[1] "2000-01-31" "2000-03-02" "2000-03-31" "2000-05-01"
[5] "2000-05-31" "2000-07-01" "2000-07-31" "2000-08-31"
[9] "2000-10-01" "2000-10-31" "2000-12-01" "2000-12-31"
TERR> seq(as.Date("2000-01-31"), by = "months", length = 12)
[1] "2000-01-31" "2000-02-29" "2000-03-31" "2000-04-30"
[5] "2000-05-31" "2000-06-30" "2000-07-31" "2000-08-31"
[9] "2000-09-30" "2000-10-31" "2000-11-30" "2000-12-31"
- Unlike open-source R, where exactly two of to, by, and length.out/along.with must be specified,
in Spotfire Enterprise Runtime for R, if only length.out / along.with is specified, by = 1 is assumed.
sequence
sequence(NULL) and sequence(integer(0)) both return integer(0) in Spotfire Enterprise Runtime for R, but return NULL in open-source R.
serialize
The RFormat argument is Spotfire Enterprise Runtime for R-specific.
sink
In open-source R, the file argument must be an open connection
when type="message". In Spotfire Enterprise Runtime for R, it can also be a file name.
solve
- The LINPACK argument, which is available in open-source R, is ignored in Spotfire Enterprise Runtime for R.
- If b contains missing values (NAs), open-source R solve(qr(a), b) returns a vector of zeros; in Spotfire Enterprise Runtime for R an error is returned.
sort
- Open-source R handles only index.return=TRUE when na.last=NA. Spotfire Enterprise Runtime for R is more flexible:
sort(mydata, na.last = TRUE, index.return = TRUE) # Error: "index.return'"only for "na.last = NA"
- The sort algorithms are not the same. The result however, should be the same unless partial is used (in which case
the sort order is undefined for the ranges in between the specified partial indices).
Sys.time
Unlike open-source R, the return value of Spotfire Enterprise Runtime for R's Sys.timezone is platform-independent
and matches the value returned in the Windows version of open-source R.
traceback
If the max.lines argument is NULL or any other
non-numeric value, open-source R prints all of the lines,
whereas Spotfire Enterprise Runtime for R prints only a maximum of 10 lines.
The print.context argument is in Spotfire Enterprise Runtime for R only; it is not in open-source R.
writeChar
- In R, if readChar is called with useBytes=FALSE,
the characters are interpreted according to the "current encoding".
In Spotfire Enterprise Runtime for R, readChar with useBytes=FALSE always
inteprets input characters using the UTF-8 encoding.
- In R, readChar with useBytes=FALSE
reads all UTF-8 byte sequences with two to five bytes.
In Spotfire Enterprise Runtime for R, reading a three-byte UTF-8 sequence encoding a character greater than 0x10FFFF
or trying to read a four or five-byte UTF-8 sequence generates an error,
because these are not valid Unicode characters.
- In R, if writeChar is called with useBytes=FALSE,
it writes characters according to the "current encoding".
In Spotfire Enterprise Runtime for R, writeChar with useBytes=FALSE always
writes characters using the UTF-8 encoding
(except for strings with the "bytes" encoding).
chull
The arguments: peel, maxpeel, onbdy and tol
are not available in Open-source R's chull function.
clusterApply
clusterSplit gives incorrect results in open-source R if
cl has one or fewer nodes, or seq has zero elements.
Spotfire Enterprise Runtime for R handles these cases better, returning a list with length equal
to the number of nodes in cl.
mclapply
Spotfire Enterprise Runtime for R defines mclapply for compatibility with open-source R,
but this function doesn't process list elements in separate parallel
processes.
mcparallel
Spotfire Enterprise Runtime for R defines mcparallel and mccollect for compatibility
with open-source R, but these functions don't evaluate expressions in
separate processes.
Spotfire Enterprise Runtime for R defines mc.reset.stream for compatibility with
open-source R, but this function doesn't reset or affect the random
number generators.
splitIndices
splitIndices gives incorrect results in open-source R if
nx or ncl is less than or equal to one. Spotfire Enterprise Runtime for R handles
these cases better, returning a list with ncl elements.
backSpline
In open-source R, backSpline uses a different algorithm, (usually) resulting in a slightly different splines.
bs
When the number of non-missing values in x is less than 2, Spotfire Enterprise Runtime for R and Open-source R
currently give different results, neither of which is very useful.
ns
When the number of non-missing values in x is less than 2, Spotfire Enterprise Runtime for R and Open-source R
currently give different results, neither of which is very useful.
Box.test
Spotfire Enterprise Runtime for R uses the truncated to integer value of lag,
as does Open-source R
but Spotfire Enterprise Runtime for R also uses the truncated integer value in computing the
degrees of freedom while R does uses the supplied lag value in
computing the degrees of freedom. This is only an issue if the value
specified for lag is not an integer.
Spotfire Enterprise Runtime for R will issue a warning if the combination of lag and fitdf
result in a negative value for the degrees of freedom,
Open-source R does not warn.
In this situation, both Spotfire Enterprise Runtime for R and Open-source R will report NA for
the test p-value.
cor.test
When method="kendall", exact=TRUE, and length(x)>8,
the exact p-values computed in Spotfire Enterprise Runtime for R differ from open-source R
by a small amount (usually less than 1e-3).
This may be due to a different algorithm (that is, AS 71) is used in Spotfire Enterprise Runtime for R.
cutree
The group numbering might be different between Spotfire Enterprise Runtime for R and open-source R, but the
group memberships are the same.
In open-source R, when k is NULL, and if
the "height" component of tree is not sorted,
cutree is stopped. Spotfire Enterprise Runtime for R sorts the "height" component to
ensure "height" is ordered as increasing.
dist
In open-source R, the definition of the canberra method is to divide by
the absolute value of the sum of the variable values. This matters only when values are negative.
effects
In open-source R, when effects component of object is NULL,
effects is stopped with an error. In Spotfire Enterprise Runtime for R, it returns NULL.
factanal
The Spotfire Enterprise Runtime for R factanal uses a different algorithm for computing
the MLE estimates so the results can be slightly different.
The return value from Spotfire Enterprise Runtime for R does not include the rotmat
component when a rotation is performed.
The current Spotfire Enterprise Runtime for R version of factanal produces the same
results as factanal in S-PLUS.
filter
NA handling for recursive filtering differs between Spotfire Enterprise Runtime for R and open-source R.
In Spotfire Enterprise Runtime for R, all values after an NA is encountered in x become NA.
fisher.test
R allows alternative to be "less" or "greater"
as well as the default value of "two-sided".
These alternatives are not yet implemented in Spotfire Enterprise Runtime for R.
If one of the unimplemented alternatives is specified,
a warning is issued and the default method ("two-sided") is used.
hclust
Open-source R gives an error when the input d is a symmetric matrix,
while Spotfire Enterprise Runtime for R allows it.
The methods: "mcquitty", "ward", "median"
and "centroid"
which are available in R are not yet implemented in Spotfire Enterprise Runtime for R.
If one of the unimplemented methods is specified,
a warning is issued and the default method ("complete") is used.
Hypergeometric
- In open-source R, dhyper accepts only integer values. phyper, qhyper, and rhyper allow non-integer values for m, n, and k, but the values are rounded.
- In Spotfire Enterprise Runtime for R, for consistency the values for m, n, and k must be integers.
kmeans
The methods "Lloyd", "Forgy" and "MacQueen",
which are available in R, are not yet implemented in Spotfire Enterprise Runtime for R.
If one of the unimplemented methods is specified,
a warning is issued and the default method ("Hartigan-Wong") is used.
ks.test
- When the alternative ="two.sided" and exact=FALSE, and for both one-sample and two-sample tests,
the p-values computed in Spotfire Enterprise Runtime for R differ from open-source R by a small amount (usually less than 1e-3).
This may be due to the algorithm used is not exactly the same in Spotfire Enterprise Runtime for R and open-source R.
- The argument y, if set to an a character string, specifies
the function that generates p-values for the hypothesized distribution.
The argument distribution in Spotfire Enterprise Runtime for R is similar to that found in S-PLUS
as an alternative way to specify the hypothesized distribution.
lag
In open-source R, the return value keeps the attribute of input object, whereas in Spotfire Enterprise Runtime for R, the return value is a "ts" object.
model.tables
The argument "type" for "feffects" and "residuals" are not implemented in open-source R.
optim
Spotfire Enterprise Runtime for R does not support the "Brent" optimization method.
ppoints
The ppoints function in open-source R does not have the weights argument.
princomp
- In Spotfire Enterprise Runtime for R, the returned component terms is
like that from S-PLUS, which is not supported in open-source R.
- The returned value is different when the argument scores is numeric
or TRUE in Spotfire Enterprise Runtime for R, but they are same in open-source R.
shapiro.test
When you run the shapiro.test on a dataset
with missing values (NA),
Spotfire Enterprise Runtime for R reports a warning about NAs that is not shown in R.
(The test output is the same.)
In R, shapiro.test fails if the data includes Infs.
Spotfire Enterprise Runtime for R removes the non-finite value(s), issues a warning about them,
and then runs the test on the remaining values.
smooth.spline
This function is based on the S-PLUS implementation and has not been
completely converted to the R parameterization. The spar
parameters do not match: They are on the same scale, but differ
by a constant. Several arguments used in the R implementation are
included here but not used. This implementation might choose a slightly
rougher spline fit than the implementation in open-source R.
t.test
The argument "treatment" is not in open-source R.
terms
abb, neg.out and as.terms are not implemented in
open-source R. The object attribute - formula is removed in open-source R.
Uniform
- In open-source R, min = max is allowed for {p,q,r}unif but dunif(2, 2, 2) returns NaN and generates a warning.
- In Spotfire Enterprise Runtime for R, min = max is allowed for all {d,p,q,r}unif and dunif(2, 2, 2) returns Inf.
colMedians
colMedians, colQuantiles, and colProds are not in open-source R.
colMins
colMins, colMaxs, colRanges, rowMins, rowMaxs, and rowRanges are not in open-source R.
colVars
- Spotfire Enterprise Runtime for R accepts vectors but open-source R does not.
rowMeans and colMeans both return NaN if there are no values; open-source R returns NA:
Example
rowMeans(matrix(NA), na.rm=T)
-
All functions listed in this alias are generic functions;
methods currently exist for data.frame, resamp, and series.
- colVars, colStdevs, rowVars, rowStdevs are not supported by open-source R but they are
supported in Spotfire Enterprise Runtime for R.
- colSums, rowSums, colMeans and rowMeans are implemented both in open-source R and Spotfire Enterprise Runtime for R, but there are more arguments in Spotfire Enterprise Runtime for R implementation:
weights, freq and n. All of these may not be present.
- colSums, rowSums, colMeans and rowMeans are NOT generic functions in open-source R.
is.number
is.number is not implemented in open-source R.
ndotargs
This function does not exist in open-source R.
stdev
stdev is not in open-source R.
startDynamicHelp
- R does not maintain the server URL in tools:::httpdUrl.
- R uses R_DISABLE_HTTPD instead of TERR_DISABLE_RDHTTPD as the
name of the environment variable to disable starting the HTTP help server.
apropos
In open-source R, what must be a character vector.
browseURL
In open-source R, when browser is not NULL, the
function "browseURL" fails to run.
count.fields
Open-source R does not have the nmax argument.
find
In open-source R, what must be a character vector.
help.start
The update argument is not used by Spotfire Enterprise Runtime for R.
In open-source R, this argument is used to update the file
R_HOME/doc/html/packages.html. In Spotfire Enterprise Runtime for R, this information is maintained
internally to Rdhttpd and is generated dynamically on request.
localeToCharset
- In Spotfire Enterprise Runtime for R, this function currently returns the single encoding
"UTF-8" for all locales except for the locale "C", where it
returns "ASCII".
- In open-source R, this function returns one or more encodings that are suitable
for the locale.
ls.str
In open-source R, the name argument seems to be ignored.
packageDescription
In Spotfire Enterprise Runtime for R, the encoding argument is not implemented.
If this argument is given, a warning is generated.
remove.packages
- In R, the argument lib is given without the default NULL value.
- In R, this function does not display a
warning for the packages in use. No warning is given if the specified package is
not found in the specified library.
- In R, after the specified package(s) are removed, the HTML index of
packages is updated.
str
- The output from str() is roughly, but not exactly, the same.
- The arguments 'vec.len', 'nchar.max', 'envir', 'strict.width' and 'formatNum' are not yet supported (so they are ignored) in Spotfire Enterprise Runtime for R.
- The methods str.dendrogram and str.logLik are not implemented in Spotfire Enterprise Runtime for R.
R Version
R-4.0.2