Re: [Alephmodular-devel] 0.3 Progress update... ints done

[Br'fin <br...@ma...>]

On Sunday, December 29, 2002, at 10:04  PM, Aaron Davies wrote:

> On Sunday, December 29, 2002, at 07:17  PM, Br'fin wrote:
>
>> OBSOLETE CODE REMOVAL
>>
>> In the code we have, we currently have parts of coded surrounded by  
>> #if 0, #ifdef NEW_AND_BROKEN, #ifdef OBSOLETE, #ifdef CYBERMAXX as  
>> well as code for Classic Mac APIS (Non-carbon) and Valkyrie video  
>> accelerators.
>>
>> Chris suggested dumping all pre-carbon support. I myself am  
>> ambivalent, but I can't support it. I don't have the compilers for  
>> making a PPC MacOS 9 build, nevermind even attempting any kind of 68k  
>> build.
>>
>> If you want or need MacOS 9 support, don't just ask for it, try to  
>> find someone to   get this project building under MacOS 9 and then  
>> ask this project to continue to support it. Now is the best time as I  
>> haven't tried to remove anything yet. So everything should still be  
>> available.
>
> What about making the Carbon build OS 9 compatible? I know of dozens  
> of apps that have "fat carbon" versions that run equally well on OS X  
> and OS 9.

Unfortunately it comes down to the same problem. I, personally, only  
have the ability to compile Mach-O binaries for MacOS X. Project  
Builder doesn't appear to be able to create applications that can run  
as "fat carbon" applications.

If we could find someone to maintain builds for MacOS 9 then we could  
debate with them whether it uses all the classic APIs or uses Carbon  
APIs in all the applicable spots.

Right now it's simply out of my hands. :/

-Jeremy Parsons

--------------------- 
+------------------------------------------------------
Br'fin               |      TIMSter, MU*er, Web Programmer, ... Insane?
The Denim Warrior    |                  You be the judge...
br...@ma...       |
--------------------- 
+------------------------------------------------------