That is the exact opposite of what I have heard everyone else say! Have you checked out that obj c to js thing?
Mike Harper
posted
Yeah. It is weird at first, but once you get used to it, it seems better... sorta like everything else apple does/uses.
Derek Brooks
posted
I like the method calling convention, but the memory model confuses me. Not sure when to deallocate...
Benjamin Garrett
posted
When you pull out, you deallocate.
Mike Harper
posted
agree with ben. it is confusing. but i think that you only have to dealloc when you explicitly call alloc. i think that if you use helper methods to initialize things, they always clean up the memory for you.
...or you could just dealloc everything and then remove the deallocs that cause your app to not compile. ;)
facebook comments
That is the exact opposite of what I have heard everyone else say! Have you checked out that obj c to js thing?
Mike Harper posted
Yeah. It is weird at first, but once you get used to it, it seems better... sorta like everything else apple does/uses.
Derek Brooks posted
I like the method calling convention, but the memory model confuses me. Not sure when to deallocate...
Benjamin Garrett posted
When you pull out, you deallocate.
Mike Harper posted
agree with ben. it is confusing. but i think that you only have to dealloc when you explicitly call alloc. i think that if you use helper methods to initialize things, they always clean up the memory for you.
...or you could just dealloc everything and then remove the deallocs that cause your app to not compile. ;)
Derek Brooks posted
Yeah, you want to control where you dealloc.
Mike Harper posted
your comments