Complete.Org: Mailing Lists: Archives: freeciv-dev: April 2004:
[Freeciv-Dev] Re: (PR#8547) GCC poisoning v2
Home

[Freeciv-Dev] Re: (PR#8547) GCC poisoning v2

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: per@xxxxxxxxxxx
Subject: [Freeciv-Dev] Re: (PR#8547) GCC poisoning v2
From: "Jason Short" <jdorje@xxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 20 Apr 2004 11:54:53 -0700
Reply-to: rt@xxxxxxxxxxx

<URL: http://rt.freeciv.org/Ticket/Display.html?id=8547 >

Per I. Mathisen wrote:

> Yes, we don't really have to have this activated all the time. If we just
> put in all the necessary changes (moving stuff around, headers), then the
> gcc poisoning _can_ be there but not used until we want to. However, if
> there are no good reasons against, I think adding gcc poisoning all the
> time might be just as good - it makes patch authors learn. Maybe commit
> with poisoning default on, then turn it off if people get problems?

I prefer to have it on.  I make these mistakes often and this will catch 
them at the time of writing.

jason




[Prev in Thread] Current Thread [Next in Thread]