This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: What tells the coding style about whitespaces at end of lines or in empty lines ?

From: Robert Dewar <dewar at adacore dot com>
To: Kai Tietz <Kai dot Tietz at onevision dot com>
Cc: gcc at gcc dot gnu dot org
Date: Thu, 01 Mar 2007 08:38:10 -0500
Subject: Re: What tells the coding style about whitespaces at end of lines or in *empty* lines ?
References: <OFA282D026.BD3C558B-ONC1257291.0049E3A1-C1257291.004A91F0@onevision.de>

Kai Tietz wrote:

Hi,

I noticed while editing gcc files, that there are a lot of *useless* whitespaces at the end of lines or within empty lines, which are getting automatic removed by some *smarter* editors as I am common to use *sigh*. This leads to huge diff files and the real change is getting veiled. I think it would be nice to eliminate these *usesless* whitespaces.


Note that the coding standard for GNAT forbids trailing white spaces.
It also forbids embedded horizontal tabs for similar reasons (avoiding
junk difs).

Follow-Ups:
- Re: What tells the coding style about whitespaces at end of lines or in *empty* lines ?
  - From: Duncan Sands
- Re: What tells the coding style about whitespaces at end of lines or in *empty* lines ?
  - From: Richard Kenner

References:
- What tells the coding style about whitespaces at end of lines or in *empty* lines ?
  - From: Kai Tietz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: What tells the coding style about whitespaces at end of lines or in *empty* lines ?

Re: What tells the coding style about whitespaces at end of lines or in empty lines ?