Long paths with ../../../../ throughout

Dave Korn dave.korn.cygwin@googlemail.com
Tue Apr 27 00:59:00 GMT 2010

On 26/04/2010 23:18, Jon wrote:
> Hi Manuel
> Manuel López-Ibáñez wrote, On 25/04/10 22:37:
> [.]
>> http://gcc.gnu.org/wiki/ChangeLog
>> Basically, in your case, do not repeat the filename and mention which
>> function is affected (if any).
> 2010-03-13  Jon Grant <04@jguk.org>
>         * collect2.h: vflag extern changed to bool so true/false can be
> used.
>         * collect2.c: "debug" global variable changed to bool so
> true/false can be used.
>         * "helpflag" bool global variable added.
>         * (main) sets "debug" to true instead of 1 when -debug is passed
> in argv
>         * --help now sets "helpflag" to true instead of 1
>         * --version now sets "vflag" global bool true instead of 1
>         * if "helpflag" is true, standard help information is output on
> stderr
> I have reworked it into that format. 

  Here, sometimes it's easier to show than to explain in terms of rules:

	* collect2.c (vflag): Change type from int to bool.
	(debug): Likewise.
	(helpflag): New global bool.
	(main): Set vflag and debug with boolean, not integer truth
	values.  Accept new "--help" option and output usage text if
	* collect2.h (vflag): Update prototype.
	(debug): Likewise.

  Summary: Asterisks are only used for the first line of each file's changes.
 TABs at the start of every line.  Place the name of the affected entity -
function, variable or macro - in brackets at the start of each line, colon,
space, then say what not why.


More information about the Gcc mailing list