Re: avoid space in path names
Re: avoid space in path names
- Subject: Re: avoid space in path names
- From: Eric Albert <email@hidden>
- Date: Wed, 14 Dec 2005 16:11:44 -0800
On Dec 14, 2005, at 4:00 PM, Justin C. Walker wrote:
On Dec 14, 2005, at 15:54 , Graham J Lee wrote:
On 14/12/05 22:45, Justin C. Walker wrote:
On Dec 14, 2005, at 14:33 , Steve Checkoway wrote:
On Dec 14, 2005, at 1:22 PM, Sean McBride wrote:
On 2005-12-13 17:22, David Fang said:
Don't forget to avoid case-insensitive clashes too!
(Bad experience: CVS checking out a project with x.c and x.C
sources)
Though in this case, there is a compiler warning to help you
at least...
forget its name tho.
What would the compiler be warning about? x.c is a C file. x.C
is a C++ file.
On a case-insensitive file system? I don't know that the
compiler can tell on the name alone.
A filesystem such as HFS+ is case-preserving, so if you called it
x.C it's called x.C so gcc will assume it's a C++ file. You could
also open it as x.c or X.C or X.c but that isn't what it's called,
AFAIK. e.g.:
I don't think the app can tell, really. It will depend on what it
looks for first.
I'm pretty sure realpath(3) will return the correct case, so apps can
differentiate between x.c and x.C that way.
-Eric
_______________________________________________
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