|
7 | 7 | * Portions Copyright (c) 1996-2002, PostgreSQL Global Development Group |
8 | 8 | * Portions Copyright (c) 1994, Regents of the University of California |
9 | 9 | * |
10 | | - * $Id: pg_list.h,v 1.28 2002/06/20 20:29:51 momjian Exp $ |
| 10 | + * $Id: pg_list.h,v 1.29 2002/08/19 00:10:03 tgl Exp $ |
11 | 11 | * |
12 | 12 | *------------------------------------------------------------------------- |
13 | 13 | */ |
|
24 | 24 | /*---------------------- |
25 | 25 | *Value node |
26 | 26 | * |
27 | | - * The same Value struct is used for three node types: T_Integer, |
28 | | - * T_Float, and T_String. Integral values are actually represented |
29 | | - * by a machine integer, but both floats and strings are represented |
30 | | - * as strings.Using T_Float as the node type simply indicates that |
| 27 | + * The same Value struct is used for five node types: T_Integer, |
| 28 | + * T_Float, T_String, T_BitString, T_Null. |
| 29 | + * |
| 30 | + * Integral values are actually represented by a machine integer, |
| 31 | + * but both floats and strings are represented as strings. |
| 32 | + * Using T_Float as the node type simply indicates that |
31 | 33 | * the contents of the string look like a valid numeric literal. |
32 | 34 | * |
33 | 35 | * (Before Postgres 7.0, we used a double to represent T_Float, |
|
38 | 40 | * |
39 | 41 | * Note that an integer-looking string will get lexed as T_Float if |
40 | 42 | * the value is too large to fit in a 'long'. |
| 43 | + * |
| 44 | + * Nulls, of course, don't need the value part at all. |
41 | 45 | *---------------------- |
42 | 46 | */ |
43 | 47 | typedefstructValue |
|