• PowerCrazy@lemmy.ml
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 hour ago

    I “understood” on a basic level what pointers were when i was first learning programing as a 12-13year old. But I never understood HOW to use them, or manipulate them, or what functions you use to interact with them, or how to examine them, or how to declare them, etc etc. And since I was young I never got the opportunity to take an actual programming class that taught any of that throughout high school. By the time I got to college I went with Electrical Engineering instead of computer science and so my journey with pointers ended.

    Now I do python and never have to think about pointers.

  • TimeSquirrel@kbin.melroy.org
    link
    fedilink
    arrow-up
    10
    ·
    3 hours ago

    Lemme tell you something, DO NOT learn BASIC as your first language. As a hobbyist, I avoided C/C++ for 25 years because I just didn’t get pointers and memory manipulation, and messed around with other languages like JS and PHP instead (also BASIC’s GOTO and GOSUB kinda ruined me as a programmer for a few years). But once it finally clicked a couple years ago, I now want to write EVERYTHING in C/C++.

    I think plain C at least should be everybody’s first language. It literally reprograms your brain to think exactly like how a computer internally functions. I never got that with other languages, because they were so far removed from the actual machine.

    Edit: also, after learning some of it, it’s pretty neat when you do stuff like look at parts of the Linux kernel source code and think “wow, I know what’s actually happening here now!”.

    • ☆ Yσɠƚԋσʂ ☆@lemmy.mlOP
      link
      fedilink
      arrow-up
      3
      ·
      2 hours ago

      I actually think that everybody should learn a functional language like Scheme first because it teaches you to think about state explicitly. It’s very easy for somebody who learned a functional language to pick up an imperative one, but it’s very hard for people to go the other way around.

  • SelfProgrammed@lemmy.today
    link
    fedilink
    English
    arrow-up
    25
    ·
    5 hours ago

    Here’s a secret I wish someone told me in high school: literally everything is pass by value, it’s just that sometimes the value is an address. It demystified pointers for me.

    • ddplf@szmer.info
      link
      fedilink
      arrow-up
      6
      arrow-down
      1
      ·
      edit-2
      4 hours ago

      It’s the opposite, everything is passed by reference but primitives are also addresses and therefore passed by value

      You can’t pass objects or functions as value

      • Ephera@lemmy.ml
        link
        fedilink
        English
        arrow-up
        2
        ·
        3 hours ago

        I mean, Rust has the additional thing that a reference is a pointer + a borrow, so it’s not quite as similar to a pass-by-value.

        And as for the dereference operator, occasionally you can use it to turn a reference into an owned value, often by making a copy of the value (but in that case, you can usually also use .to_owned()).

        A case where I don’t think there’s an alternative to the dereference operator, is if you’ve got a mutable reference and you want to replace the value that’s underneath: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=04621490e1d0fd6fe1af7f2e843547fb
        At the very least, if you remove the asterisk, the compiler will tell you very precisely that you need to add it back.

    • underisk@lemmy.ml
      link
      fedilink
      arrow-up
      2
      ·
      4 hours ago

      They taught you about pointers in high school? The only course available to me that even touched on programming just covered how to use C to do conditionals, read keyboard input, and print text to a terminal. The bulk of the course was learning MS Office.