• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Why can't I Run > Fix?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why can't I Run > Fix?


  • Subject: Re: Why can't I Run > Fix?
  • From: "Paul Sanders" <email@hidden>
  • Date: Tue, 16 Mar 2010 17:56:24 -0000


Chris Espinosa said:
>> The feature has not been removed, but its usefulness is ebbing over time.

Paul Sanders said:
> Oh no it isn't.  I also develop for Windows, where Fix and Continue works as it should, and it is an enormous time saver.

Sorry, that was a rather bald statement, wasn't it?  Let me try and explain.  Debugging is often a matter of context.  Depending on the complexity of the program and the nature of the bug, it can often take a while to get the program to the point of failure.  The ability to fix the bug *there and then*, and the ability to text that fix (and maybe fix it again, if you got it wrong) can be hugely productive.  It also avoids losing concentration while waiting the the build to complete and then getting the program back to the point of failure.  But I don't think I can sell this to someone who hasn't tried it.  Only when you actually use it in anger do you come to appreciate what a great time saver it is.

>> The feature has not been removed
 
When I filed a bug about Fix 'n Continue being broken (7505431 ), I was told that it is no longer supported and the bug was closed.

I've said before on this list that the debugging facilities in Xcode fall well short of what I'm used to.  An expressions window that (a) works properly - it doesn't reflect values that have changed on my setup - and (b) can be 'docked' as a pane in the source editor (rather than floating freely on the desktop) is the other major gripe.  Debugging at the assembler level is also painful and the debugger UI is sometimes rather flakey, although I have learned to live with that, most of the time.  My own opinion, based on developing on both the Mac and Windows, is that improvments to the debugger would boost the productivity of the average Mac programmer a great deal.  My work is cross-platform, and I do as much development and debugging as I can on Windows before taking it across to the Mac.  What does that tell you?  And it's not just a question of what I'm used to.  I have been working on the Mac for over a year and the debugging environment just doesn't compare.  Which is a shame as Xcode is otherwise very nice and the debugger rather lets it down.

Paul Sanders.
 
 _______________________________________________
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

References: 
 >Re: Why can't I Run > Fix? (From: Antonio Nunes <email@hidden>)
 >Re: Why can't I Run > Fix? (From: Chris Espinosa <email@hidden>)
 >Re: Why can't I Run > Fix? (From: Antonio Nunes <email@hidden>)
 >Re: Why can't I Run > Fix? (From: "Paul Sanders" <email@hidden>)

  • Prev by Date: Re: Why can't I Run > Fix?
  • Next by Date: XCode, libs and SNMP
  • Previous by thread: Re: Why can't I Run > Fix?
  • Next by thread: Re: Why can't I Run > Fix?
  • Index(es):
    • Date
    • Thread