Re: PostgreSQL future ideas - Mailing list pgsql-hackers

From Marko Kreen
Subject Re: PostgreSQL future ideas
Date
Msg-id e51f66da0809250620j4c49d8b0h303be7bbaec6a68e@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL future ideas  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 9/25/08, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Zdenek Kotala <Zdenek.Kotala@Sun.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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Add default_val to pg_settings
Next
From: Simon Riggs
Date:
Subject: Re: Add default_val to pg_settings