• 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: Does not execute on launch
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Does not execute on launch


  • Subject: Re: Does not execute on launch
  • From: Gwynne <email@hidden>
  • Date: Thu, 20 May 2004 23:41:33 -0400

On May 20, 2004, at 9:28 PM, John Stiles wrote:
Should be in FAQ, this has already bitten the bottom of nearly each OSX
programmer (myself included) ;)

The Zero Link works locally only. To be able to run the app on another
machine, build it using the deployment style (not development).
It seems that it would alleviate a lot of newbie problems if ZeroLink were disabled by default.
I've thought that a couple of times, but then it strikes me that newbies need to learn to ship deployment builds and not debug builds, and this teaches them very quickly :) The REAL problem is that the Finder is supremely unhelpful about letting you know when ZeroLink has bitten you. In an ideal world, it would not only display an error, but the error would specifically mention ZeroLink and something about development versus deployment builds.

Start rant.
Personally, I make a point of turning off both Fix & Continue and ZeroLink as the very first things I do when creating a new project; I find both of them untrustworthy and distracting. The next thing I do is turn on a whole pile of warning flags that really ought to be on by default. Unused values, unused functions, shadowed declarations, missing initializer braces, no Pascal strings, printf() format string checking, switch statement checking, sign comparison... with the exception of Pascal strings and shadowed decls, not one of these warnings has EVER made my life anything but significantly easier. The basic template projects that come with Xcode are very lacking, especially with rememberance to the thread a few weeks back about const qualifier mismatches in the call to NSApplicationMain(). One of these days I'll probably get around to replacing the templates; the only reason I haven't already is I don't create new projects all that often. Regardless, not everyone knows how to replace templates, and newbies are getting bitten over and over by such basic things as these. *goes to file a bug*.
End rant :).

-- Gwynne, key to the Code that runs us all
Formerly known as Sailor Quasar.
Email: email@hidden
Web: http://musicimage.plasticchicken.com/
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.


References: 
 >Does not execute on launch (From: Kodex <email@hidden>)
 >Re: Does not execute on launch (From: Ondra Cada <email@hidden>)
 >Re: Does not execute on launch (From: Shaun Wexler <email@hidden>)
 >Re: Does not execute on launch (From: John Stiles <email@hidden>)

  • Prev by Date: Re: NSMakePoint and such - what about memory allocation?
  • Next by Date: Re: Avoiding == and = mixup in if statements
  • Previous by thread: Re: Does not execute on launch
  • Next by thread: Re: Does not execute on launch
  • Index(es):
    • Date
    • Thread