• gramie@lemmy.ca
    link
    fedilink
    arrow-up
    7
    ·
    10 months ago

    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.

    • ArbitraryValue@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      5
      ·
      edit-2
      10 months ago

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

    • Serinus@lemmy.world
      link
      fedilink
      arrow-up
      6
      arrow-down
      1
      ·
      edit-2
      10 months ago

      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.

      • gramie@lemmy.ca
        link
        fedilink
        arrow-up
        3
        ·
        10 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.