2 ms·
Right, thanks. It's a form of pointer virtualization basically. To me personally this falls into the same domain as the "if (0 == x)" notation - it protects ag
by eps 13y ago
Right, thanks. It's a form of pointer virtualization basically.
To me personally this falls into the same domain as the "if (0 == x)" notation - it protects against a very specific type of rake that its proponents just happened to have stepped on at some point eariler on. I've been programming in C for over 20 years now and I have never had the issue you are describing. I understand it's possible, but then there's plenty more ways to shoot oneself with C pointers.
- hal9000xp 13y agoI worked (and I'm still working) on several big projects which wrote by different people, and by different companies, and at different time. I repeatedly noticed the same pattern where there is a limited linear array of contexts. For example, linear array of user contexts. In this case, it's easy to create a new object in that array just after previous object was destroyed at the same slot (we called an index number in the user context array - slot).