Paul McNett wrote: > MB Software Solutions General Account wrote: >> Paul McNett wrote: >>> Tracy Pearson wrote: >>>> Well, case matters in some source control systems. That's why I know of >>>> MoveFile(). When a Linux file system gets involved, the same filename with >>>> different cases could be in the same folder, since they are not the same. >>> It isn't the OS that determines whether MyFile.txt or myfile.txt are the >> same file or >>> not, but the filesystem in use. >>> >>> ext3fs, the most common Linux filesystem, does indeed treat those as >> separate files, >>> while ntfs and fat wouldn't. >> >> What's the sense in that, Paul? You folks who are proLinux could >> probably explain it to us Windoze folks. > > As I said, it isn't a Linux thing, it's a 'feature' of certain filesystems. > Just > because I'm a Linux user and advocate and use a case-sensitive filesystem > doesn't > mean I necessarily agree with it. > > I believe it is simply one of those things that is there for historical > reasons. We > are talking about filesystems that have been evolving for 30+ years. Changing > it now > could cause a heap of trouble for existing files. > > It also doesn't really cause as many problems as you appear to assume it > would. The > only time I've had an issue with this is back when I used to use CVS as my > source > control for VFP, and *VFP* had this really wonky behavior where it would > change the > case of certain file extensions, which would throw a wrench in the backend > csv as now > we have two files: the .vct and the .VCT. But I still blame that on VFP, not > on CVS > or Linux, or even the filesystem, as they were just doing what they were > asked to do.
Oh, I forgot to mention the main reason I like case-sensitivity in general: It doesn't let you get sloppy. I look back at my VFP code today, code I was proud of, and I can't believe how inconsistent I was in whitespace and casing. Things like: IF ... ... ... else ... ... endif and calling it m.CustomerName in one place and m.customername in another. Case-sensitivity simply doesn't allow for this unforgivable sloppiness, so the sloppiness doesn't happen in the first place. I think the same argument could be made for files in a filesystem. Being sloppy with naming will result in problems. Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
