[Bioc-devel] avoiding clashes of different S4 methods with the same generic
Yes, but "monkeyBars" doesn't have quite the same pithiness for a package name. Anyway, the dual dispatch mechanism sounds most interesting. I assume that means we'd have to define some sort of base "normalizeParam" class, and then derive "csawNormParam" and "swingsNormParam" subclasses, so that specific methods can be defined for each signature. - Aaron
Martin Morgan wrote:
On 04/26/2016 05:28 PM, Michael Lawrence wrote:
On Tue, Apr 26, 2016 at 2:16 PM, Martin Morgan <martin.morgan at roswellpark.org> wrote:
On 04/26/2016 04:47 PM, Michael Lawrence wrote:
On Tue, Apr 26, 2016 at 11:00 AM, Aaron Lun<alun at wehi.edu.au>
wrote: ...
BiocGenerics. However, if some other hypothetical package
(I'll call it
"swings", for argument's sake) were to define a normalize()
method with a ...
I like the dual dispatch method quite a bit (but wonder why we get
several
swings but only one csaw? Maybe a csaw implies two participants
[though I
think I once in a while csaw-ed alone], so a singular csaw and a
pair of
swings balance out?), partly because it's very easy to extend
(write another
method) and the second argument can be either lightweight or
parameterized.
I could go along with the dual dispatch. "Swings" is short for "Set of swings". Usually, there are several swings in a row, but only one see-saw.
Googling for "how many swings per see-saw" took me to https://www.cpsc.gov//PageFiles/108601/playgrnd.pdf where it is apparent that swings are much more dangerous than see-saws (e.g., 51 matches for "swing" versus 4 for "see-saw"; "Swings ... were involved in about 19 ... percent of injuries ... See-saws accounted for about three percent"; "Homemade rope, tire, or tree swings were also involved in a number of hanging deaths" [no mention of death by see-saw]). I think for the sake of our users, especially our younger users, we do not want to consider swings, or even methods on swings, further. Martin This email message may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited. If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you.