Re: Change definitions of bitmap flags to bit-shifting style

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Change definitions of bitmap flags to bit-shifting style
Date: 2020-12-05 18:03:43
Message-ID: 2303329.1607191423@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> writes:
> The attached patch changes definitions like
> #define FOO 0x01
> #define BAR 0x02
> to
> #define FOO (1 << 0)
> #define BAR (1 << 1)
> etc.

> Both styles are currently in use, but the latter style seems more
> readable and easier to update.

FWIW, personally I'd vote for doing the exact opposite. When you are
debugging and examining the contents of a bitmask variable, it's easier to
correlate a value like "0x03" with definitions made in the former style.
Or at least I think so; maybe others see it differently.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2020-12-05 18:40:33 Re: [PATCH] Keeps tracking the uniqueness with UniqueKey
Previous Message Dmitry Dolgov 2020-12-05 17:55:42 Re: Index Skip Scan (new UniqueKeys)