• 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: Upon break, debugger not showing correct line in source
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Upon break, debugger not showing correct line in source


  • Subject: Re: Upon break, debugger not showing correct line in source
  • From: Wade Williams <email@hidden>
  • Date: Mon, 15 Feb 2010 17:42:12 -0600


On Feb 14, 2010, at 1:16 PM, Fritz Anderson wrote:

On 14 Feb 2010, at 12:44 PM, Julian Gómez wrote:

And just what is the competition to Xcode?

This restriction strikes me as another way to waste developers' time.

The person you replied to said "YOUR competitor," by which I understand him to mean a competitor of you, Julian Gómez, the person he was addressing.


To restate: Suppose developer JG files a bug saying he wants to do X, using iPhone OS feature Y, and provides source code revealing his design for X. Suppose JG's work and product plans are how he makes money for food. Other people want to make money, too. If you got your wish, and the bug database was open to those other people, they would be able to add X to their products, and probably get them to market before JG, because they have his design and his warning that Y isn't the way to do it.

Or: Suppose Apple responds that feature Y will be enhanced, or replaced, in a future version of iPhone OS. Apple has competitors too. Apple does not love its competitors.

Do you see how others might not be as generous as you? And that the privacy of the database may not have been devised just to annoy you?

And please don't suggest that Apple should examine each bug, case-by- case, and publish the "harmless" ones. Each would take a lawyer at least a day to resolve, and if a bug develops so it would reveal Apple or filer secrets, hiding the bug would itself be a disclosure. Besides, JG knows better than Apple what his secrets are. If he wants to publish his bugs, he can file in parallel with Open Radar <http://openradar.appspot.com/ >.


There are ways you can provide valuable information to customers/ developers without giving away the store.


For example, Cisco customers can search for open bugs. If the bug is not theirs, they only get to read the release note, which describes the bug, the versions it affects, workarounds, etc. If it's the customer's own bugs they get to see the complete case notes.

Wade _______________________________________________
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: Upon break, debugger not showing correct line in source (From: Matt Neuburg <email@hidden>)
 >Re: Upon break, debugger not showing correct line in source (From: Julian Gómez <email@hidden>)
 >Re: Upon break, debugger not showing correct line in source (From: Douglas Norton <email@hidden>)
 >Re: Upon break, debugger not showing correct line in source (From: Julian Gómez <email@hidden>)
 >Re: Upon break, debugger not showing correct line in source (From: Fritz Anderson <email@hidden>)

  • Prev by Date: Re: Upon break, debugger not showing correct line in source
  • Next by Date: Re: Xcode performance issues over time
  • Previous by thread: Re: Upon break, debugger not showing correct line in source
  • Next by thread: Re: Upon break, debugger not showing correct line in source
  • Index(es):
    • Date
    • Thread