Tom Lane <t...@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
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
