From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | "Bruce Momjian" <bruce(at)momjian(dot)us>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Macros for time magic values |
Date: | 2011-03-14 16:01:36 |
Message-ID: | 10615.1300118496@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> My first reaction that this change was about a net wash in
> readability for me -- in a couple places it might save me a few
> moments thinking about what the number was meant to represent,
> balanced against following the ctag back to the #define to see what
> number was used for things like DAYS_PER_YEAR or DAYS_PER_MONTH.
> Comments like the one Bruce cites above seem like they tip the
> scales in favor of the patch for me. Having a place to document
> the choice of questionable values seems like it's better than just
> using the questionable values "bare" all over the place. Neither
> omission of the justification nor repeating it seems better.
Another advantage of the macros is that it makes it a lot easier to grep
to see where a questionable value is being used. Originally I'd felt
that wrapping those bogus numbers in macros was a bad idea, but the
documentation and searching advantages are enough to make me think it's
all right.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2011-03-14 16:08:13 | Re: GSoC 2011 - Mentors? Projects? |
Previous Message | Kevin Grittner | 2011-03-14 15:56:31 | Re: Macros for time magic values |