Memory lane

So I did not get the number right. Not so much because I did not understand the 16 base system, but because apparently I cannot count. Somehow I got 41. I got 32 by the time I came to the spot I wanted (don’t ask me how), then added 8 (or 9).

The +1 is understandable. Had I counted properly I would have come up with 33. I counted my starting point (0x00) as 1,giving me a plus one in my counting thereafter. But I forgot that you do not begin counting from your point of origin (0) , you have not even moved yet. It is only when you walk the full distance, from point A(0) to point B(1) that you can count that length as “1”. The space between A and B= 1, B(1) and C(2)= 2, etc.

Subtle, but your reference point makes all the difference.

Cakes: I had the right idea, but I did not know about the filling up the continuous space bit (or byte? Take your pick, not your pic, no selfies needed.). But it makes complete sense: the memory will shove the code into the first available spot, filling up the gaps where possible.

1 Like

Haha sometimes we can’t count. It happens :stuck_out_tongue:

Privacy & Terms