phidauex
10-08-2002, 11:27 AM
Hi,
I'm learning C programming, and just picked up a book on Carbon (Learning Carbon, the o'reilly one). I was more interested in learning Cocoa, because by all accounts its the 'bees knees' for OS X. However, since its based on object oriented languages (which I haven't even touched), it wasn't a reasonable goal. But since Carbon programs can be written in C, its right up my alley.
I've heard a lot of disparaging things about Carbon, in the sense that people brag about having a program in Cocoa, developers talk about how good it would be to rewrite in cocoa, all the cool cocoa features like services and spellchecking, and stuff like that. I've also heard claims that Carbon isn't as stable, isn't as fast, etc. However, I've also heard general claims that Carbon can be just as fast, just as stable, and have all the cool features of Cocoa, if the program is 'done right'.
So anyway, my question is this: Is there anything I should look out for as a beginning carbon programmer to make sure my programs are 'done right'? Obviously simply getting them to run right is the first hurdle, but there are lots of resources out there for that, but is there any antecdotal advice anyone has for making fast stable osx-feature rich carbon apps? Any bad habits or traps I should avoid?
Thanks!
Sam
I'm learning C programming, and just picked up a book on Carbon (Learning Carbon, the o'reilly one). I was more interested in learning Cocoa, because by all accounts its the 'bees knees' for OS X. However, since its based on object oriented languages (which I haven't even touched), it wasn't a reasonable goal. But since Carbon programs can be written in C, its right up my alley.
I've heard a lot of disparaging things about Carbon, in the sense that people brag about having a program in Cocoa, developers talk about how good it would be to rewrite in cocoa, all the cool cocoa features like services and spellchecking, and stuff like that. I've also heard claims that Carbon isn't as stable, isn't as fast, etc. However, I've also heard general claims that Carbon can be just as fast, just as stable, and have all the cool features of Cocoa, if the program is 'done right'.
So anyway, my question is this: Is there anything I should look out for as a beginning carbon programmer to make sure my programs are 'done right'? Obviously simply getting them to run right is the first hurdle, but there are lots of resources out there for that, but is there any antecdotal advice anyone has for making fast stable osx-feature rich carbon apps? Any bad habits or traps I should avoid?
Thanks!
Sam