>> You see, LOGGING_MAX is the mechanism that causes the logging instructions
>> that are not enabled to be compiled out -- in that way, the values that
>> are printed are not even evaluated. Setting LOGGING_MAX to 0xFF causes
>> all of this code to be included, and Polipo's performance to be reduced.
> Not, I suspect, to any detectable degree, on modern hardware.
While that's not unlikely, it's quite besides the point. Polipo is
a horribly over-optimised piece of software, and I happen to like it
this way.
Think of Polipo as a political statement against Pike's rules of program
optimization [1].
>> Oh, that's another issue -- I don't want to make it easy for stupid
>> admins to spy on their users.
> Now *that's* a good reason :)
Heh.
Juliusz
[1] Rule 1: Don't do it.
Rule 2: Don't do it yet.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Polipo-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/polipo-users
