Re: const correctness - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: const correctness
Date
Msg-id 4EBBDEB00200002500042CFF@gw.wicourts.gov
Whole thread Raw
In response to Re: const correctness  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: const correctness
List pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> wrote:
> The problem with it of course is that mistaken use could have the
> effect of casting-away-const, which is exactly what we hoped to
> prevent.  Still, there may not be a better solution.
Yeah, I've come to the conclusion that the compiler doesn't do the
apparently-available optimizations using const precisely because it
is so easy to cast away the property maliciously or accidentally.
-Kevin


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pg_upgrade automatic testing
Next
From: "Kevin Grittner"
Date:
Subject: Re: foreign key locks, 2nd attempt