Re: Calling fopen() from a simple C++ program in Xcode 5.0.2 raises EXC_BAD_ACCESS, code=2
Re: Calling fopen() from a simple C++ program in Xcode 5.0.2 raises EXC_BAD_ACCESS, code=2
- Subject: Re: Calling fopen() from a simple C++ program in Xcode 5.0.2 raises EXC_BAD_ACCESS, code=2
- From: Quincey Morris <email@hidden>
- Date: Tue, 31 Dec 2013 13:19:31 -0800
On Dec 31, 2013, at 12:43 , Dan Korn <email@hidden> wrote:
> they informed me that my brand-new MacBook Pro would not run Mountain Lion; the hardware is not compatible. Apparently the "late 2013" models which come with Mavericks pre-installed can't run any other versions of OS X.
> as far as I know, this is the first time that Apple has released hardware that won't run at least one previous version of the OS.
No, it’s always like this, but our brains aren’t wired to understand it naturally. I get caught by this repeatedly, too.
What you’re asking for is OS X versions to run on at least one *future* version of the hardware, and even Apple can’t bend time that way.
Specifically, Mountain Lion doesn’t know about the new hardware features of the just-released Macs, therefore it won’t run on them. For example, perhaps, the new Mac has a different power management chip, which responds to a different set of OS-issued commands. Mountain Lion wouldn’t be able to issue the correct commands.
The only way this could work would be for Apple to issue an update to Mountain Lion itself. Generally, it doesn’t do that if a newer OS is already shipping.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden