> But keep in mind that "buffer overflow within a struct" is often considered a feature. Yes this is used rampantly in any kind of code that's running in basic

> But keep in mind that "buffer overflow within a struct" is often considered a feature. Yes this is used rampantly in any kind of code that's running in basically all of the world's network appliances that do packet processing. I'd even say it's considered "best practice" by most C programmers.