Currently, there are two ways to encode markers: vectors (legacy) and matrices (new encoding) - see ?markers. Some functions have been updated to deal with both (see issue #52). There are a few possibilities for the future:
update some functions/methods to deal with vector/matrix markers and assume that the legacy infrastructure/functionality will only deal with vector markers, and new functionality will mainly deal with either matrix markers of both. Update accordingly.
update all functions/methods to deal with vector/matrix markers
Refactor everything to use matrix markers - note that there exists already converters, namely mrkVecToMat, mrkMatToVec and friends
Develop a dedicated markers S4 infrastructure to deal with any implementation in a transparent way (from user point of view)
These are the functions (don't think methods would be caught by this) that have formals that match fcol (including *fcol*).
Currently, there are two ways to encode markers: vectors (legacy) and matrices (new encoding) - see
?markers
. Some functions have been updated to deal with both (see issue #52). There are a few possibilities for the future:mrkVecToMat
,mrkMatToVec
and friendsThese are the functions (don't think methods would be caught by this) that have formals that match
fcol
(including*fcol*
).