Certain functions and function arguments are still provided for
compatibility with older versions of oce, but will be removed soon.
The oce scheme for removing functions is similar to that used by
Bioconductor: items are marked as "deprecated" in one release, marked as
"defunct" in the next, and removed in the next after that. This goal is to provide a
gentle migration path for users who keep their packages reasonably
The following are marked "deprecated" in the present CRAN release of oce. Please use the replacement functions as listed below. The upcoming CRAN release of oce will mark these as "defunct", which is the last step before outright removal.
The following are marked "defunct", so calling them in the the present version produces an error message that hints at a replacement function. Once a function is marked "defunct" on one CRAN release, it will be slated for outright deletion in a subsequent release.
The following were removed after having been marked as "deprecated" in at least one CRAN release, and thereafter as "defunct" in at least one CRAN release. (The version number in the table is the first version to lack the named function.)
Several oce function arguments are considered "deprecated", which means they will be marked "defunct" in the next CRAN release. These are normally listed in the help page for the function in question. A few that may be of general interest are also listed below.
endian argument of
byteToBinary() will be removed sometime
in the year 2017, and should be set to
"big" in the meantime.
Several ‘oce’ function arguments are considered "defunct", which means they will be removed in the next CRAN release. They are as follows.
date argument of
was discovered to have been unused in early 2016. Since
startTime actually fills its role,
was considered to be deprecated in June 2016.
quality flag of
marked as deprecated in March 2016.
fill argument of
mapPlot() was confusing
to users, so it was designated as deprecated in June 2016.
(The confusion stemmed from subtle differences between
polygon(), and the problem is that
mapPlot() can use either of these functions, according
to whether coastlines are to be filled.)
The functionality is preserved, in the
The ‘Bioconductor’ scheme for removing functions is described at https://www.bioconductor.org/developers/how-to/deprecation/ and it is extended here to function arguments.