[Biococoa-dev] Sequence Structure
Koen van der Drift
kvddrift at earthlink.net
Wed Jul 13 13:26:16 EDT 2005
On Jul 13, 2005, at 11:30 AM, Charles Parnot wrote:
> We should only do the caching for the immutable object. For the
> mutable one, it does not make much sense. If the user needs the
> symbol array all the time while changing the sequence string, AND
> needs performance, the final application is doomed anyway ;-)
> Then caching on the immutable sequence is trivial. It can be done
> in the accessor. To avoid memory issues, we could set an arbitrary
> threshold above which no caching occurs.
> ABout the sequenceData ivar (probably better to keep the name a bit
> longer, 'data' would really be too generic, in my opinion; and who
> knows, maybe later we will need another 'xxxData' ivar), I would
> type it to a NSMutableData in the interface. And then, in the init
> method, create an NSData (we might need just one cast there). This
> way, we won't get compiler warnings in the methods for the mutable
> class (otherwise we would have to cast the NSData into an
> NSMutableData in too many places).
I'll try that - I have some more time tonight.
> Have fun coding! BTW, we have to solve the Xcode 2/2.1 issue.
I have recently switched to Tiger and Xcode 2.1, so not an issue for
me anymore. I think I was the only one not yet on Tiger.
More information about the Biococoa-dev