Re(3): C'mon Apple! DECIDE!
Re(3): C'mon Apple! DECIDE!
- Subject: Re(3): C'mon Apple! DECIDE!
- From: Jens Bauer <email@hidden>
- Date: Sun, 28 Apr 2002 00:01:27 +0200
Hi Chris,
On Sat, 27 Apr, 2002, Chris Hanson <email@hidden> wrote:
>
At 4:57 PM +0200 4/27/02, Jens Bauer wrote:
>
>-I tried using Project Builder for a Carbon App. but as I found out it
>
>was time consuming to switch to Mac OS 9 all the time for testing it, I
>
>decided to pick CodeWarrior for this task.
>
>
It was probably more difficult than just switching to Mac OS 9 to
>
test it, since gcc doesn't generate PEF binaries and Mach-O binaries
>
won't run on Mac OS 9...
I think you're right. I'm not sure if I ever got a working application
for Mac OS 9;
then it was just easier to keep CW, as I knew how to do these things.
>
>I've never attempted to use CW for building a real Cocoa application,
>
>probably because I don't have 7.x.
>
>
CodeWarrior Pro 7 has preliminary support, but Metrowerks hasn't
>
switched CodeWarrior to use FSRefs instead of FSSpecs yet. Which
>
means there's no long filename support within CodeWarrior.
This is OK with me.
>
Which
>
means to do Cocoa development with CodeWarrior, you have to change
>
the names of a couple header files and edit references to them in the
>
headers.
Wouldn't it be possible to create aliases (symbolic links) for these
header files ? :)
>
There's also no good support for nibs, property lists, localized
>
files, etc. in CodeWarrior yet, which makes it annoying for Carbon
>
Mach-O development. It's too bad, because it has a better compiler
>
and I think it's a far nicer coding environment than Project Builder.
I won't blame anybody for having the best compiler (except for MPW); CW
has a few advantages over gcc, but gcc definately has advantages over CW
as well.
It's mostly a matter of taste I think.
If you want to find bugs in your code, try compiling with both compilers,
and look at the warnings.
Get rid of all warnings, and your code will probably get more stable.
-But also, you should test more under Mac OS X, because the memory
protection tells you immediately if you got a bad pointer. ;)
>
I'm hoping CodeWarrior Pro 8 has at least the long filename support,
>
if not the other elements necessary to do Mach-O and Cocoa
>
development more easily.
I think those guys will think about this; be sure they know that this
issue is serious. ;)
Love,
Jens
--
Jens Bauer, Faster Software.
-Let's make the World better, shall we ?
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.