Content-Type: multipart/alternative;
 boundary="------------QGpWbnSbtIImofnM7t6UeGxF"
Message-ID: <e5167b2b-81ff-4ade-adcc-70814ce162c6@gmail.com>
Date: Sat, 19 Apr 2025 14:00:00 +0300
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Typos in the code and README
To: Michael Paquier <michael@paquier.xyz>
Cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>,
 Daniel Gustafsson <daniel@yesql.se>, Heikki Linnakangas <hlinnaka@iki.fi>,
 David Rowley <dgrowleyml@gmail.com>
References: <ae9f2fcb-4b24-5bb0-4240-efbbbd944ca1@gmail.com>
 <CAApHDvq7chgw8=7TU4-hLpQNw8e7qN9_oA4ew2UH05RCcihEDQ@mail.gmail.com>
 <c1d63754-cb85-2d8a-8409-bde2c4d2d04b@gmail.com>
 <CAApHDvoYsiFkZpjWeLGejibAXi=T3B70MzFr7z-1EiJ4pVX2hA@mail.gmail.com>
 <f7e514cf-2446-21f1-a5d2-8c089a6e2168@gmail.com>
 <ZtadkEfXje7zvOs4@paquier.xyz> <Ztaj7BkN4658OMxF@paquier.xyz>
 <5812a0b9-b0cf-4151-9a14-d9f00e4f2858@gmail.com>
 <CAApHDvrFg0xKRW6SgsFqnmSjbUThgX1U2F6KCoAKL9aRQ5_GdQ@mail.gmail.com>
 <9a7763ab-5252-429d-a943-b28941e0e28b@gmail.com>
 <aAN1LJ2T7BWssSSC@paquier.xyz>
Content-Language: en-US
From: Alexander Lakhin <exclusion@gmail.com>
In-Reply-To: <aAN1LJ2T7BWssSSC@paquier.xyz>
Archived-At: 
 <https://www.postgresql.org/message-id/e5167b2b-81ff-4ade-adcc-70814ce162c6%40gmail.com>
Precedence: bulk

This is a multi-part message in MIME format.
--------------QGpWbnSbtIImofnM7t6UeGxF
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hello Michael,

19.04.2025 13:04, Michael Paquier wrote:
> Good finds, Alexander, particularly for the set of function and
> variable names used in the comments that do not match with the
> reality.  I've checked all these, and they're good for me.

Thank you for your attention to this!

>> GIN_TUPLE_ -> GIN_TUPLE_H
> This one is interested.  It should be harmless in practice, but it
> could cause conflicts in theory.
> --

I've included it in the collection because of:
#ifndef GIN_TUPLE_
...
#endif                                                   /* GIN_TUPLE_H */

Best regards,
Alexander Lakhin
Neon (https://neon.tech)
--------------QGpWbnSbtIImofnM7t6UeGxF
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">Hello Michael,<br>
      <br>
      19.04.2025 13:04, Michael Paquier wrote:<span
      style="white-space: pre-wrap">
</span><br>
      <blockquote type="cite" cite="mid:aAN1LJ2T7BWssSSC@paquier.xyz">
        <pre class="moz-quote-pre" wrap="">Good finds, Alexander, particularly for the set of function and
variable names used in the comments that do not match with the
reality.  I've checked all these, and they're good for me.</pre>
      </blockquote>
      <br>
      Thank you for your attention to this!<br>
      <br>
      <span style="white-space: pre-wrap">
</span></div>
    <blockquote type="cite" cite="mid:aAN1LJ2T7BWssSSC@paquier.xyz">
      <blockquote type="cite">
        <pre wrap="" class="moz-quote-pre">GIN_TUPLE_ -&gt; GIN_TUPLE_H
</pre>
      </blockquote>
      <pre wrap="" class="moz-quote-pre">
This one is interested.  It should be harmless in practice, but it
could cause conflicts in theory.
--
</pre>
    </blockquote>
    <br>
    I've included it in the collection because of:<br>
    #ifndef GIN_TUPLE_<br>
    ...<br>
    #endif                                                   /*
    GIN_TUPLE_H */<br>
    <br>
    Best regards,<br>
    Alexander Lakhin<br>
    Neon (<a class="moz-txt-link-freetext" href="https://neon.tech">https://neon.tech</a>)<br>
  </body>
</html>

--------------QGpWbnSbtIImofnM7t6UeGxF--