Standard forensics

[rjmccall]

My life mutates and evolves, its vines clinging to the clay, cutting grooves in no particular pattern but gradually giving me form. Watching its progress is curious; are those tendrils so unlike the roots of these trees? Well, anyway

Comments

[dvarin]

I am curious about the side effects of l-value to r-value conversion here. How could anyone tell whether you did it or not?
(Related to this is: If the answer to the preceding is "No one can," then it's not so much adding or removing a wart so much as it is just changing the color of one.)

[rjmccall]

Oh, sorry. The way you convert an l-value (the location of an value stored in memory) into an r-value (an actual value) is you initialize a temporary with the value in memory. For non-class types, that means executing actual machine load instructions; for class types, that means calling a copy constructor, which then generally executes actual machine loads and stores

[nickjong]

Cool, I didn't know ARC was you. Nice!

[aleffert]

I tried to use arc briefly for a new project, but it freaked me out. In particular, I couldn't figure out if

self.someProperty = [[SomeClass alloc] init];

Was the right thing or not. It seems like it should be a leak. If it's not, I'm freaked out since all the naming conventions are out the window. If it is, I couldn't figure out how to fix it, because, release and autorelease are invalid.

[aleffert]

I should add that I was excited about using it in the first place and I think this is mostly a documentation issue. So good job!

[rjmccall]

It's not a leak. Don't freak out. :) The naming conventions aren't out the window; it's just that ARC enforces them for you, and does the right thing in response to them. So in this case, ARC knows that -init returns a retained pointer, and it knows it needs to balance that out at some point, and so it does.