Namespaces
Variants
Views
Actions

Talk:c/header

From cppreference.com

Contents

[edit] Formatting header lists

Header lists are quite ugly compared to other pages. What about the following styles?

Plain dcl list item
<assert.h> Conditionally compiled macro that compares its argument to zero
<complex.h> (since C99) Complex number arithmetic
Using dcl member
<assert.h>
Conditionally compiled macro that compares its argument to zero
<complex.h>
(since C99)
Complex number arithmetic

--Bazzy 05:36, 24 April 2012 (PDT)

I like this idea -- I prefer the aesthetics and it's more consistent with the rest of the site. I say do it. With perhaps a slight vote in favor of the plain dcl list item over the dcl member version. --Nate 06:26, 24 April 2012 (PDT)
I'm in favor of using the bold monospace version. There's no need to use dcl member as there's no link to show. The same effect can be achieved by using {{ttb}}.
Plain dcl list item
<assert.h> Conditionally compiled macro that compares its argument to zero
<complex.h> (since C99) Complex number arithmetic
-- P12 07:55, 24 April 2012 (PDT)
Done. I've used list_item+ttb. ( ttb was already around header names ) --Bazzy 12:04, 24 April 2012 (PDT)

[edit] __STDC_IEC_559__

Given footnote 3 on page 8 of n1570, should all examples in headers math.h and fenv.h be guarded by "#ifdef __STDC_IEC_559__...#endif" to make the examples strictly conforming? Newatthis (talk) 05:19, 21 October 2014 (PDT)

I don't think it is practical, how many compilers do you know that do not at least claim to implement IEEE 754 floating-point numbers? You might as well suggest checking __STDC__ in every example and __STDC_VERSION__ in every example that goes beyond C89. I don't think feature test macros belong in usage examples (but they do belong to the descriptions of their respective features) --Cubbi (talk) 06:23, 21 October 2014 (PDT)