This is in unused code. I have a patch that addresses this by adding some stuff to configure.ac. The reason I haven't committed is that it seems over-the-top to prevent a warning in dead code; I wonder whether we should just remove the function instead.
If it's unused, it should be removed. Period. Debugging stuff gets a pass, but only in the short-term.
One of the first things I do when debugging a problem with layout is to turn on this bit of code, so it's still very useful (and will become more so when I start adding features to flowtext again after the release). It is still debugging code, however, and will not be callable in the final build. How do you guys deal with such things? I have read of a disapproval of #iffing out code, and putting it in a separate source file might cause me to accidentally check in a change to the makefile. Also, I do sort of have a vision of using it in some sort of automated regression test. How does that affect your answer?
As for the matter of the warning, the #ifdef was never really meant to be serious, it was just a way to get the file to build again on my machine. Now that win32 is upgraded to gtk2.6, is there anybody left who still does not have that constant?
Richard.