[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] Re: tla1.2 on cygwin

From: Dustin Sallings
Subject: Re: [Gnu-arch-users] Re: tla1.2 on cygwin
Date: Wed, 10 Mar 2004 00:56:17 -0800

On Mar 10, 2004, at 1:12, Tom Lord wrote:

Suppose that someone wrote a C library you'd really like to use but it
has header files:


would you say that the C language should be changed?

No, I'd say the developer made a poor choice in naming conventions. I've never seen this happen, but I'd definitely file a bug to get it fixed. It would at the very least be terribly confusing.

How do you cope with #include, btw?   And, what does tar do?

        I'm not sure what you mean by #include.  I haven't seen any problems
related to that.  Tar works just fine.  The filesystem preserves case
just fine, it just ignores it when accessing files or directories.

Will a tar file containing "./x.h" and "./X.h" work "just fine" on
your case insensitive system?

Again, I've rarely seen anything like this. When I have seen it, it's with confusing filenames anyway.

Your examples are quite contrived here, and I don't understand the relevance.

SPY                      My girlfriend asked me which one I like better.
pub  1024/3CAE01D5 1994/11/03 Dustin Sallings <address@hidden>
|    Key fingerprint =  87 02 57 08 02 D0 DA D6  C8 0F 3E 65 51 98 D8 BE
L_______________________ I hope the answer won't upset her. ____________

reply via email to

[Prev in Thread] Current Thread [Next in Thread]