[info-mcl] Pathname and Unicode in MCL 5.1

[Raffael Cavallaro]

On Oct 3, 2007, at 2:28 PM, Alexander Repenning wrote:

> On Oct 1, 2007, at 3:05 PM, Takehiko Abe wrote:
>
>> MCL had been waiting for the 64-bit Mac OS for the last two years.
>> But it turned out that Leopard will not be full 64-bit system. It is
>> reported that Apple decided not to release full 64-bit Carbon. That
>> was last June.
>>
>> http://www.carbondev.com/site/?page=64-bit+Carbon
>>
>> It means that MCL is completely screwed.
>
> No it does not. Carbon will hang around for a long time. Unless you  
> absolutely need a 64bit Lisp app there will be no real issue  
> compared to NOT having an Intel compiler. If I were Digitool I would  
> this a small priority. Give us a Intel compiler and then, some time  
> later, migrate to Cocoa. No hurry.

 From the page that Keke Abe cites:

"Fundamentally, Apple engineering is focused on Cocoa much more than  
Carbon, and Apple's engineering management made the decision to un- 
support 64-bit Carbon to emphasize that fact."

Sounds like "no hurry" is bad advice since one doesn't know which os  
rev will un-support carbon entirely.

"Much of the Carbon API will still be available in 64-bit. The primary  
parts planned for removal are the UI portions of HIToolbox"

So writing a Carbon (as opposed to Cocoa) *GUI* app means it won't run  
in the future when all Apple os releases will be 64-bit.

You clearly don't speak for Apple when you opine that "carbon will  
hang around for a long time."

N.B. I'm cc-ing some of you since the info-mcl list is losing some of  
my posts.


Raffael Cavallaro, Ph.D.
raffaelcavallaro at mac.com