From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jerry Sievert <jerry(at)legitimatesounding(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #15414: extension compilation fails when c++ files are named with .cc |
Date: | 2018-10-01 21:16:06 |
Message-ID: | 29555.1538428566@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Jerry Sievert <jerry(at)legitimatesounding(dot)com> writes:
>> On Oct 1, 2018, at 1:25 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>> 1) Add rules for ".cpp", ".cc", ".C", ".cxx", and ".c++" and whatever
>> else we can think of. Add additional variants whenever somebody
>> presents one (and backpatch it).
> This is a rather disingenuous choice. Perhaps a better approach would be to do a quick survey of the existing c++ extensions (there aren’t very many),
Andres just named five, which is about four too many. I wouldn't mind
adding one more, but it's not very clear where to stop. Most of the ones
he mentioned do seem to have some currency, with the possible exception
of '.C' which as you say is a hazardous choice.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jerry Sievert | 2018-10-01 21:16:30 | Re: BUG #15414: extension compilation fails when c++ files are named with .cc |
Previous Message | Andres Freund | 2018-10-01 21:07:26 | Re: BUG #15414: extension compilation fails when c++ files are named with .cc |