On Jul 26, 5:37 pm, Pete Becker <p...@versatilecoding.com> wrote:
James Kanze wrote:
On Jul 26, 12:00 pm, "Fraser Ross" <z...@zzzzzz.com> wrote:
I've been looking at N2914. 3.6.3/3 only refers to non-local
statics.
There is no such thing as N2914. (The latest I can see is
N2881.)
N2914 is the working draft in the pre-Frankfurt mailing. It's
dated 2009-06-22. It's now the current working draft.
So I see. And I didn't have the latest mailings downloaded to
my machine here.
The wording of ?3.6.3 has been completely changed with regards
to the standard, to take into account threading and thread local
storage. And ?3.6.3 has been changed to exclude static objects
with local scope. Is this intentional, and for what reason?
(It may break existing programs.) Or is it an unintentional
side effect of some other change? I presume that the intent
here is to exclude objects with thread storage duration; if so,
should I raise a defect report, or is the original intent clear
enough that you could handle it as an editorial change. (It
looks a bit big for an editorial change to me, but if the
proposal that was actually voted on was clear, perhaps that
would be acceptable.)
It's still under discussion. See N2880 and and N2917. The problem
Roundhouse Consulting, Ltd. (www.versatilecoding.com) Author of