From: | Marko Kreen <markokr(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Kurt Harriman <harriman(at)acm(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Patch: Remove gcc dependency in definition of inline functions |
Date: | 2009-12-16 14:30:19 |
Message-ID: | e51f66da0912160630y1a92cb56p99b10343ec249410@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12/16/09, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Tue, Dec 15, 2009 at 10:34 PM, Kurt Harriman <harriman(at)acm(dot)org> wrote:
> >> Your worry ii) can be ignored, managing to compile on such
> >> compilers is already overachievement.
> >
> > I think so too. With your opinion added to mine, do we constitute a
> > consensus of the pg community? Someone might object that a sample of
> > two individuals is insufficiently representative of the whole, but
> > away with the pedants: let us not quibble over trifles.
>
>
> I haven't completely followed this thread, but I think there has been
> some discussion of making changes to inline that would cause
> regressions for people using old, crappy compilers, and I think we
> should avoid doing that unless there is some compelling benefit. I'm
> not sure what that benefit would be - I don't think "cleaner code" is
> enough.
Seems you have not followed the thread...
Hypothetical old, crappy compilers would still work, only AC_C_INLINE
would turn "static inline" into plain "static", so hypothetically
they would get some warnings about unused functions.
As this is all hypothetical, I don't see why that should stop us
cleaning our code?
--
marko
From | Date | Subject | |
---|---|---|---|
Next Message | Boszormenyi Zoltan | 2009-12-16 14:41:03 | Re: ECPG patch 2, SQLDA support |
Previous Message | Marko Kreen | 2009-12-16 14:23:51 | Re: Patch: Remove gcc dependency in definition of inline functions |