<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; ">Hey Alex,<DIV><BR class="khtml-block-placeholder"></DIV><DIV>nice to hear something from the netherlands :-).</DIV><DIV><BR><DIV><DIV>Am 03.07.2005 um 13:46 schrieb Alexander Griekspoor:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">- The class cluster design of sequence objects. Is it still necessary, is it correct, flexible? As said, phil and I had problems with it, and phil was not sure if it was implemented fully correct, but he'll chime in I guess<BR></FONT></P></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV><DIV>There is a structural failure in our implementation, the user thinks he will get a BCSequence object, when he calls a init or convenient method of BCSequence, but he gets a BCAbstractSequence. So we have to fix the inheritance model.</DIV><BR><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">. Purely from complexity towards novel users (and people like me who had to get back in again ;-), I would like to see it disappear if possible.</FONT></P> </BLOCKQUOTE></DIV><BR></DIV><DIV>thanks for mention the class cluster problem. Here is a short description of my understanding of a class cluster:</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>A class cluster like NSNumber is intransparent to the user of the framework. The user just knows the NSNumber class, but the functionality and content of the class depends on the constructor and initialization of the class. NSDoubleNumber, NSIntegerNumber etc have all private headers, so the user doesn't know the class exists.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>---> In our implementation is all visible to the user... (public headers for BCSequenceProtein etc.)</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I think we should go for a simple superclass class structure not to confuse the users of the framework.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>cheers,</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Phil</DIV></BODY></HTML>