Tom Lane wrote:
> Under *no* circumstances use __inline__, as it will certainly break
> every non-gcc compiler. Use "inline", which we #define appropriately
> at need.
>
OK. (this was from upstream patch.)
>
> I thought we'd concluded that this explanation is pseudo-science?
>
>
[...]
>
> spellcheck...
>
>
>
Right. I'm waiting on a consensus about the UTF8-ness of the solution
before I adjust comments.
cheers
andrew
