[Biococoa-dev] RE: Nomenclature
Koen van der Drift
kvddrift at earthlink.net
Sat Aug 14 08:27:03 EDT 2004
On Aug 13, 2004, at 1:41 PM, Alexander Griekspoor wrote:
> I was thinking of the following two options, but perhaps someone comes
> up with something must better.
>
> BCRecord - Based on a record from a nucleotide database like entrez.
> (BCEntry would be another variant). Advantage: familiar setup
> (sequence, name, features, etc). Disadvantage: sometimes it's a bit
> strange to call things a record, like if you're cloning for instance,
> your not messing around with BCRecords. But perhaps in this case you
> are busy with BCFragments, derived from a BCRecords so it's not that
> bad after all.
>
> BCEntity - My favorite. BCUnit is to boring, but a more general,
> "building block of our framework" name would perhaps be apporiate
> here. Anyway, you might be laughing at it right now...
>
What about BCObject or BCRoot? Boring but effective.
Silly solutions are BCLego, BCTwoByFour, BCBrick, etc. Peter is
remodelling his house, he might have even more suggestions :)
>> And the second method (which I wrote this morning) looks like:
>> - (BOOL) representsBase: (BCSequenceDNABase *) entry {
>> if ( [[self matches] containsObject: entry] )
>> return YES;
>> return NO;
>> }
> Really elegant!
>
Even shorter:
- (BOOL) representsBase: (BCSequenceDNABase *) entry
{
return [[self matches] containsObject: entry];
}
- Koen.
More information about the Biococoa-dev
mailing list