Tom Lane wrote: > [EMAIL PROTECTED] (Bruce Momjian) writes: > > Prevent certain symbols that are used for both typedefs and variable > > names from being added to pgindent's typedef list. The existance of > > them caused weird formatting in the date/type files, and in keywords.c. > > Maybe it would be better to do some judicious renaming in the sources > to avoid the conflicts? ISTM that failing to mark a typedef as such > will inevitably result in bad formatting of code that uses the name > as a typedef.
Yea, but I don't want to do anything like that now, especially since most of the date/time typedefs are used by ecpg and I am unsure what affect changing those might have. My logic was that is was better to have ecpg unclearly typedef'ed in a few places than to have an adt/ file show "interval ->days". "ANY" is coming from plperl but I can't see from where. -- Bruce Momjian | http://candle.pha.pa.us [email protected] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
