[v3] add c_compatibility headers, gcc bits

Zack Weinberg zack@codesourcery.com
Fri Jun 21 18:35:00 GMT 2002


On Fri, Jun 21, 2002 at 08:46:47PM -0400, Phil Edwards wrote:
> On Fri, Jun 21, 2002 at 01:43:33PM -0700, Zack Weinberg wrote:
> > On Fri, Jun 21, 2002 at 01:26:27PM -0700, Benjamin Kosnik wrote:
> > ...
> > > + #endif
> > > + 
> > >   #endif /* _STDARG_H */
> > >   
> > >   #endif /* not _ANSI_STDARG_H_ */
> > >   #endif /* not _STDARG_H */
> > > + 
> > > + 
> > > Index: stddef.h
> > 
> > Can you please not introduce blank lines at EOF?
> 
> I've been doing this in many of the libstdc++ headers.

"this" = introducing trailing blank lines, or adding namespace guards?
I have no problem with the latter.

> Nobody's complained.  What's the reasoning behind this?

The trailing blank lines don't do any harm, but I don't see that they
do any good either, and they certainly do cause people to wonder what
they're there for...

zw



More information about the Gcc-patches mailing list