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

Re: volatile markings to silence compilers

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: volatile markings to silence compilers
Date: 2011-03-17 14:03:43
Message-ID: AANLkTik000goBGFSvTDT+VfMeW1xg0aKG9t=+QO0it=S@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Thu, Mar 17, 2011 at 12:36 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Looking over the release notes, we have added a few 'volatile' storage
> specifications to variables which are near longjump/TRY blocks to
> silence compilers.  I am worried that these specifications don't clearly
> identify their purpose.  Can we rename these to use a macro for
> 'volatile' that will make their purpose clearer and perhaps their
> removal one day easier?

I don't particularly see the point of this.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

pgsql-hackers by date

Next:From: Robert HaasDate: 2011-03-17 14:09:56
Subject: Re: Rectifying wrong Date outputs
Previous:From: Robert HaasDate: 2011-03-17 14:02:07
Subject: Re: really lazy vacuums?

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