On Sun, 25 Jan 2015, David Wohlferd wrote:
> >> Arrays and Vectors
> >> Designated Inits: Labeling elements of initializers.
> >
> > I think this one might better be placed in a section on initializers.
>
> Since the only place 'Designated Inits' can be used is on arrays, placing this
> in t
On 1/22/2015 1:23 PM, Joseph Myers wrote:
On Thu, 22 Jan 2015, Jeff Law wrote:
Inline: Defining inline functions (as fast as macros).
Doesn't seem to belong here.
Given that inline isn't really an extension anymore, one could argue this
isn't relevant anymore.
Well, we need to documen
> H, looking at your list, I think it is better to leave things that
> are hard to categorize where they are, as top-level sections within the
> chapter, rather than trying to group them arbitrarily with other things
> that are hard to categorize; the latter only makes things things harder
> t
On Thu, 22 Jan 2015, Jeff Law wrote:
> > > Inline: Defining inline functions (as fast as macros).
> >
> > Doesn't seem to belong here.
> Given that inline isn't really an extension anymore, one could argue this
> isn't relevant anymore.
Well, we need to document -std=gnu89 / __gnu_inline__
On 01/18/15 09:47, Sandra Loosemore wrote:
Arrays and Vectors
Designated Inits: Labeling elements of initializers.
I think this one might better be placed in a section on initializers.
With a pointer/reference in the Array/Vector section.
Pointers to Arrays: Pointers to arrays
On 01/17/2015 04:44 PM, David Wohlferd wrote:
The page for Extensions to the C Language Family
(https://gcc.gnu.org/onlinedocs/gcc/C-Extensions.html) is very long (60+
items) and completely unordered. This makes it hard to find things,
even when you know they are there. I have taken a first sho
The page for Extensions to the C Language Family
(https://gcc.gnu.org/onlinedocs/gcc/C-Extensions.html) is very long (60+
items) and completely unordered. This makes it hard to find things,
even when you know they are there. I have taken a first shot at
grouping these. Hopefully it can at le
