| 1 |
On 06/26/2012 06:59 AM, Duncan wrote: |
| 2 |
> Ryan Hill posted on Mon, 25 Jun 2012 22:57:30 -0600 as excerpted: |
| 3 |
> |
| 4 |
>> On Mon, 14 May 2012 19:58:13 +0100 Markos Chandras <hwoarang@g.o> |
| 5 |
>> wrote: |
| 6 |
>> |
| 7 |
>>> On 05/14/2012 06:03 PM, hasufell wrote: |
| 8 |
>>>> So, I will file a documentation bug unless someone can point me in |
| 9 |
>>>> the right direction. I didn't find a reference to that issue. |
| 10 |
>> |
| 11 |
>>> Open a bug, write a devmanual patch and I will be happy to apply it |
| 12 |
>> |
| 13 |
>> FWIW I started a compiler flag policy / best-practice guide a while |
| 14 |
>> back. |
| 15 |
>> One of these years I'll get around to actually writing it. :p |
| 16 |
> |
| 17 |
> FWIW, flameeyes' blog has a lot of this sort of content, and with his |
| 18 |
> autotools mythbuster and similar content as well, I gather there's at |
| 19 |
> least some upstream eyes following it. |
| 20 |
> |
| 21 |
> So that's a bit of a start for anyone looking for such information right |
| 22 |
> now, as well as reasonable research for anyone else considering writing |
| 23 |
> such a guide who might want some other references or quote-worthy |
| 24 |
> material. |
| 25 |
> |
| 26 |
> I believe he has specifically covered -Werror too. I know he mentioned |
| 27 |
> it (with a link to /something/, of his or not I didn't check) in a recent |
| 28 |
> entry. |
| 29 |
> |
| 30 |
|
| 31 |
Then he should write it. +1 for that |
Archives