Skip to content
Prev 75198 / 398502 Next

modifying argument of a .C call (DUP=FALSE)

Tamas K Papp <tpapp at princeton.edu> writes:
It's more a question of whether the dangers affect you. In general,
the issue is that you risk modifying a second (virtual) copy of the
data along with the one you intend to modify. If you're sure that you
don't have any, the point is moot. It is fairly difficult to be sure
of that in the general case, which is why we generally discourage
DUP=FALSE, especially for package writers, but for personal use you
might just get away with it.