Re: double compile messages
Re: double compile messages
- Subject: Re: double compile messages
- From: Fritz Anderson <email@hidden>
- Date: Sun, 4 Nov 2007 14:03:22 -0600
On 4 Nov 2007, at 1:00 PM, Bill Bumgarner wrote:
Not really -- for a new project there are typically only a handful
of source files.
Defaulting to Release doesn't add *that* much time to compilation
(especially not for Cocoa apps -- ObjC compiles fast), doesn't
impact debugging *that* badly while the code is simple, and means
that the app is reasonably sized and "just works" when drag-n-
dropped somewhere else.
What you are saying is that it _is_ worse than the alternative
(slower, harder to debug), but the problem won't be noticed until it
has become severe, and then is easily corrected.
After all, what's a few non-consecutive debugging steps and missing
variables between friends? And nobody is ever confused by the double-
compilation... oops -- see the title of this thread.
"For a new project there are typically" more than a handful of bugs to
track down.
Defaulting to Debug has surprised many a developer when their app
didn't work anywhere but the products directory
Does this happen now that ZeroLink is no longer possible? <Drags a
recent Debug build to the Desktop... seems to run just fine.>
OR was considerably larger than expected.
And here is my turn to say this is easily remedied by releasing only
under the configuration named... you know... "Release." Who shares out
the product of a BRAND NEW PROJECT? And do they not run it under a
debugger first?
By the time someone has any complexity to their project, they have
probably had to adjust something build related and figured out that
there is a "release" vs. "debug" modality available.
"By the time someone has any complexity to their project" is surely
the time when one finally begins to be concerned with product size,
yes? And not before? So they should be using "Debug" while they are
debugging?
This has a lot of the flavor of "my manager is forcing it because it
fits the way _he_ works."
Defaulting new projects away from debugging really, REALLY annoys me.
If I were writing a book about this, I'd have to add extra
instructions for the reader to switch back. Just at the point, early
in the experience, where he needs the simplicity. If you have to tell
everybody to switch away from the default, it's a bad default.
— F
_______________________________________________
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