I'm just thinking out loud about this one. So far I was saving all package-specific settings in options
. I have some experience with ReferenceClass
es (thanks to Rook
), and I've seen that knitr
uses RC to save package-specific staff. I'd like to know more about pros/cons of both approaches. Or maybe you'd like to recommend another approach (e.g. sourcing R file located in getwd()
on startup, much like devtools
and .Rpackages
)?
Ideas?
You can also store options in an environment
stored at the top-level of your package. That may be closest to options()
use, while avoiding the global variable.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With