https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101258
--- Comment #12 from Christopher Yeleighton <giecrilj at stegny dot 2a.pl> --- (In reply to Jonathan Wakely from comment #10) > Lots of things in our API docs are not in the standard, and lots of things > in the standard are not in our API docs. If you're trying to use it for > that, no wonder it's painful. Stop it. The difference between compiler documentation and the standard is that compiler documentation is easier to use and to understand and more task-oriented, although it may be incomplete. I understand the difference. I understand that compiler documentation may sacrifice precision for clarity here and there. The sacrifice must not go too far though---hence my patches to MSDN for example. I still prefer reading the vendor documentation to reading the standard, except in some special cases. I promise I shall stop using GCC documentation if said documentation tells me what I should use instead. I have reported a request regarding that. I can still hardly accept that we are such a failure in this area (I believe that if we have time to implement things, we should also dedicate some to describe them).
