[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: Tom Lord
Subject: Re: [Gnu-arch-users] Re: tla1.2 on cygwin
Date: Wed, 10 Mar 2004 01:26:58 -0800 (PST)

    > From: Dustin Sallings <address@hidden>

    > 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:

    > >         x.h
    > >         X.h

    > > 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 
    > >> 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.

With the #include and tar examples, you have tools that are case
sensitive and that are made friendly for broken environments like
those that you are using by virtue of people's choices of which among
the permissable names of files to use.

Why should arch be any different?


reply via email to

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