4 ms·
I agree with him. in many practical applications with well design class hierarchies it just really isn't much of an issue. Hasn't been for me either.
by vasilipupkin 8y ago
I agree with him. in many practical applications with well design class hierarchies it just really isn't much of an issue. Hasn't been for me either.
- fetbaffe 8y ago> with well design class hierarchies :eyes:
- aldanor 8y ago... and with proper use of Design Patterns!
- vasilipupkin 8y agoyou can roll eyes at me all you want, but I've been programming in C++ for a long time. These memory access issues just don't seem to be a big problem for us in practice. That's because we wrap all raw memory manipulation in appropriate classes for our application, so it's just not an issue. I agree it could be an issue in theory.
- ncmncm 8y agoHe rolls his eyes at "hierarchies". Libraries do make the difference. Somebody else interjected Design Patterns. You can define a design pattern as a weakness in your language's ability to express a library function to do the job.