Hey again,
Here are a couple comments/questions on the current 3.2.0b4 code.
1. Any opposition to using GNU indent to pretty up the code a bit? I
don't care about the specific style options used. I'd like to make &
contribute bug fixes, but honestly some of the code is very hard to follow
because of formatting reasons.
See htdig/htdig.cc lines 583-626 for a mild example of
nested-ifs-gone-wild.
This may make security auditing a bit more enjoyable ;-)
2. It would be wonderful if there was a way to disable/enable different
compile options in the Makefiles or configure script. Use -O0 rather than
-O2, disable -g, etc. Pretty minor, and I've got it fixed for
me... anyone else interested?
I did it by mucking with the configure scripts. Change parameters
at the top of the files, run ./configure and viola.
3. Now that I've got my feet wet here, what exactly needs to be done to
sync-up the current mifluz code with what is in the htdig/db directory?
Are we picking and choosing or tossing the old stuff or what?
Thanks!
--
Neal Richter
Knowledgebase Developer
RightNow Technologies, Inc.
Customer Service for Every Web Site
_______________________________________________
htdig-dev mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/htdig-dev
