From: | Kurt Roeckx <Q(at)ping(dot)be> |
---|---|
To: | Dann Corbit <DCorbit(at)connx(dot)com>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: 7.5 beta version |
Date: | 2004-04-13 22:22:18 |
Message-ID: | 20040413222218.GA27350@ping.be |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Apr 12, 2004 at 10:00:05PM +0200, Jeroen T. Vermeulen wrote:
> On Mon, Apr 12, 2004 at 12:35:15PM -0700, Dann Corbit wrote:
>
> > I do know of important differences in compilers in this regard. You can
> > (for instance) have 80 bit floating point on one compiler using double
> > but it is only 64 bits on another.
>
> But in the case of x86 (among others) that's the in-register
> representation, no? IIRC they are stored to memory as 64-bit doubles at
> best.
You also have "long double"s on some compilers which could be 80 bit.
> In C++, ABI compatibility is normally protected through a side effect of
> name mangling. By maintaining different name mangling schemes for
> different ABI conventions, compiler vendors ensure that object files will
> refuse to link to other object files that adhere to different ABIs.
We gave up trying to make C++ dlls on windows because of ABI/name
mangling problems, never tried it again though.
The compilers from Microsoft and Borland atleast aren't
compatible.
Kurt
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2004-04-14 01:18:55 | Re: Lexing with different charsets |
Previous Message | Josh Berkus | 2004-04-13 22:20:16 | Remove MySQL Tools from Source? |