[splint-discuss] Warnings when using g_assert

[spam_account at sympatico.ca]

On 11 Oct 2006, jeremy at cowgar.com wrote:
> When I use g_assert:

> g_assert (g_file_test ("config.ini", G_FILE_TEST_EXISTS) == 0);

> I get 3 warnings:

[snip]

> All three of these warnings are warnings I cannot do anything about
> w/ o altering glib code, which I obviously do not want. I can
...

Well, actually the best solution might be to modify the glib headers.
This is the solutions used for library headers.  Glib headers with
annotations would be most useful for debugging this code.

Sorry, I don't have such files and I don't know where they would
exist.  Perhaps a contrib to splint, glib (or some separate project)
would help.  A major problem is the amount of revisions of the glib
libraries.  I guess that the minor versions of Glib should have the
same API, so only one version (conditional) would be needed for the
major revisions.  Hiding implementation details from splinted code
would also be a plus...

I had started to do this with a Glib/GTK project.  However, I found
that the GCC vararg macros were problematic.  I tried to redefine the
macros as a function.  Eventually I got to the point where splint
wanted the function definitions, I believe it was failing due to
parsing errors.

I am interested in this and GTK as well.  Does anyone have pointers to
previous work done on this?  Any pointers on doing this with other
APIs?  If files are submitted to the list, would the get incorporated
into the CVS code at source forge?

Fwiw,
Bill Pringlemeir.