AW: Coping with 'C' vs 'newC' function language names - Mailing list pgsql-hackers

From Zeugswetter Andreas SB
Subject AW: Coping with 'C' vs 'newC' function language names
Date
Msg-id 11C1E6749A55D411A9670001FA68796336810D@sdexcsrv1.f000.d0188.sd.spardat.at
Whole thread Raw
Responses Re: Coping with 'C' vs 'newC' function language names  (Marko Kreen <marko@l-t.ee>)
List 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


pgsql-hackers by date:

Previous
From: Zeugswetter Andreas SB
Date:
Subject: AW: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c)
Next
From: Bruce Momjian
Date:
Subject: Re: AW: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c)