Subject: Re: [GENERAL] C++ port of Postgres
To: Thomas Munro <thomas.munro@enterprisedb.com>
References: 
 <CABgyVxDBd3EvRdo-Rd6eo8QPEqV8=ShaU2SJfo16wfE0R-hXTA@mail.gmail.com>
 <CABgyVxBA24NnPri8BYQFjVdn2pgqcB=Q6MXFXdcwchUmJSAUPw@mail.gmail.com>
 <CAOmy0wLcyE3d=jbfpgoKtTicGoZ64AKKfEkG+ccXxtmajSBGeQ@mail.gmail.com>
 <CABgyVxBjX6VbnbHfZRSDJBav4xKH5vSLZqTpr989sMOb+jX+jA@mail.gmail.com>
 <CAMjNa7e7E81T3NqoReixYxrCFQpfWd+Mht0NhetW3bJB=Gs7Og@mail.gmail.com>
 <007001d1f786$d903fa90$8b0befb0$@andl.org>
 <00a52208-3199-5858-8846-2530b0bb34df@archidevsys.co.nz>
 <f7682c24-4271-1ff5-d963-053ecb0fce40@BlueTreble.com>
 <CA+Tgmoa8=kMNkOGDCZYR-L_PAoQ2Vdb9EmSV+=7pRv+J3u7_CA@mail.gmail.com>
 <27271.1471366764@sss.pgh.pa.us>
 <CA+TgmoZYjv9xWub1kbcSWC_RPg3qB_ELNBhQOki1g387JMyoVg@mail.gmail.com>
 <CABgyVxAO57r=cE0TdMn2XpBDO=d3cj289ep3xQu=8K-tWs79+w@mail.gmail.com>
 <66b61d8b-fe76-d4a9-a983-93a94444a2a6@BlueTreble.com>
 <bf9de63c-b669-4b8c-d33b-4a5ed11cd5d4@2ndquadrant.com>
 <CAEepm=0OtZ9i-G48dAGtdcsvkhUvmZrxn7ODJRkMbdGmPw6nLw@mail.gmail.com>
 <CAEepm=17=83AzSL7yUe4DQXRD4zC9_cN_9sW6yTpCuatmx4xQg@mail.gmail.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>,
 Jim Nasby <Jim.Nasby@bluetreble.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Organization: 2ndQuadrant
Message-ID: <6703fdf2-d0e8-54f5-333a-19220d9a716a@2ndquadrant.com>
Date: Fri, 30 Sep 2016 15:24:09 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0)
 Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: 
 <CAEepm=17=83AzSL7yUe4DQXRD4zC9_cN_9sW6yTpCuatmx4xQg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

On 9/28/16 10:48 PM, Thomas Munro wrote:
> I wonder if the following bit of gin.h should be more nuanced: maybe
> it's OK to convert between bool and GinTernaryValue, but it's
> definitely not OK to cast between pointers types?  Or maybe we should
> have a function/macro to convert between the types explicitly and not
> encourage people to consider them convertible.

The more I look into the this, the more this looks like a web of lies.
:-)  The GIN consistent and triconsistent functions randomly change
around between bool and GinTernaryValue, share some of the same data
structures, and there is little guarantee that they each get the right
kind of value all the time.  This could perhaps use some deeper cleaning
at some point.  I've left that alone for now.

>> 0009-Rename-some-typedefs-to-avoid-name-conflicts.patch
> 
> I don't know if it's a relevant precedent or not, but I noticed that
> fdwapi.h, amapi.h and tsmapi.h used the convention that function
> pointer types are named XXX_function, and then the members of a struct
> behaving as a kind of vtable are named XXX.

Good idea, and that also overlaps with some other stuff I have wanted to
tidy up in pg_dump, so I might get back to that later.

>> 0011-Add-missing-fields-in-struct-initializations.patch
> 
> I don't undestand why this is necessary, unless you're explicitly
> choosing to enable a warning like missing-field-initializers for C++
> but not for C.

I can't reproduce this anymore, so never mind.

> As for the commitfest entry: this thread discusses two different
> people's efforts to compile PostgreSQL as C++.  Joy Arulraj's github
> branch derives in some way from Peter Eisentraut's work, but I have
> provided feedback on Peter's patches, because (1) they were posted
> here in patch format and (2) there is a commitfest entry listening
> Peter as the author.  I think several of these patches are
> committable, and many obviously are not.  Heikki already set the CF
> item to 'Ready for Committer' based on an inspection of a few of the
> patches, but invited others to continue looking, so I did.

Yeah, I have committed a few of the patches now and I'll close the CF
entry now.  Thanks for your research.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers