solaris 2.5.1 still no good

[Andre Lucas]

> Please, please NO, don't do this. Instead, try to find snprintf, and
> iff that fails, search for __snprintf. This makes the search more OS
> independant, since you're searching for features, not OS characteristics.
> (I know, it's a pain. Welcome to autoconf.)

And on how many OSes is __snprintf going to be equivalent to snprintf?

This is what we were talking about before - detect features portably
where useful. If it's a 'platform x is fucked up' hack, treat it as
such. Then, at least it's clear what is going on. In this case, it's
unlikely that you'll find a platform y with the same problem. Why
clutter the code?

You can be over-generic. Look at SGML ;-)

I see your point, but I'm not sure it's always correct to put in generic
detection routines for everything. This is one silly little thing in
Solaris 2.5.x, let it stay there.

-Andre

-- 
Andre Lucas <andre.lucas at dial.pipex.com>
http://dspace.dial.pipex.com/andre.lucas/