Re: [R] Proper way to implement package internal functions

2013-06-12 Thread Duncan Murdoch
On 12/06/2013 10:44 AM, Bryan Hanson wrote: [previously posted on Stack Overflow: http://stackoverflow.com/questions/17034309/hiding-undocumented-functions-in-a-package-use-of-function-name ] I've got some functions I need to make available in a package, and I don't want to export them or

Re: [R] Proper way to implement package internal functions

2013-06-12 Thread Bryan Hanson
Thanks Duncan... Silly me, it's section 1.6.1 not version 1.6.1! So this warning from check is not a problem in the long run: * checking for missing documentation entries ... WARNING Undocumented code objects: ‘ang0to2pi’ ‘dAB’ ‘doBoxesIntersect’ ... All user-level objects in a package should

Re: [R] Proper way to implement package internal functions

2013-06-12 Thread Rolf Turner
On 13/06/13 03:34, Bryan Hanson wrote: SNIP So this warning from check is not a problem in the long run: * checking for missing documentation entries ... WARNING Undocumented code objects: ‘ang0to2pi’ ‘dAB’ ‘doBoxesIntersect’ ... All user-level objects in a package should have

Re: [R] Proper way to implement package internal functions

2013-06-12 Thread Michael Weylandt
On Jun 12, 2013, at 16:34, Bryan Hanson han...@depauw.edu wrote: Thanks Duncan... Silly me, it's section 1.6.1 not version 1.6.1! So this warning from check is not a problem in the long run: * checking for missing documentation entries ... WARNING Undocumented code objects:

Re: [R] Proper way to implement package internal functions

2013-06-12 Thread Bryan Hanson
Hi Rolf... Thanks. I discovered the approach you described by looking at the source for spatstat, which as it turns out does exactly that. I also discovered by testing that if you don't export a pattern, but rather export the specific names, not including the functions one wants to hide,