C++ compiler standards compliance (was: SPI and I2C, was Re: Raspberry Pi and America)

In article <0F2F7083-54E8-49C2-A5EC-308F30C91BB9 at gmail.com>, David Riley <fraveydank at gmail.com> writes: ptrdiff_t has been in MSVC for a long time. In a private reply, David indicated that he meant to say <stdint.h> instead of ptrdiff_t. <stdint.h> is not present in VS2008, but is present in VS2010. However, ptrdiff_t doesn't come from <stdint.h>, it comes from <stddef.h>, which is present in VS2008, and although I don't have them installed, I suspect that it was present in MSVC going all the way back to VC6, which is about 15 years old at this point. I don't mind people picking on the standards compliance of a C++ compiler, but you should at least be accurate when you complain about it or imply that it doesn't support something. Microsoft's compiler has been getting better with each and every release and hasn't ever been "bad" in my opinion. (Anyone who asserts that they should support 100% of the standard in the first release hasn't been reading the standard.) gcc/g++ doesn't support all of the current (or previous) ISO standards for C++ either. -- "The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline> The Computer Graphics Museum <http://computergraphicsmuseum.org> The Terminals Wiki <http://terminals.classiccmp.org> Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com>