[Bioc-devel] prada package and eSet in Biobase

[Vincent Carey 525-2265]

>
> Instead, we propose that users like Martin create a subclass of eSet
> with enough supporting infrastructure (initialize method, validity
> checking) to ensure the proper structure is available.  This way, you
> don't have to know Martin very well (you should, he's a great guy), he
> has put everything you need to know into the class definition.  You
> can reuse his code.

This is a tremendous step forward.  It is a bit painful to program
these seemingly purely infrastructural elements (initialize/validity)
but -- I think it is a reasonable hope, but there is some risk
involved -- once we get these habits in place, things should work
together much more reliably.

Now, how can we help in this part of the programming  discipline?
Is it possible to generate useful stubs?

I really enjoyed reading to the end of Seth's email -- I recommend
it to the core, and eventually it should be part of a best practices
document that we serve to the developer community.

(And of course I reserve the right to retract anything I have just written
at any time.)