为什么不读的标准自己吗？***的文章 IEEE 包含指向标。

Why not read the standard yourself? The Wikipedia article for IEEE contains links to the standard.

请注意：在C的标准文件的不可***。但是的最终草案的是（这是我的联系，搜索，找到的PDF版本）。不过，我从来没见过这里被引用的最后文件和AFAIK曾有大多了一些错别字纠正;没有改变。 IEEE然而，免费提供的。

Note: The C standard document is not available freely. But the final draft is (that's what I linked, search to find the pdf version). However, I've not seen the final document being cited here and AFAIK there had mostly been some typos corrected; nothing changed. IEEE is, however, available for free.

请注意，一个编译器不必坚持标准（一些嵌入式的编译器/版本比如没有实现IEEE-符合浮点值，但仍C-一致 - 只是阅读的细节标准）。故见编译器文档查看兼容。 MS-VC比如是不是甚至C99兼容（永远不会BEN），而gcc和铛/ LLVM是（大部分）在当前版本的C11兼容（GCC 4.9.2，因为至少在自4.7份）。

Note that a compiler need not stick to the standards (some embedded compilers/versions for instance do not implement IEEE-conforming floating point values, but are still C-conforming - just read the standard for details). So see the compiler documentation to see the compatibility. MS-VC for instance is not even compatible to C99 (and will never ben), while gcc and clang/llvm are (mostly) compatible to C11 in the current versions (gcc since 4.9.2 at least, in parts since 4.7).

在一般情况下，使用MS-VC时，检查它是否真正的确实的使用的所有标准功能的支持。它实际上是不能完全兼容当前的标准，也不是C99。

In general, when using MS-VC, check if it actually does support that all standard features used. It is actually not fully compliant to the current standard, nor C99.