[R-pkg-devel] fate of functions with periods in name

2018-09-12 Thread Paul Johnson
I have not introduced functions with periods in their name before, but recently I wanted to put a new version of "rbind.fill" in my package rockchalk. When I do the package check with R-3.5.1, I see a package build warning: Found the following apparent S3 methods exported but not registered: rb

Re: [R-pkg-devel] Package Etiquette

2018-09-12 Thread Robert M. Flight
Of course, if you do truly decide to *copy* a function from another package, make sure everything is licensed appropriately and the authors given attribution! -Robert On Wed, Sep 12, 2018, 8:09 AM Robert M. Flight wrote: > Regarding still wanting to copy functions situation, I did this for my >

Re: [R-pkg-devel] Package Etiquette

2018-09-12 Thread Robert M. Flight
Regarding still wanting to copy functions situation, I did this for my knitrProgressBar PKG, as it makes the progress R6 object from dplyr a first class citizen of the PKG, and dplyr has a lot of dependencies that I didn't want to force just to use their pre-existing progress bar. Robert On Wed,

Re: [R-pkg-devel] Package Etiquette

2018-09-12 Thread Killick, Rebecca
To add my two-pence regarding duplication. I think this is a judgement call. If the functionality would be precisely the same and for the same situations then there are some instances where you would still want to duplicate but generally probably not. An example would be where the function is s