------=_Part_960_1286445495.1443800775203
Content-Type: multipart/alternative;
 boundary="----=_Part_961_1837466408.1443800775203"

------=_Part_961_1837466408.1443800775203
Content-Type: text/plain; charset=UTF-8

I don't know if this is the place to discuss it, but from the recent
mailing, it's apparent that there is a new naming convention: P*XXXX*R*Y*.

My question is this: is the R*Y* part a revision number, so that as a paper
gets revised it *doesn't* get a whole new number? Because that'd be good.

--

---
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/.

------=_Part_961_1837466408.1443800775203
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I don&#39;t know if this is the place to discuss it, but f=
rom the recent mailing, it&#39;s apparent that there is a new naming conven=
tion: P<i>XXXX</i>R<i>Y</i>.<br><br>My question is this: is the R<i>Y</i> p=
art a revision number, so that as a paper gets revised it <i>doesn&#39;t</i=
> get a whole new number? Because that&#39;d be good.<br></div>

<p></p>

-- <br />
<br />
--- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:std-proposals+unsubscribe@isocpp.org">std-proposa=
ls+unsubscribe@isocpp.org</a>.<br />
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org">std-proposals@isocpp.org</a>.<br />
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/">http://groups.google.com/a/isocpp.org/group/std-proposals/<=
/a>.<br />

------=_Part_961_1837466408.1443800775203--
------=_Part_960_1286445495.1443800775203--

.

On 02/10/15 16:46, Nicol Bolas wrote:
> I don't know if this is the place to discuss it, but from the recent
> mailing, it's apparent that there is a new naming convention: P/XXXX/R/Y/.
>
> My question is this: is the R/Y/ part a revision number, so that as a
> paper gets revised it /doesn't/ get a whole new number? Because that'd
> be good.

Yes, the RY part is the revision number. Every paper starts at R0.

Anthony
--
Author of C++ Concurrency in Action     http://www.stdthread.co.uk/book/
just::thread C++11 thread library             http://www.stdthread.co.uk
Just Software Solutions Ltd       http://www.justsoftwaresolutions.co.uk
15 Carrallack Mews, St Just, Cornwall, TR19 7UL, UK. Company No. 5478976

--

---
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/.

.

2015-10-02 17:46 GMT+02:00 Nicol Bolas <jmckesson@gmail.com>:
> I don't know if this is the place to discuss it, but from the recent
> mailing, it's apparent that there is a new naming convention: PXXXXRY.
>
> My question is this: is the RY part a revision number, so that as a paper
> gets revised it doesn't get a whole new number? Because that'd be good.

Augmenting Anthony reply: If you want to write a proposal that would
be the n-th revision of a previous N-numbered document, you would
still need to allocate a fresh R number and that first n-th revision
would still start with R0, *not* Rn.

I'm not yet sure how P numbering works, if authors X want to write a
revision to PnnnnRx of author Y. I'll return with that information
once I do know this.

- Daniel

--

---
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/.

.

2015-10-02 19:14 GMT+02:00 Daniel Kr=C3=BCgler <daniel.kruegler@gmail.com>:
> 2015-10-02 17:46 GMT+02:00 Nicol Bolas <jmckesson@gmail.com>:
>> I don't know if this is the place to discuss it, but from the recent
>> mailing, it's apparent that there is a new naming convention: PXXXXRY.
>>
>> My question is this: is the RY part a revision number, so that as a pape=
r
>> gets revised it doesn't get a whole new number? Because that'd be good.
>
> Augmenting Anthony reply: If you want to write a proposal that would
> be the n-th revision of a previous N-numbered document, you would
> still need to allocate a fresh R number and that first n-th revision
> would still start with R0, *not* Rn.
>
> I'm not yet sure how P numbering works, if authors X want to write a
> revision to PnnnnRx of author Y. I'll return with that information
> once I do know this.

OK, I got the answer to that: In such a case author Y would allocate a
new document number Pyyyy and would use PyyyyR0 for the first revision
to PnnnnRx.

Summarizing: A given main author "owns" a P-number and the R series is
not necessarily related to absolute revision of other N or P numbers
which can also be revised.

- Daniel

--=20

---=20
You received this message because you are subscribed to the Google Groups "=
ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposa=
ls/.

.