On Fri, May 1, 2009 at 4:54 PM, Erik Buck wrote:
> There is nothing to add now (13 years later):
That's a bit bold, isn't it? Sure, the primitives and research might
not have changed all that much, but the technology sure has. We now
have GPGPU and the prospect of manycore Larabee, both thrusti
The whole debate about mutable and immutable classes, the inheritance
hierarchy, what it means to return a pointer to a supposedly immutable object,
what it means to store a pointer to a supposedly immutable object, the
"substitutability" principle of object oriented programming, whether
altern
On Apr 30, 2009, at 6:47 PM, Ali Ozer wrote:
[...]
What I don't get is... why is there NSMutableString and NSString?
#1. It seems weird to me that a string object can't be modified
once it's
created. Why is this?
Immutable objects are useful for various reasons:
- Knowing that they can'
I am pretty new to objective-c, and I've been going over some stuff
in a book I
bought, and there is just something that is really bothering me. I
can't
really ask the author a question about his paragraph, so I thought
I'd write
here instead.
So--- This has to do with arrays, dictionarie
Hi everyone,
I am pretty new to objective-c, and I've been going over some stuff in a book I
bought, and there is just something that is really bothering me. I can't
really ask the author a question about his paragraph, so I thought I'd write
here instead.
So--- This has to do with arrays, dict