this post was submitted on 06 Sep 2024
615 points (90.6% liked)

linuxmemes

20880 readers
5 users here now

I use Arch btw


Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 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.

[–] [email protected] 2 points 2 months ago

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

[–] [email protected] 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.