Remember: GNU/Linux and other UNIX systems can make files that are case-sensitive, Windows can't make files that are case-sensitive
Remember: GNU/Linux and other UNIX systems can make files that are case-sensitive, Windows can't make files that are case-sensitive
You're viewing a single thread.
It's neat that Linux has the ability to do this, but I honestly can't think of a good usecase for this. I think this is more confusing than it is useful
Git likes to have a word with you.
Command 'Git' not found
Beautiful
Huh, what makes this a use case in favor of case sensitive file names? How does git use this feature?
Create multiple branches that only differ in cases from a Unix OS so it breaks git for Windows users in the same project.
We had a repo with some really weird (filename) case issues on Mac also. I could only fix it on my home Linux machine, by deleting all the affected files, committing that, then restoring them with all lowercase names. Only time I've dealt with that in 20 years but it can happen!
I feel the same way about programming languages. There is no way that "User" and "user" should refer to different variables. How many times has that screwed people up, especially in a weekly typed language?
One of the many things that I feel modern versions of Pascal got right.
Nope. Completely different.
Case is often used to distinguish scope. Lowercase is local while uppercase is public. "Name = name" is a pretty standard convention, especially in constructors.
There is a ubiquitous use case in programming. There is not in the file system.
My point is not about how case is meant to be used my point is that it is very easy to make a mistake that is difficult to spot. I think it makes a lot more sense to the case insensitive, and force different names to be used.
This is the first time I've seen uppercase denoting scope. Usually it is done with a "_" or "__" prefix.
Casing styles usually mean different identifier types.
snake_case or pascalCase for functions and variables, CamelCase for types, UPPER_SNAKE_CASE for constants, and so on.
If we want to apply this to file systems, you could argue something like: CamelCase for directories, snake_case for files, pascalCase for symlinks, UPPER_SNAKE_CASE for hidden files.
My naming convention for C++ is that custom types are capitalized and instances aren't. So I might write
User user;.
It's quite useful for stuff like PROGRAM and Program in the same directory where PROGRAM is the program itself and Program is some unrelated files about the program. Bad example, but the case stands.
So what you're telling me is that it's useful when the software you use is made by absolute idiots?
It's not about software. Program, PROGRAM were just placeholders for content. I know you can think more abstract and argue in better faith than this.
Replace 'software' by w/et placeholder thing
I think if you can write them in two different ways it should consider them two different things