| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: small cleanup in unicode_norm.c |
| Date: | 2020-12-08 09:44:55 |
| Message-ID: | X89LF9uw0BD0Z5ls@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Dec 07, 2020 at 03:24:56PM -0400, John Naylor wrote:
> We've had get_canonical_class() for a while as a backend-only function.
> There is some ad-hoc code elsewhere that implements the same logic in a
> couple places, so it makes sense for all sites to use this function
> instead, as in the attached.
Thanks John for caring about that. This is a nice simplification, and
it looks fine to me.
-static uint8
-get_canonical_class(pg_wchar ch)
-{
Two nits here. I would use "code" for the name of the argument for
consistency with get_code_entry(), and add a description at the top of
this helper routine (say a simple "get the combining class of given
code"). Anything else you can think of?
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2020-12-08 09:54:55 | Re: Logical archiving |
| Previous Message | vignesh C | 2020-12-08 09:38:11 | Re: Printing backtrace of postgres processes |