| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Jeff Davis" <list-pgsql-hackers(at)dynworks(dot)com>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | RE: A couple items on TODO |
| Date: | 2001-08-24 04:39:44 |
| Message-ID: | ECEHIKNFIMMECLEBJFIGCEKGCBAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> That's good information, now I have a better idea what I am
> looking for. I am
> using Source Navigator (good recommendation I got reading this
> list). I am
> basically just trying to find either variables that can be
> declared const, or
> inconsistancies (as Chris mentions).
>
> If anyone else has a clearer idea of what the intention of that
> todo item is,
> let me know.
I assume that since most of the times char * is passed to a function, it is
supposed to be unmodifiable. Putting the 'const' there enforces this -
thereby making PostgreSQL more robust against poxy programming.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Ford | 2001-08-24 05:32:22 | Re: Link to bug webpage |
| Previous Message | Tom Lane | 2001-08-24 04:22:51 | Re: Re: OLAP, Aggregates, and order of operations |