Deep C and C++ (2011)
slideshare.net
Deep C and C++ (2011)
1–10 of 243 posts
Re: Deep C and C++ (2011)
#2Because we 1) for some reason or another we _must_ use C or C++, 2) we're coding for a single CPU platform, and 3) we need to get the friggin' job done in this century.
Re: Deep C and C++ (2011)
#3Re: Deep C and C++ (2011)
#4For this reason, a lot of compilers have options to not strictly enforce the aliasing rules
[edit] Also C and C++ are both permitted to reorder structs, it's just that they don't because that's the easiest way to follow the standard.
Re: Deep C and C++ (2011)
#5But I'm very aware of "smart code" and we shouldn't be writing code that relies on the details (especially ones that might change between compilers)
Re: Deep C and C++ (2011)
#6Re: Deep C and C++ (2011)
#7In an interview, I would much rather hear a person say something about a statically declared variable with no initialization being poor code to leave behind for the next person than some arcana about the standard.
Re: Deep C and C++ (2011)
#8It's a good discussion of the behind the curtains working of compilers But I'm very aware of "smart code" and we shouldn't be writing code that relies on the details (especially ones that might change between compilers)