[Boost-commit] svn:boost r42022 - sandbox/committee/LWG

From: bdawes_at_[hidden]
Date: 2007-12-13 17:50:22

Author: bemandawes
Date: 2007-12-13 17:50:22 EST (Thu, 13 Dec 2007)
New Revision: 42022
URL: http://svn.boost.org/trac/boost/changeset/42022

Log:
V1 issues 50-53, 56-58
Text files modified: 
   sandbox/committee/LWG/issues.html         |    14 +++++++-------                          
   sandbox/committee/LWG/thread_library.html |    28 +++++++++++++++++++++-------            
   2 files changed, 28 insertions(+), 14 deletions(-)

Modified: sandbox/committee/LWG/issues.html
==============================================================================
--- sandbox/committee/LWG/issues.html	(original)
+++ sandbox/committee/LWG/issues.html	2007-12-13 17:50:22 EST (Thu, 13 Dec 2007)
@@ -300,19 +300,19 @@
 defined to be d.tick_count() at entry into the function? Also, in the
 postconditions for -= and +=, the firs tmention of tick_count needs ()
 afterwards. </p>
-<p>50. [time.nanoseconds] (31.2): first paragraph mixes non-normative and
+<p>&#10004; 50. [time.nanoseconds] (31.2): first paragraph mixes non-normative and
 normative text. Put the second sentence into a separate paragraph. </p>
-<p>51. [time.microseconds] (31.3): see 50. </p>
-<p>52. [time.milliseconds] (31.4): see 50. </p>
-<p>53. [time.seconds] (31.5): see 50. </p>
+<p>&#10004; 51. [time.microseconds] (31.3): see 50. </p>
+<p>&#10004; 52. [time.milliseconds] (31.4): see 50. </p>
+<p>&#10004; 53. [time.seconds] (31.5): see 50. </p>
 <p>54. [time.seconds] (31.5) and the rest: would it help to write those
 multipliers as factors of 1000? So, for example, seconds::nanoseconds()
 instead of returning count() * 1000000000 would return count() * 1000
 * 1000 *
 1000. </p>
-<p>56. [time.minutes] (31.6): see 50. </p>
-<p>57. [time.hours] (31.7): see 50. </p>
-<p>58. [time.system] (31.8): separate non-normative from normative text:
+<p>&#10004; 56. [time.minutes] (31.6): see 50. </p>
+<p>&#10004; 57. [time.hours] (31.7): see 50. </p>
+<p>&#10004; 58. [time.system] (31.8): separate non-normative from normative text:
 break
 into two paragraphs. </p>
 <p>59. [time.nonmembers] (31.9): would it help with the comparison

Modified: sandbox/committee/LWG/thread_library.html
==============================================================================
--- sandbox/committee/LWG/thread_library.html	(original)
+++ sandbox/committee/LWG/thread_library.html	2007-12-13 17:50:22 EST (Thu, 13 Dec 2007)
@@ -3869,7 +3869,9 @@
 
 <p>
 Objects of class <code>nanoseconds</code>
-can be used to represent a count of nanoseconds.
+can be used to represent a count of nanoseconds.</p>
+
+<p>
 Class <code>nanoseconds</code>
 shall be a duration type ([time.duration.requirements]).
 For the sake of exposition,
@@ -3930,7 +3932,9 @@
 
 <p>
 Objects of class <code>microseconds</code>
-can be used to represent a count of microseconds.
+can be used to represent a count of microseconds.</p>
+
+<p>
 Class <code>microseconds</code>
 shall be a duration type ([time.duration.requirements]).
 For the sake of exposition, the semantics of member functions are not described
@@ -4007,7 +4011,9 @@
 
 <p>
 Objects of class <code>milliseconds</code>
-can be used to represent a count of milliseconds.
+can be used to represent a count of milliseconds.</p>
+
+<p>
 Class <code>milliseconds</code>
 shall be a duration type ([time.duration.requirements]).
 For the sake of exposition,
@@ -4100,7 +4106,9 @@
 
 <p>
 Objects of class <code>seconds</code>
-can be used to represent a count of seconds.
+can be used to represent a count of seconds.</p>
+
+<p>
 Class <code>seconds</code>
 shall be a duration type ([time.duration.requirements]).
 For the sake of exposition,
@@ -4208,7 +4216,9 @@
 
 <p>
 Objects of class <code>minutes</code>
-can be used to represent a count of minutes.
+can be used to represent a count of minutes.</p>
+
+<p>
 Class <code>minutes</code>
 shall be a duration type ([time.duration.requirements]).
 For the sake of exposition,
@@ -4331,7 +4341,9 @@
 
 <p>
 Objects of class <code>hours</code>
-can be used to represent a count of hours.
+can be used to represent a count of hours.</p>
+
+<p>
 Class <code>hours</code>
 shall be a duration type ([time.duration.requirements]).
 For the sake of exposition,
@@ -4470,7 +4482,9 @@
 <p>
 The class <code>system_time</code> provides a time point
 that represents the current
-Coordinated Universal Time, known as UTC, time.
+Coordinated Universal Time, known as UTC, time.</p>
+
+<p>
 <code>system_time</code>
 shall provide an epoch time of 1970-01-01 00:00:00.000000000
 and a maximum time value of at least epoch time + 292 years.