Skip site navigation (1) Skip section navigation (2)

Re: msvc const warnings

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Gregory Stark <stark(at)enterprisedb(dot)com>, pgsql-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: msvc const warnings
Date: 2007-07-24 19:31:19
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
Tom Lane wrote:
> Gregory Stark <stark(at)enterprisedb(dot)com> 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.

Sure, there are a couple of places we can do it:
1) We can add the pragma at the top of the file, which will turn it off
for that file, but keep it for other files.
2) We can turn it off on a per-project basis, meaning we turn it off for
the entire backend and the entire psql, but not for other EXEs and DLLs.
3) We can just turn it off for everything

Note that it'll of course turn off the warning in *all* cases, not just
the "free const chra **"-one.

Which way would be preferred?


In response to


pgsql-patches by date

Next:From: Andrew DunstanDate: 2007-07-24 19:40:58
Subject: Re: msvc const warnings
Previous:From: Bruce MomjianDate: 2007-07-24 18:53:14
Subject: Re: tsearch core path, v0.58

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group