It’s 0-255 when you’re indexing like that. 11111111b = 255.
It’s 0-255 when you’re indexing like that. 11111111b = 255.
I have a question for my Canadian sisters, brothers, and others.
How much of this shit is actually organic to Canadian culture, and how much creeps in because the assholes there see what the assholes in the US are exploiting and decide to give it a try there?
Perchance programming with pointers has plunged as a percentage of programmers.
But thank you. I was hoping someone would notice that.
When you’ve eaten more than 50% of the hamburger, do you claim to have eaten one, or do you claim zero? Are you useing standard founding or are you using floor()?
This.
One of the reasons indexing starts at zero is because back when we used to use pointers and memory addresses, the first byte(s) of an array were at the address where the array was stored. Let’s say it is at 1234. If it was an array of bytes, the first data element was at 1234, or 1234 + 0. The second element would be at 1235, or 1234 + 1. So the first element is at location 0 and the second at location 1, where the index is actually just an offset from the base address. There may be other/better reasons, but that’s what I was taught back in the 90s.
Counting always starts at 1 (if we’re only using integers). You don’t eat a hamburger and say you ate zero hamburgers.
This isn’t the kind of thing you forget like missing a birthday. It’s a major directive from one institution to another, and it’s entirely possible it’s just being slow walked. These are all handled by working groups who may not be motivated to get it done.
I’m not sure if the situation might change if Trump gets re-elected.