On Tue, Jul 24, 2007 at 09:43:51PM +0200, Magnus Hagander wrote:
> Tom Lane wrote:
> > Magnus Hagander <[EMAIL PROTECTED]> writes:
> >> Tom Lane wrote:
> >>> Gregory Stark <[EMAIL PROTECTED]> writes:
> Can we just disable const checking for MSVCC in general without using the
> #pragmas? I
Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
>> Tom Lane wrote:
>>> Gregory Stark <[EMAIL PROTECTED]> writes:
Can we just disable const checking for MSVCC in general without using the
#pragmas? It clearly doesn't understand how const works making that warning
from it
Magnus Hagander <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Gregory Stark <[EMAIL PROTECTED]> writes:
>>> Can we just disable const checking for MSVCC in general without using the
>>> #pragmas? It clearly doesn't understand how const works making that warning
>>> from it useless.
>>
>> +1 ...
Magnus Hagander wrote:
Tom Lane wrote:
Gregory Stark <[EMAIL PROTECTED]> writes:
Can we just disable const checking for MSVCC in general without using the
#pragmas? It clearly doesn't understand how const works making that warning
from it useless.
+1 ... any useful warning of
Tom Lane wrote:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> Can we just disable const checking for MSVCC in general without using the
>> #pragmas? It clearly doesn't understand how const works making that warning
>> from it useless.
>
> +1 ... any useful warning of this kind will be had from ot
Am Dienstag, 24. Juli 2007 17:24 schrieb Gregory Stark:
> Can we just disable const checking for MSVCC in general without using the
> #pragmas? It clearly doesn't understand how const works making that warning
>
> >from it useless.
That was my thought.
--
Peter Eisentraut
http://developer.postgr
Gregory Stark <[EMAIL PROTECTED]> writes:
> Can we just disable const checking for MSVCC in general without using the
> #pragmas? It clearly doesn't understand how const works making that warning
> from it useless.
+1 ... any useful warning of this kind will be had from other compilers.
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> "Magnus Hagander" <[EMAIL PROTECTED]> writes:
>>> Stefan mentioned that the warning may be one that shows up in a different
>>> compiler somewhere as well, thouh, which might indicate that we should fix
>>> the u
Gregory Stark <[EMAIL PROTECTED]> writes:
> "Magnus Hagander" <[EMAIL PROTECTED]> writes:
>> Stefan mentioned that the warning may be one that shows up in a different
>> compiler somewhere as well, thouh, which might indicate that we should fix
>> the underlying issue? (Even if the code is correct,
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> Stefan mentioned that the warning may be one that shows up in a different
> compiler somewhere as well, thouh, which might indicate that we should fix
> the underlying issue? (Even if the code is correct, if it confuses multiple
> compilers...)
I th
MSVC generates a number of const warnings, that's been discussed before
(http://archives.postgresql.org/pgsql-hackers/2007-01/msg01214.php).
Attached patch adds a pragma to get rid of the warnings. Again, not sure if
it's worth it?
I think I need to #ifdef the pragma - gcc generates a warning if
11 matches
Mail list logo