this post was submitted on 06 Sep 2024
614 points (90.4% liked)

linuxmemes

21210 readers
89 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    [email protected]
    [email protected]
    [email protected]
    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 months ago by [email protected] to c/[email protected]
    242 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 9 points 2 months ago (2 children)

    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.

    [–] [email protected] 11 points 2 months ago* (last edited 2 months 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.

    [–] [email protected] 5 points 2 months 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.

    [–] [email protected] 3 points 2 months 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.

    [–] [email protected] 9 points 2 months ago* (last edited 2 months ago)

    My naming convention for C++ is that custom types are capitalized and instances aren't. So I might write User user;.