On 5/16/01 1:22 PM, "Eric Deines" <[EMAIL PROTECTED]> wrote:
> First of all, I see there are two different types of builds, Classic and
> Carbon. What is the difference between each? (Yes, I am a Windows
> programmer new to Mac, no laughing....)
Erik,
I see that I answered your question about a problem, but didn't give you the
information you requested. So in answer to your question about the
difference between classic and carbon:
A "Classic" application is one way of describing an application that runs on
the "traditional" MacOS API set.
A "Carbon" application uses a slightly different set of APIs that�s designed
to allow the application to function as a full-fledged citizen both on Mac
OS X and on more "classic" Mac OS Systems (8.x & 9.x), using a library
called "CarbonLib", and including the "Classic" environment on Mac OS X,
which (just to confuse you), allows "classic" applications to run on Mac OS
X even if they haven't been "Carbonized".
So you write a Carbon application now, because you probably want it to run
both on Mac OS X and Mac OS 9.x; old applications, or those that can't
easily be revved to be such, are classic applications.
Now, as an old Math professor used to query, "Isn't that just as clear as
mud?"
-jdb
--
/**********************************
James D. Berry
mailto:[EMAIL PROTECTED]
vox:503.265.1213 fax:503.222.3020
**********************************/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
