From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
---|---|
To: | Adriaan van Os <pgres(at)microbizz(dot)nl> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #2292: Calling conventions in docs |
Date: | 2006-03-01 19:18:23 |
Message-ID: | 20060301191823.GA14141@wolff.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, Mar 01, 2006 at 13:08:17 +0000,
Adriaan van Os <pgres(at)microbizz(dot)nl> wrote:
>
> Section 32.9.5. Writing Code of the 8.1 docs says:
>
> >>While it may be possible to load functions written in languages other than
> C into PostgreSQL, this is usually difficult (when it is possible at all)
> because other languages, such as C++, FORTRAN, or Pascal often do not follow
> the same calling convention as C. That is, other languages do not pass
> argument and return values between functions in the same way<<
>
> This is nonsense. GNU Pascal and GNU C use the same calling conventions. In
> fact, they share the same compiler-backend.
You seem to be assuming that Postgres will always be built using gcc. That
isn't the case.
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Fitzgerald | 2006-03-01 19:29:38 | Re: BUG #2294: SPI_connect() fails in trigger when a Foreignkey constraint exists on same table as trigger. |
Previous Message | Alvaro Herrera | 2006-03-01 18:57:59 | Re: BUG #2294: SPI_connect() fails in trigger when a Foreignkey constraint exists on same table as trigger. |