| From: | "Chuck McDevitt" <cmcdevitt(at)greenplum(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Neil Conway" <neilc(at)samurai(dot)com>, "Jacob Rief" <jacob(dot)rief(at)gmx(dot)at>, pgsql-patches(at)postgresql(dot)org, andrew(at)dunslane(dot)net |
| Subject: | Re: SPI-header-files safe for C++-compiler |
| Date: | 2007-07-02 16:01:47 |
| Message-ID: | EB48EBF3B239E948AC1E3F3780CF8F880244ED84@MI8NYCMAIL02.Mi8.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
>
> BTW, one problem I didn't understand at all was that g++ spit up on
> bitand() and bitor() as function names. Those are not C++ keywords
> to my knowledge; anyone have a theory?
>
I forgot these c++ keywords, as you never need to use them in a c++
program:
and bitand compl not_eq or_eq xor_eq
and_eq bitor not or xor
They are equivalents of the operators for use on systems that don't have
full character set support.
Bitand is the same as &, and bitor is the same as |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Rief | 2007-07-02 20:33:25 | Re: SPI-header-files safe for C++-compiler |
| Previous Message | Kevin Grittner | 2007-07-02 13:50:10 | Re: Warm standby patch |