"Helen Borrie" <helebor@...> wrote in message

>
> How would you feel about documenting them "to the best of your knowledge"?
> I guess that's the only way we will get doc for them. I'd be quite

intrig-

> ued to include a topic in the Developer's Handbook entitled "The Hidden

API".

Lesson to newsgroup lurkers: Stay in the shadows.

I honestly don't know much about the API. Hey, that's why I use gpre. I
have never hand-coded an API call.

I noticed the undocumented functions when debugging my C programs. My
suspicion immediately fell on the gpre-generated stuff since I naturally
assume my own code to be bug-free. Of course, my humility was quickly
restored. But the exercise did force me to read the documentation.


Additional comment about gpre and the compilation process:
I have found it useful to eliminate the "#line" preprocessor commands that
are created to allow you to step through your .e file when debugging. You
are better off stepping through the .c file. Any knowledge I have about the
API is by doing this. Some debuggers do not identify the current line of
the .e correctly. (At least this is true for an old version of GNU gdb that
I have used on an old Sun Sparc 10... Dare I admit that I am still using
InterBase version 3.3H on this machine?)

Eric