Displaying 2 results from an estimated 2 matches for "normalizelowess".
2003 Feb 20
2
Who to decide what a generic function should look like?
...e" for my microarray
package and expect it to work together with other package defining a
generic function with the same name. Some short-term and long-term
outcomes from this are:
* Each developer who cares has to come up with a less general name
than "normalize", e.g.
"normalizeLowess". However, this will still not guarantee you that
there will not be any
naming conflict with other, to you unknown or future upcoming,
packages. People will have
to create extremely awkward method names to make there generic
functions unique. This is
already happening today (and...
2003 Feb 20
2
Who to decide what a generic function should look like?
...e" for my microarray
package and expect it to work together with other package defining a
generic function with the same name. Some short-term and long-term
outcomes from this are:
* Each developer who cares has to come up with a less general name
than "normalize", e.g.
"normalizeLowess". However, this will still not guarantee you that
there will not be any
naming conflict with other, to you unknown or future upcoming,
packages. People will have
to create extremely awkward method names to make there generic
functions unique. This is
already happening today (and...