On Jan 18, 2010, at 23:06 , Bryan McLellan wrote:
My company recently started using a R library
I suspect you meant R package as R libraries have no DESCRIPTION ...
from RCRAN that is licensed under the LGPL Version 2 or greater per
the DESCRIPTION file, but contains no copy of the LGPL
On Mon, 18 Jan 2010, Bryan McLellan wrote:
My company recently started using a R library from RCRAN that is
licensed under the LGPL Version 2 or greater per the DESCRIPTION file,
but contains no copy of the LGPL notice, or any copyright notice. I've
grown accustomed to paying attention to
Is it safe to call setGeneric twice, assuming some setMethod's for the
target function occur in between? By safe I mean that all the
setMethod's remain in effect, and the 2nd call is, effectively, a no-op.
?setGeneric says nothing explicit about this behavior that I can see.
It does say that if
On 1/19/10 10:01 AM, Ross Boylan wrote:
Is it safe to call setGeneric twice, assuming some setMethod's for the
target function occur in between? By safe I mean that all the
setMethod's remain in effect, and the 2nd call is, effectively, a no-op.
?setGeneric says nothing explicit about this
Thanks,
the universal MacOS X binaries are now updated/built, which are what
the CRAN package pages refer to.
Just for others information: I've been emailing offline with Simon U
(maintainer), and it turns out that my initial posts to him
regarding these issues went into his spam folder.
On Tue, 2010-01-19 at 10:05 -0800, Seth Falcon wrote:
This came up because of some issues with the sequencing of code in
my
package. Adding duplicate setGeneric's seems like the smallest, and
therefore safest, change if the duplication is not a problem.
I'm not sure of the answer to
On 1/19/10 11:19 AM, Ross Boylan wrote:
If files that were read in later in the sequence extended an existing
generic, I omitted the setGeneric().
I had to resequence the order in which the files were read to avoid some
undefined slot classes warnings. The resequencing created other
problems,
On Tue, 2010-01-19 at 12:55 -0800, Seth Falcon wrote:
I would expect setGeneric to create a new generic function and
nuke/mask
methods associated with the generic that it replaces.
I tried a test in R 2.7.1, and that is the behavior. I think it would
be worthwhile to document it in
