On 29.01.2016 15:21, Berry Boessenkool wrote:
Hi,
in our Berlin R User Group meeting yesterday we talked about dependencies in
package development.
One thing that came up is that it's a good practice to explicitly write
package::function in the code.
Is it worth to go through all of my package and enhance the code in all
instances?
No, *if* you import anyway (see below).
Or do you think that NAMESPACE sufficiently prevents using a function with the
same name from another package than intended and people reading source code
should be aware of that anyways?
Yes.
If Answer1==YES:
Should I also refer to other functions within my own package through
myPackage::otherFunction?
Yes, *if* you only suggest the package and do not import from the
namespace unconditionally, you should do that.
Best,
Uwe Ligges
Should I do that for base packages like graphics, stats, utils, grDevices? (we
have to declare them in the NAMESPACE imports, after all)
What's a fast and easy way to find all the instances of 'external' function
usage?
I guess there must be discussions and guidelines about this, so some pointers
instead of answers would be fine as well.
Thanks ahead,
Berry
[[alternative HTML version deleted]]
______________________________________________
[email protected] mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
______________________________________________
[email protected] mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
