Neil Conway wrote:
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.
I thought of that, but what if one gets missed? Is the tool worth the
hassle?
cheers
andrew
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
