Fix sloppy comment.

tglsfdc · tglsfdc · commit b3d7af46a99d · 2003-01-22T20:44:20.000Z
diff --git a/src/backend/utils/adt/date.c b/src/backend/utils/adt/date.c
@@ -8,7 +8,7 @@
  *
  *
  * IDENTIFICATION
- *	  $Header: /cvsroot/pgsql/src/backend/utils/adt/date.c,v 1.75 2003/01/09 01:06:57 tgl Exp $
+ *	  $Header: /cvsroot/pgsql/src/backend/utils/adt/date.c,v 1.76 2003/01/22 20:44:20 tgl Exp $
  *
  *-------------------------------------------------------------------------
  */
@@ -656,7 +656,7 @@ AdjustTimeForTypmod(TimeADT *time, int32 typmod)
 		/*
 		 * Note: this round-to-nearest code is not completely consistent
 		 * about rounding values that are exactly halfway between integral
-		 * values.  On most platforms, rint() will implement round-to-nearest,
+		 * values.  On most platforms, rint() will implement round-to-nearest-even,
 		 * but the integer code always rounds up (away from zero).  Is it
 		 * worth trying to be consistent?
 		 */
diff --git a/src/backend/utils/adt/timestamp.c b/src/backend/utils/adt/timestamp.c
@@ -8,7 +8,7 @@
  *
  *
  * IDENTIFICATION
- *	  $Header: /cvsroot/pgsql/src/backend/utils/adt/timestamp.c,v 1.76 2003/01/09 01:06:57 tgl Exp $
+ *	  $Header: /cvsroot/pgsql/src/backend/utils/adt/timestamp.c,v 1.77 2003/01/22 20:44:20 tgl Exp $
  *
  *-------------------------------------------------------------------------
  */
@@ -206,7 +206,7 @@ AdjustTimestampForTypmod(Timestamp *time, int32 typmod)
 		/*
 		 * Note: this round-to-nearest code is not completely consistent
 		 * about rounding values that are exactly halfway between integral
-		 * values.  On most platforms, rint() will implement round-to-nearest,
+		 * values.  On most platforms, rint() will implement round-to-nearest-even,
 		 * but the integer code always rounds up (away from zero).  Is it
 		 * worth trying to be consistent?
 		 */
@@ -677,7 +677,7 @@ AdjustIntervalForTypmod(Interval *interval, int32 typmod)
 			/*
 			 * Note: this round-to-nearest code is not completely consistent
 			 * about rounding values that are exactly halfway between integral
-			 * values.  On most platforms, rint() will implement round-to-nearest,
+			 * values.  On most platforms, rint() will implement round-to-nearest-even,
 			 * but the integer code always rounds up (away from zero).  Is it
 			 * worth trying to be consistent?
 			 */

Original file line number	Diff line number	Diff line change
`@@ -8,7 +8,7 @@`
`8`	`8`	`*`
`9`	`9`	`*`
`10`	`10`	`* IDENTIFICATION`
`11`		`- * $Header: /cvsroot/pgsql/src/backend/utils/adt/date.c,v 1.75 2003/01/09 01:06:57 tgl Exp $`
	`11`	`+ * $Header: /cvsroot/pgsql/src/backend/utils/adt/date.c,v 1.76 2003/01/22 20:44:20 tgl Exp $`
`12`	`12`	`*`
`13`	`13`	`*-------------------------------------------------------------------------`
`14`	`14`	`*/`
`@@ -656,7 +656,7 @@ AdjustTimeForTypmod(TimeADT *time, int32 typmod)`
`656`	`656`	`/*`
`657`	`657`	`* Note: this round-to-nearest code is not completely consistent`
`658`	`658`	`* about rounding values that are exactly halfway between integral`
`659`		`- * values. On most platforms, rint() will implement round-to-nearest,`
	`659`	`+ * values. On most platforms, rint() will implement round-to-nearest-even,`
`660`	`660`	`* but the integer code always rounds up (away from zero). Is it`
`661`	`661`	`* worth trying to be consistent?`
`662`	`662`	`*/`