Re: iCode development tool
Re: iCode development tool
- Subject: Re: iCode development tool
- From: Jerry <email@hidden>
- Date: Wed, 4 Jan 2006 09:07:23 +0000
At 1:02 PM -0700 1/3/06, Nick Nallick wrote:
On Jan 3, 2006, at 11:54 AM, Mark Munz (DevList) wrote:
The reality is that PB/Xcode are basically GUI wrapper around
command-line tools. I see Xcode as trying to be the next MPW
environment (all things to all people).
...
Another one is include paths. The fact is that the build settings
don't give a real GUI to the options that are available.
Personally I see the include path issue as the best example of
Xcode failing to be an "integrated" development environment (IDE).
The editor and the compiler should have a common search path
mechanism so they always find the same source file. Otherwise you
run the risk of errors where you're editing one file but compiling
another.
This very thing caused me to be told off in public by Larry - the IDE
had opened a different file from the one being compiled with and I
asked a question on the Carbon-dev mailing list which then made me
look foolish, so I take this problem very seriously :-(
Jerry
_______________________________________________
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