From: Earnie B. <ea...@us...> - 2007-09-29 18:18:48
|
Quoting Keith Marshall <kei...@us...>: > On Sat, 2007-09-29 at 08:45 -0400, Earnie Boyd wrote: >> Fact: I want tools that pay attention to the case of its arguments and >> commands even in a case insensitive file system. Argument to this >> fact is futile. > > IMO, your logic is flawed. The file system *is* case insensitive; any > tool which believes that it can change this fundamental reality, by > *pretending* that it is otherwise, is broken. This isn't an argument > against the fact. That you *want* the broken behaviour is your choice; > you are welcome to collect as many broken pieces as you wish. > The Makefile creator [TMC] presents the tool with commands that look for files on the disk. TMC expects that the file names in a case preserving, case insensitive file system to be found exactly as stated. If TMC wants to search for files regardless of case the TMC can create target and dependency patterns that search in case insensitive ways. >> Fact: You want tools that do not pay attention to the case of its >> arguments and commands especially in a case insensitive file system. >> Argument to this fact is futile. > > No, this is not what I want, at all. What I want is tools which DTRT, > whether the file system is case sensitive or not. I recognise that some > file systems are case sensitive and some are not; I adapt my working > practices to accommodate both. MSYS make-3.79.1 has never completely > done TRT, simply because it has refused to understand that it has no > choice but to recognise that it has got to work with a case insensitive > file system; Chuck's build of make-3.81 has corrected that deficiency. > So now with case insensitive targets and dependencies enforced regardless, TMC has no opportunity to make certain that his files will remain case preserved as he desires. But you have your desire to take makefiles written for DOS 8.3 and have the work out of the box. >> Given these two facts we must agree to compromise. > > Sure. Life is all about compromise; I don't have any problem here. > >> The best compromise I've seen offered in this thread was to include a >> runtime switch or environment setting to control its operation. > > The best compromise is simply to provide two separate builds, one > offering each behaviour, and you choose whichever you prefer. If you That works too. >> I have strong opinions that tools that allow the user to misuse the >> case insensitive file system fact are broken. > > Yet, you argue the case for providing the broken tool, in preference to > the sane! > SSY >> Therefore the tools so far have considered foo != FOO even though the >> file system thinks so. > > The file system, by definition, *must* be correct! The tools which > pretend otherwise are broken. > SSY >> I can agree to the above compromise however because I can still >> therefore enforce my opinion while at the same time you can enforce >> your opinion. > > It isn't about enforcement; it is about choice. I can happily agree to > this compromise because it allows you to have the behaviour you prefer, > no matter how insane I consider your choice, while I too can have what I > consider correct, even if you think I am crazy. > I don't think you're crazy; I think you have strong opinions that are different from mine. We are both correct and it comes down to which version is correct for the moment. Earnie P.S.: SSY == So say you. |