Re: XCode 3.1.2 ( downloaded from iPhone SDK 9m2621afinal ) Debugger bugged : Won't stop at break points ?
Re: XCode 3.1.2 ( downloaded from iPhone SDK 9m2621afinal ) Debugger bugged : Won't stop at break points ?
- Subject: Re: XCode 3.1.2 ( downloaded from iPhone SDK 9m2621afinal ) Debugger bugged : Won't stop at break points ?
- From: Darcy Brockbank <email@hidden>
- Date: Thu, 12 Mar 2009 11:51:51 -0400
- Organization: Quarrelsome Logick and Divination, Inc.
I have had XCode tell me that something has gone wrong and it needs to
shut down, but unlike VS it will give you the option to struggle on if
you wish and complete your tasks.. Often it will clear itself and recover.
The something going wrong is an exception, and an app that is giving itself
exceptions is an app that is unstable. After one of the frequent exceptions
occurs I always quit and restart. Going past that point is a user-at-risk
situation.
One thing that XCode always seems to do is save your most recent
changes, even if you lock a machine up during a compile / debug
iteration which causes a machine crash.
This is a misfeature in my opinion. I know I will catch hell for this
kind of
statement, but the thing is that the person responsible for it has
considered
that the app is able to catch signals and exceptions, so they have a chance
to do some cleanup and save open files. So who needs to keep a backup
file? When will *this* ever happen that I won't be able to clean up?
And then blammo the situation happens that they didn't foresee and the
user is screwed. There is a major problem with the concept of doing file
operations once the application has become unstable... if things are so
unreliable that the ship is sinking, this is not the time to perform
critical
operations.
Keeping a rolling backup of files open and edited means that while things
are stable you can do critical operations and rely on the results. Not while
the boat is half under water and you have no guarantee that you're able
to complete the task... if you can complete it at all.
XCode is not perfect, but pound for pound it's the most reliable
development environment I have worked on in 30 years of coding.
I fail to understand how this comment jibes with the comment above about
Xcode dying and saving files on the way out the door. A reliable
and stable development environment doesn't crash.
I try to stick to emacs in general because I don't face any of these issues.
If I want to clean a project I can do a make clean and simple, standard
tools work. Xcode can't do it... file a bug report. Find out it's a "known
issue" and maybe one day will be fixed. To me this is one of the most
basic and simple requirements of a development tool... it does not jibe
with it being "the most reliable" development environment someone
has ever encountered. It's a known issue, so guess it can't be one of
these things that people can blame on my setup or a lack of honesty.
I have to wonder if there is something up with your setup, or perhaps
even your HD if you are truly experiencing the kind of problems you say.
Oh look, there it is.
- darcy
_______________________________________________
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