Re: cvs commit: apr/include apr_strings.h

[Wilfredo Sánchez <ws...@mit.edu>]

   I'm going to go ahead and rename the function, so the API is correct.

   How do I test for the size of a type with autoconf?

	-wsv


On Tuesday, July 30, 2002, at 11:38  AM, William A. Rowe, Jr. wrote:

> You aren't being anal... I believe we built this fn upside down.
>
> apr_int64 is a predictable type.  I'd suggest we should have added 
> apr_strtoi64()
> instead of strtoll (which isn't a portable type in the first place.).
>
> If apr_strtoll exists and longlong == 64 bits, then map that to 
> apr_strtoi64.
> If apr_strtoq exists and quad == 64 bits, then map that to 
> apr_strtoi64.
> If apr_strtol exists and long == 64 bits {64 bit cpu}, then map that 
> to apr_strtoi64.
>
> And if we have none of the above, use our own version of 
> apr_strtoi64().
>
> Now we have a useful and predictable type for large math.  If 
> apr_strtoll is
> really a 128 bit object on a given 64 bit architecture, using it would 
> be massive
> overkill :-)

Re: cvs commit: apr/include apr_strings.h

[Wilfredo Sánchez <ws...@mit.edu>]

   Yeah.  That's what I get for being slow.

	-wsv

On Thursday, August 15, 2002, at 11:11  AM, Ryan Bloom wrote:

> I believe that Will Rowe already changed the function name.  Also, you
> don't need to check the size, we already have the logic in APR's 
> configure
> script to do that.   :-)

Re: cvs commit: apr/include apr_strings.h

[Ryan Bloom <rb...@ntrnet.net>]

On Thu, 15 Aug 2002, [ISO-8859-1] Wilfredo S�nchez wrote:

>    I'm going to go ahead and rename the function, so the API is correct.
> 
>    How do I test for the size of a type with autoconf?

I believe that Will Rowe already changed the function name.  Also, you
don't need to check the size, we already have the logic in APR's configure
script to do that.   :-)

Ryan