Just one more thing...

Michel Fortin michel.fortin at michelf.com
Fri Feb 27 20:06:46 PST 2009


On 2009-02-27 16:37:13 -0500, Jacob Carlborg <doob at me.com> said:

> Nick Sabalausky wrote:
>> Ordinarily, I detest the idea of pulling support for anything as recent 
>> as just a few years old. But Apple themselves has a habit of ignoring 
>> users of anything except the latest version, so I would think that mac 
>> users would be accustomed to the old routine of their OS becoming a 
>> deadend the moment a new version comes out. So, in this case, I would 
>> think that there may actually be justification in sticking with 10.5+, 
>> if you were to so choose.
> 
> I would not completely agree with you on this. When you install the 
> developer tools on osx 10.5 it installs SDKs for 10.5 and 10.4 as 
> default, but you can also choose to install support for older versions. 
> I'm not sure if it's only for 10.3 or also for 10.2.

On Mac OS X 10.5, you can compile for 10.3 using Xcode 3, and 10.2 
using Xcode 2.5 (Xcode 2.5 for Leopard is a free download). Of course, 
10.2 and 10.3 being PowerPC-only, there's no point trying to compile 
DMD for them.


> Then what about Carbon, Classic (don't know if this is still available) 
> and Rosetta, environments and libraries to support older applications.

Classic is no longer supported on Leopard, and was never supported on 
Intel Macs.

Apple keeps old application running on newer versions of the operating 
system -- I can run apps I made for 10.0 on Leopard -- but their 
developer tools are limited to a few operating systems back.


-- 
Michel Fortin
michel.fortin at michelf.com
http://michelf.com/



More information about the Digitalmars-d-announce mailing list