RE: squid-2.4 release ?

Not really.
For consistency with NTLMSSP (which I didn't write) I used
in32_t and u_int32_t.
That could (and in fact I believe should) be changed.

-- 
	/kinkie 
> -----Original Message-----
> From: Robert Collins [mailto:robert.collins@itdomain.com.au]
> Sent: Tuesday, January 09, 2001 10:03 AM
> To: Adrian Chadd; Chemolli Francesco (USI)
> Cc: squid-dev@squid-cache.org
> Subject: Re: squid-2.4 release ?
> 
> 
> There have been two reports recently of problems with the 
> uintx_t types on solaris 2.8
> 
> See the squid-users list...
> ----- Original Message ----- 
> From: "Adrian Chadd" <adrian@creative.net.au>
> To: "Chemolli Francesco (USI)" <ChemolliF@GruppoCredit.it>
> Cc: <squid-dev@squid-cache.org>
> Sent: Tuesday, January 09, 2001 7:39 PM
> Subject: Re: squid-2.4 release ?
> 
> 
> > On Tue, Jan 09, 2001, Chemolli Francesco (USI) wrote:
> > > Which reminds me I should write the configure parts to
> > > define known-width types.
> > > Before I do so, I believe we should agree on such
> > > types' names.
> > > 
> > > My suggestion is:
> > > [u]int[size]_t
> > > 
> > > where size can be on e of 8,16,32
> > > 
> > > Do we need 64 bits things anywhere? (keep in mind
> > > those MIGHT not be available on some platforms).
> > > 
> > > Notice: those types MIGHT be defined somewhere else
> > > (for instance on my RH Linux they're defined in <stdint.h>
> > > which is included by other headers. Of course the configure
> > > tests should cover all bases.
> > 
> > Well, these should be defined in sys/types.h . Have you tried
> > looking at this?
> > 
> > 
> > I've found it on
> >   * solaris 2.7
> >   * freebsd-stable
> >   * freebsd-current
> >   * linux
> >   * OSF/1 5.1
> > 
> > I don't know about older platforms however, and that would 
> be architecture
> > and compiler dependant.
> > 
> > -- 
> > Adrian Chadd "Sex Change: a simple job of inside
> > <adrian@creative.net.au>   to outside plumbing."
> >     - Some random movie
> > 
>