From: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
---|---|
To: | Neil Conway <neilc(at)samurai(dot)com> |
Cc: | Jim Nasby <decibel(at)decibel(dot)org>, Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Added the word TODO in comments |
Date: | 2007-01-11 00:58:48 |
Message-ID: | 20070111005848.GB12217@nasby.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jan 10, 2007 at 02:45:24PM -0500, Neil Conway wrote:
> On Wed, 3 Jan 2007 10:16:41 -0500
> Jim Nasby <decibel(at)decibel(dot)org> wrote:
> > Given that the TODO list is the official compilation of things that
> > need to get done, ISTM that anything warranting a TODO or XXX in the
> > code should probably be on the TODO list.
>
> There are a wide class of possible improvements / fixes that are too small to bother adding to the TODO list, but should still be recorded somewhere. Recording those improvements in the source code seems better than not recording them at all.
>
> Also, minor improvements to some part of the implementation are typically dependent on their context in the source code. Since TODO entries are often lacking in context as it is, I don't think trying to move everything to the TODO list would be wise.
Yeah, 'anything' is too strong... but I've certainly run across some
stuff that could go into the TODO. There's some things in there
questioning algorithm choices that probably won't ever get done unless
someone goes and researches them, for example.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
From | Date | Subject | |
---|---|---|---|
Next Message | Gavin Sherry | 2007-01-11 01:03:18 | Re: ideas for auto-processing patches |
Previous Message | Jim C. Nasby | 2007-01-11 00:44:28 | Re: ideas for auto-processing patches |