Re: Setting up searches in Xcode (Re: [ANN] Xcode + Leopard at WWDCthis year)
Re: Setting up searches in Xcode (Re: [ANN] Xcode + Leopard at WWDCthis year)
- Subject: Re: Setting up searches in Xcode (Re: [ANN] Xcode + Leopard at WWDCthis year)
- From: Steve Checkoway <email@hidden>
- Date: Thu, 20 Jul 2006 16:56:06 -0700
On Jul 20, 2006, at 4:32 PM, Laurence Harris wrote:
On Jul 20, 2006, at 12:31 PM, Chris Espinosa wrote:
Surely if you know enough about /usr/include to want to search it
explicitly, you know the ways to get to it through the standard
Mac OS X user interface that hides Unixisms from end users?
This is an assumption, or at least an expectation, but there's no
logical basis for believing it is always true. Developers have a
wide variety of backgrounds, work habits, and experiences. I never
use paths. To be honest, it would not even occur to me under normal
circumstances to type a path to specify a file because it's just
something I haven't needed to do in over 15 years of using a Mac.
Were I really a path kind of person, I'd probably be using
Windows. ;-)
That's impossible to believe. Do you keep all of your files in the
root directory of your harddrive? In 15 years of using a mac, you've
never had to double click a folder? Have you never #include <sys/
types.h> before? All of these are using paths in a very explicit manner.
What part of using a file path is windows-ish? Every modern (and many
much less modern) operating systems have had file systems that were
not flat.
--
Steve Checkoway
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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