AW: Coping with 'C' vs 'newC' function language names

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: AW: Coping with 'C' vs 'newC' function language names
Date: 2000-11-13 08:58:30
Message-ID: 11C1E6749A55D411A9670001FA68796336810D@sdexcsrv1.f000.d0188.sd.spardat.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> > because as said, it can be any other language besides C and also
> > the 'AS file' is weird.
>
> This is interesting. It allows us to control the default behavour of
> "C". I would vote to default to 7.0-style when no version is used for
> 7.1, then default to 7.1 style in 7.2 and later. We don't need
> backward C function compatibility for more than one release, I think.

We need the 7.0 style for compatibility with other DB's. Postgres was
"the" pioneer in this area, but similar functionality is now available in other DB's.

I think it would be worthwhile, to at least peek at what Informix and DB/2
does here.

Andreas

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Frank Jördens 2000-11-13 11:27:13 Re: [HACKERS] Re: DBD::Pg installation seems to fail with 7.1 libs
Previous Message Zeugswetter Andreas SB 2000-11-13 08:36:53 AW: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c)