Re: Abstract class with single subclass
Re: Abstract class with single subclass
- Subject: Re: Abstract class with single subclass
- From: Michael Ash <email@hidden>
- Date: Wed, 27 May 2009 21:42:52 -0400
On Wed, May 27, 2009 at 5:37 PM, Seth Willits <email@hidden> wrote:
> I know this isn't exactly a very detailed description, but if they were
> equivalent, then changing [self class] to self shouldn't have fixed it, but
> it did. Pretty weird.
Does not follow. It's quite common in C-based languages to have broken
code which only manifests bugs in a certain machine context. (For
example, reading from unintialized memory.) Code which is logically
equivalent will not necessarily generate the same machine code, thus
you can have two pieces of logically equivalent code but only have one
of them set you up for a crash due to a bug elsewhere.
Mike
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden