From: Earnie B. <ea...@us...> - 2008-05-02 02:58:45
|
Quoting Keith Marshall <kei...@us...>: > On Wednesday 30 April 2008 21:31, Keith Marshall wrote: >> I can give you 7.3787e+19 reasons >> why your proposed solution is ineffective > > Correction; in haste, I miscalculated. The reality is even worse; > csmake would require 1.021456e+27 distinct rules, to replace just _one_ > simple pattern rule of the form: > > %.TXT: %.APP ; dostool $< > Wouldn't just one do? %.TXT: %.app ; dostool $< Well, unless you want to really support such possible nonsense as myfile.App and myfile.APp and myfile.ApP, etc. > where `dostool is a legacy MS-DOS tool to generate *.TXT files, (always > named in upper case, because that's what MS-DOS tools do), from *.APP > source files, where the case of the source file name is unpredictable, > and assuming only [-A-Z_a-z0-9] are allowed in the source file name. > Simple, if it's legacy code then the file names on the file system must match the legacy system names, even in case. Case sensitive patterns on windows file systems is a must, the file system may actually support case sensitivity but even those that don't support case preservation. The real issue seems to be that the files from the legacy system could be named with lowercase because it is natural even though it should not be. Again if you're supporting a legacy system then the files must be named even in case as the legacy system expects it and not as the new system might make the case. Earnie |