| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-03-17 14:09:56 | Re: Rectifying wrong Date outputs |
| Previous Message | Robert Haas | 2011-03-17 14:02:07 | Re: really lazy vacuums? |