[Biococoa-dev] NSMutableData vs malloc

[Charles Parnot]

Sorry, what I meant is we should use

+ (id) symbolForChar: (unsigned char)aSymbol

and not

+ (id) symbolForChar: (unsigned char *)aSymbol


because the latter implies that we are using an array of char for  
each symbol, and would require us to pass an array of char as  
argument to the method, instead of just a char.

I don't remember all the details of the implementation right now, and  
I probably should have a look before commenting too much, but I hope  
you see what I mean :-)

BTW, I checked out the code lately, and I have not seen the xcodeproj  
file in the folder. The project still loads OK (I had to upgrade),  
but I am not sure I got the right settings, as I had to use the old  
pbproj file to open the project.

charles


On Jul 17, 2005, at 9:56 AM, Koen van der Drift wrote:

>
>
>
> On Jul 17, 2005, at 12:02 PM, Charles Parnot wrote:
>
>
>> I don't see why we can't keep simply
>>
>> + (id) symbolForChar: (unsigned char)aSymbol
>>
>> There is a direct correspondance between BCSymbol and char, so a  
>> BCSymbol is defined by a char, not a string. I should have a look  
>> at the code to help better, but maybe there is some confusion  
>> happpeing when switching between NSString and char* and char...
>>
>>
>
>
> We now use the symbolString to retrieve info from the  
> propertiesDict, eg:
>
>         symbolInfo = [[[BCAminoAcid aaPropertiesDict] objectForKey: 
> [self symbolString]] copy];
>
>
> And it is also used in BCCodon.
>
> So we might need to keep the symbolString around, otherwise we need  
> to create the NSString on the fly everytime.
>
>
> cheers,
>
> - Koen.
>

--
Xgrid-at-Stanford
Help science move fast forward:
http://cmgm.stanford.edu/~cparnot/xgrid-stanford

Charles Parnot
charles.parnot at gmail.com