httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject Re: and now back to snprintf (fwd)
Date Thu, 16 Jan 1997 03:44:20 GMT
Marc Slemko wrote:
> 
> 
> Shucks.  Guess need to stop disagreeing then.  I was under the impression
> that you were commenting on #2.  
> 
> So do:
> 	- if we know the OS has snprintf use it
> 	- otherwise use ap_snprintf
> 	- if it fails, have 'em come crying to us to make them feel
> 	  better and hopefully fix the problem.
> 
> I would like to avoid breaking everything if our ap_snprintf doesn't
> compile, but I don't think it is worth wasting much effort on because
> it would be a short term thing anyway.  So how about we say bye-bye
> entirely to option #3?  The first try at ap_snprintf had pretty good
> results WRT compiling and working.

+1

> 
> You get any further on the 64-bit stuff?  I am soon going to be to the
> point where the patches are done, so if you don't have an idea of
> where you are going with that I will start looking harder.
> 

I'm close... By access to a 64 bit machine has been flakey lately
so.... :/


-- 
====================================================================
      Jim Jagielski            |       jaguNET Access Services
     jim@jaguNET.com           |       http://www.jaguNET.com/
                  "Not the Craw... the CRAW!"

Mime
View raw message