'for every' and 'for any'

[Andrae Muys]

Oren Tirosh <oren-py-l at hishome.net> wrote in message news:<mailman.1022658469.27441.python-list at python.org>...
> I don't have a personal utility library. It's on purpose. I don't have
> personalized key bindings. I try to avoid customization.  Customization is
> a big part of what makes one programmer's code difficult to maintain by
> another programmer, what makes on programmers's workstation unusable by 
> another and makes combining code from several sources difficult.
> 
> Just one little example: I hate it when different parts of the code use 
> their own customized constants for ints from specific sizes.  Is it 
> u_int32_t, uint32_t or guint32? I hate it when a big project starts and the 
> programmers all start to waste their time on writing a yet another library 
> with all this stuff.
> 

Now I just don't understand how this position can possibly make sense?
 C dosn't have any 32-bit int types standardised, so what do _you_ use
when you need one?  Please don't tell me you don't use int, or I'll
have to hunt you down and put you out of your misery ;).  I personally
have absolutely no problem with any of the 3 examples you gave above:

sometimes-the-word-length-is-important-ly yours 
Andrae Muys