Adam Thompson <[email protected]> writes: > Ok, that makes sense, though I'm surprised we can't check at configure time if > the version of tidy defines the symbols (and macros) we expect.
Sure, we can check for symbols. If the library defines tidyLibraryVersion, it is tidy-html5. If it doesn't, then it's some ancient version of tidy, so throw up our hands and refuse to proceed. What we won't know without building and running an executable is the version number of tidy-html5. Really, we don't know the actual version until runtime. I can build a program under version 5.1.x and then run it under 5.1.y, just fine, assuming the public API hasn't changed between x and y. Hence we should probably do both a compile-time and run-time check. Compile-time tells us whether we have tidy-html5 or tidy, run0-time tells us more specifically which version of tidy-html5 we have. -- Chris _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
