Re: PostgreSQL future ideas

From: "Marko Kreen" <markokr(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Zdenek Kotala" <Zdenek(dot)Kotala(at)sun(dot)com>, "Gevik Babakhani" <pgdev(at)xs4all(dot)nl>, "PGSQL Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PostgreSQL future ideas
Date: 2008-09-25 13:20:30
Message-ID: e51f66da0809250620j4c49d8b0h303be7bbaec6a68e@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On 9/25/08, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> writes:
> > Gevik Babakhani napsal(a):
>
> >> I have not investigated this yet. But I am very interested to know what the
> >> advantages would be to "upgrade" the code to C99 standards.
>
> > I think replace macros with inline functions. It brings to ability to
> > monitor them for example by DTrace.
>
>
> C99's definition of inline functions really sucks --- it's awkward to
> use, and essentially doesn't work at all for declaring inlines in header
> files, which would be the main use if we wanted to replace macros with
> inlines. I'm much happier using gcc's version of inline where we really
> need it (which is not that many places anyway).

AFAIK the problem was only with 'extern inline' which is different,
the 'static inline' which is the main replacement for macros,
should behave same?

+1 for C99

--
marko

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Louis-David Mitterrand 2008-09-25 14:13:31 group by error message?
Previous Message Albe Laurenz 2008-09-25 13:04:04 Re: namespace in pgsql

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2008-09-25 13:23:22 Re: Add default_val to pg_settings
Previous Message Tom Lane 2008-09-25 13:15:29 Re: Add default_val to pg_settings