Gavin Sherry <[EMAIL PROTECTED]> writes:
> The attached patch clarifies (or, rather, makes explicit) to readers how
> to handle memory management for char pointers returned by libpq
> functions.
Patch applied. I expanded the tabs in that file to 4 spaces, per the
discussion. I also noticed and fix
Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > Please don't put tabs in SGML files.
>
> That's a new one on me. Why should we avoid tabs? The existing
> files are certainly full of them.
Those are just the files that I haven't edited recently and gave the old
"M-x untabify"
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Please don't put tabs in SGML files.
That's a new one on me. Why should we avoid tabs? The existing files
are certainly full of them.
regards, tom lane
---(end of broadcast)--
Gavin Sherry wrote:
> The attached patch clarifies (or, rather, makes explicit) to readers
> how to handle memory management for char pointers returned by libpq
> functions. Although the sections on PQfinish(), PQclear() and
> PQfreemem() give an indication that all pointers returned by
> functions
