Re: CodeWarrior vs Xcode issues
Re: CodeWarrior vs Xcode issues
- Subject: Re: CodeWarrior vs Xcode issues
- From: Markus Hitter <email@hidden>
- Date: Tue, 7 Jun 2005 21:39:13 +0200
Am 07.06.2005 um 18:22 schrieb Andy O'Meara:
I'm not convinced Apple is looking out for devs who aren't gcc
gurus (but need a also demand a lot from their compiler).
You rarely have to bother which compiler works in the background.
My small company develops performance graphics stuff for win32 as
well as mac
os x, so it's been very effective over the years to use codewarrior to
target CFM carbon, mach-o, and win32.
Are you targetting Classic Mac OS or are you bothering about
performance? If you do the latter, you might want to have a look for
IBM's xlc which is known to produce quite fast executables.
I got to keep all our cross-platform code in a DLL and .bundle
project, and
that was damn nice
Now you have a directory of code files with two project files inside
it. A Xcode one and some Windows one. Using a file with one IDE
doesn't stop you to use it in another one as well.
- Codewarrior has great warning control and suppression support.
Why do you switch warnings on if you suppress them afterwards?
To control warnings in Xcode, go to the build settings panel(s) and
play with the checkboxes. Selecting a line in the table there puts
you the related part of the man page at the bottom. What else would
you expect?
I realize the gcc has many warning-related features, but I don't
have the
resources/interst/patience to become a gcc options and flags guru
(when
there's two other compilers that I have to manage as well).
So, switch all warnings off and gcc will allow you to write sloppy
code without complaining with a single line of output.
Currently, my cross-platform code base
compiles like a champ, but there's certain warnings that come up
that are a
horrible distraction from real warnings that I may need to know about
You are right. gcc doesn't have a how-does-my-developer-feel-about-
this-warning sensor built in. It doesn't get tired to point out every
possible occurence of mistyped code. If you don't want to see them,
switch them off or fix your code. It's not that hard to switch a lot
of warnings on but to have compliations free of warnings anyways, btw.
1) Syntax/editor features. Again, Apple beats the
cocoa-and-xcode-is-superior drum, but how impressed can I be when
Apple
doesn't seem to have matched (or surpassed) codewarrior's editor in
full?
1) As you note later, you're coding in C++ which isn't adressed by
this drum. Cocoa is Objective-C.
2) Sounds like you consider the codewarrior editor to be the state of
the art editor others have to measure with. So, why don't you
continue to use it? Xcode supports external editors.
3) Instead of investing time with improving the code editor, Apple
focusses on making it more obsolete. See Key Value Coding, see
Bindings, see Core Data, see ...
Hope that helps,
Markus
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden