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

linuxmemes

21311 readers
401 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!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 1 year ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    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 LuuTuyen@lemmy.world to c/linuxmemes@lemmy.world
    242 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] wizardbeard@lemmy.dbzer0.com 3 points 2 months ago* (last edited 2 months ago) (2 children)

    PowerShell variable names and function names are not case sensitive.

    I understand the conventions of using capitalization of those names having specific meanings in regards to things like constants, but the overwhelming majority of us all use IDEs now with autocomplete.

    Personally, I prefer to use prefixes anyway to denote that info. Works better with segmenting stuff for autocomplete, and has less overhead of deriving non-explicit meaning from stuff like formatting or capitalization choices.

    On top of that, you really shouldn't be using variables with the same name but different capitalization in the same sections of code anyway. "Did I mean to use $AGE, $Age, or $age here?" God forbid someone come through to enforce standards or something and fuck that all up.

    [–] palordrolap@fedia.io 2 points 2 months ago

    But should $Age return the same value as $age if used in its place by mistake?

    [–] Serinus@lemmy.world 0 points 2 months ago* (last edited 2 months ago)

    you really shouldn't be using variables with the same name but different capitalization in the same sections of code anyway.

    It's a standard convention. Notice step #3 here: https://scottlilly.com/learn-c-by-building-a-simple-rpg-index/lesson-08-1-setting-properties-with-a-class-constructor/

    Edit: Step #4 is a different standard convention that also applies here.