| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Patch to mark items as static or not used |
| Date: | 2006-07-15 04:40:54 |
| Message-ID: | 1152938455.5402.6.camel@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Sat, 2006-07-15 at 00:05 -0400, Tom Lane wrote:
> The fundamental problem with find_static is that it hasn't got a clue
> about likely future changes, nor about what we think external add-ons
> might want
We could annotate the source to indicate that some functions are
deliberately intended to be externally visible, but not referenced
within the source tree, and then teach find_static to grok that
annotation.
-Neil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | User Pgstudy | 2006-07-15 08:35:49 | fulldisjunction - fd: more CTID attribute consolidation. |
| Previous Message | Tom Lane | 2006-07-15 04:29:41 | Re: Patch to mark items as static or not used |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2006-07-15 08:41:39 | Re: Patch to mark items as static or not used |
| Previous Message | Tom Lane | 2006-07-15 04:29:41 | Re: Patch to mark items as static or not used |