= wx code checker =

I see the wxWidgets API Documention not only as a programming aide, but rather 
as a Specification to which all implementations (different ports, different
builds and build configurations) should adhere.

Now I created the XML version of the wxWidgets docs, I figured i could use that
to check whether the implementations really implement all the methods that are
promised by the documentation.

== gathering info ==

=== nm and objdump ===

I have considered taking the symbol information from the library as a basis,
but it seems neither nm nor objdump can produce the return types of the symbols.
`nm -C /usr/lib/libwx_gtk-2.4.a' was close but not quite.

=== gcc and ctags ===

Now i think i might be able to combine gcc -E (`only preprocess') and ctags.

  gcc -E `wx-config --cxxflags` include.cpp > preprocessed.cpp
  ctags preprocessed.cpp

This is a bit tricky though:
* all preprocessing has been done, but the specification may still have 
  preprocessing directives
* ctags files have the following fields:
  tag name, filename, ex-command, extension fields

=== linking ===

(currently the `main' approach)

another approach would be to try and create a .cpp file that calls all 
documented methods, and simply tries to compile and link that file. If that 
succeeds, the result will not be a useful executable, but it will tell us that
all documented methods are indeed implemented.

=== doxygen ===

Maybe doxygen could provide the information needed.