On 9 Jun 2003 at 22:35, Philip M. Aker wrote: > Adaption of the old MacOS to a pre-emptive multitasking system is > embodied in the Carbon layer. Carbon supports ~90% of the the old > toolbox APIs (including the event loop in question). So you see, the > Macintosh _concept_ gains only about 10% in OS X. Where OS X really > shines is in the area of blending MacOS, Cocoa (NeXT), and unix. For > instance a substantial portion of Cocoa is now interfaced/integrated > with AppleEvents and it's possible to make unix calls with our > AppleEvent-based scripting language (AppleScript) and vice versa. > Multitasking simply isn't an issue on the Mac. Get the point? > Multitasking is only an issue for Windows developers.
And another thing: since the advent of Win32 and Windows OS's that could pre-emptively multi-task, programmers of 32-bit Windows programers have *not* had to worry about multi-tasking, as once you're writing a Win32 program, all multi-tasking and memory management is handled by the OS. So, it's patently false to make the claim that Mac developers need not worry about multi-tasking but Windows programmers do. It's precisely the opposite -- non-Carbon/Cocoas programmers have to program their own cooperative multi-tasking. Since about 1995, Windows programmers have not needed to give it a thought, unless they were writing programs to run on Win3.x. So, your statement is pretty much incorrect for any interpretation you'd want to give it. Now I'm *really* done. -- David W. Fenton http://www.bway.net/~dfenton David Fenton Associates http://www.bway.net/~dfassoc _______________________________________________ Finale mailing list [EMAIL PROTECTED] http://mail.shsu.edu/mailman/listinfo/finale
