Re: s_lock.h default definitions are rather confused - Mailing list pgsql-hackers

From Andres Freund
Subject Re: s_lock.h default definitions are rather confused
Date
Msg-id 20150115160705.GA14782@awork2.anarazel.de
Whole thread Raw
In response to Re: s_lock.h default definitions are rather confused  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: s_lock.h default definitions are rather confused
List pgsql-hackers
On 2015-01-15 10:57:10 -0500, Tom Lane wrote:
> * I've got gaur configured so it will throw "array subscript of type char"
> complaints whenever somebody forgets to cast a <ctype.h> function argument
> to unsigned char.

But, but. That would never happen to anyone (hides).

> While I'll not cry too hard when we decide to break C89 compatibility,
> I don't want it to happen accidentally; so having a pretty old-school
> compiler in the farm seems important to me.

Yea, agreed. I also don't think we want to adopt all of C99 at once, but
rather do it piecemal. Feature by feature.

I'd worked on setting up a modern gcc (or was it clang?) with the
appropriate flags to warn about !C89 stuff some time back, but failed
because of configure bugs. I think Robert has committed most of the
fixes since, and I now actually could do the rest one of these days...

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: s_lock.h default definitions are rather confused
Next
From: Sawada Masahiko
Date:
Subject: Re: Merging postgresql.conf and postgresql.auto.conf