|
|
|
|
|
by coldpie
359 days ago
|
|
I had a professor tell the class, in response to a student's question, that the "0x" in the "0x1" memory address on the slide meant "a bunch of stuff that doesn't matter," like the "x" was a stand-in for some unimportant portion of the memory address that had been elided. I stopped attending that class. That professor was not significantly below the average at my school (University of Minnesota, late 2000s). Blowing 4 years and a bunch of money at university getting a computer science degree is one of the biggest regrets of my life. Luckily I already had a software job during my 1st year, so those years weren't totally wasted. |
|
Like, when I was in school we saw a lot of pointers and yeah, 99% of the time the actual memory address was more or less useless. What mattered is it was a pointer and it was over there, and it was part of some struct or whatever. The actual numbers of it's address didn't matter much and would actually change between runs.
I don't know, I see people miss the forest for the trees with this stuff constantly. They don't understand that absolute veracity and education are pretty much orthogonal. As in, your professor isn't trying to just say correct things, they're trying to teach you. And, actually, saying too many correct things makes it harder to teach you.