Re: More 10.1 backward compatibility
Re: More 10.1 backward compatibility
- Subject: Re: More 10.1 backward compatibility
- From: Philip George <email@hidden>
- Date: Mon, 16 Dec 2002 13:06:52 -0600
What happens when you compile on 10.1?
- Philip
On Monday, December 16, 2002, at 08:40 PM, Drew McCormack wrote:
As much as everyone is probably sick to death of this topic, I still
haven't found a satisfactory answer in the archives, so I will ask
anyway.
My program, compiled on 10.2 with gcc3.1, crashes without any warning
on 10.1, and leaves nothing behind in terms of logs etc. I think I
know which section of code is at fault: I recently made changes there
which broke the backward-compatibility. I want to keep the changes, so
going back to the old code is not an option.
I have setup the availability macros described in Apple's doc to
compile for 10.1, and determined that there are no methods being
called that were not supported in 10.1.
I have checked the code to see if there are any "extern" variables
from the frameworks, but cannot see any.
Someone mentioned in the archives that "Class" objects could cause
problems, but I don't really understand this. Is this true, and if so,
in what circumstances? My code makes use of NSStringFromClass,
NSClassFromString, and also "Class" objects. Could this be the
problem, and if so, why?
Drew McCormack
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.