Re: 64-bit fun with cache.c

> 4 GB ought to be enough for everybody, eh?

 No, I did not say that.
 What I meant is: profile. Don't do things blindly, just for the heck
of it. There are costs, and risks, associated to every change to the
code; before changing anything, make sure the benefits outweigh the
costs.
 You may call me conservative, but as far as djbware is concerned,
I've found the conservative approach to work best.


> If it's not too ugly, I'm not going to worry about it.

 Well, I am going to worry about it.
 You sound like a child who's found a new toy to play with, and that
toy happens to be djbdns. As long as you're hacking it on your own
and experimenting on your own private machines, more power to you,
that's what free software is for. But as soon as you're packaging
and distributing the results of your experiments, you have a
responsibility: to ensure the quality of what you're distributing.

 You started with autoconfizing a working build system for no other
reason than "I want to be able to build djbdns the same way as other
packages". You're continuing with "I can use uint64 everywhere, the
compiler will optimize it for me", when I had just given you the
answer to a question you asked, which was "how can I detect native
64-bit platforms ?"

 I know it's not what you want to hear, and I'm sorry to be harsh,
but you sound careless - way more careless than I'm comfortable with
where djbware is concerned. djbware is quality software, it needs
to be adopted more widely, but it has suffered from bad publicity
for a long time, and most people are reluctant to use it. The main
advantage it has is *quality of code* : djbdns is probably the
*least* buggy DNS software suite that was ever written. And now that
it is in the public domain, it needs to remain that way.

 Your approach sounds likely to introduce bugs into the code. This
is not a good thing for djbdns' reputation, and ultimately, this is
not a good thing for the users either. Please don't do this. Please
be more careful with changes you make to code you're going to
package and distribute.

 We don't need more GNU-quality software.

-- 
 Laurent