614
Remember: GNU/Linux and other UNIX systems can make files that are case-sensitive, Windows can't make files that are case-sensitive (lemmy.world)
submitted 2 years ago by to c/linuxmemes@lemmy.world
239 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 11 points 2 years ago* (last edited 2 years ago) (2 children)

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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 5 points 2 years ago

    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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 3 points 2 years ago

    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.

  • permalink
  • fedilink
  • source
  • parent