From 6fb05e06a317962ea84eee570d1b9f067813a799 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Mon, 19 Aug 2002 00:10:03 +0000 Subject: [PATCH] Improve obsolete comment. --- src/include/nodes/pg_list.h | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/src/include/nodes/pg_list.h b/src/include/nodes/pg_list.h index a6854d1688..e1de57b53e 100644 --- a/src/include/nodes/pg_list.h +++ b/src/include/nodes/pg_list.h @@ -7,7 +7,7 @@ * Portions Copyright (c) 1996-2002, PostgreSQL Global Development Group * Portions Copyright (c) 1994, Regents of the University of California * - * $Id: pg_list.h,v 1.28 2002/06/20 20:29:51 momjian Exp $ + * $Id: pg_list.h,v 1.29 2002/08/19 00:10:03 tgl Exp $ * *------------------------------------------------------------------------- */ @@ -24,10 +24,12 @@ /*---------------------- * Value node * - * The same Value struct is used for three node types: T_Integer, - * T_Float, and T_String. Integral values are actually represented - * by a machine integer, but both floats and strings are represented - * as strings. Using T_Float as the node type simply indicates that + * The same Value struct is used for five node types: T_Integer, + * T_Float, T_String, T_BitString, T_Null. + * + * Integral values are actually represented by a machine integer, + * but both floats and strings are represented as strings. + * Using T_Float as the node type simply indicates that * the contents of the string look like a valid numeric literal. * * (Before Postgres 7.0, we used a double to represent T_Float, @@ -38,6 +40,8 @@ * * Note that an integer-looking string will get lexed as T_Float if * the value is too large to fit in a 'long'. + * + * Nulls, of course, don't need the value part at all. *---------------------- */ typedef struct Value -- 2.11.0