Re: [preview-latex-devel] dvipng 1.1 in teTeX 2.96.4

Harald Koenig wrote:
> 1)
> OSF1 v4.0 and SunOS 5.5.1 don't have neither stdint.h nor inttypes.h.
> 
> I've added tests in configure for stdint.h and inttypes.h
> and some fallback code if neither file is available.

This is also true for VC++, used for MIKTeX. *But* I'd expect something like
  font.c:89: error: `uint64_t' undeclared (first use in this function)
So I would like to add (the equivalent of)

typedef long long                int64_t;
typedef unsigned long long      uint64_t;

Is this good, or do I need to dig deeper? In MIKTeX, I've been told to
use __int64 (Christian?)

Also, from autoconf's docs:
----------------------------
`inttypes.h' vs. `stdint.h'
     Paul Eggert notes that: ISO C 1999 says that `inttypes.h' includes
     `stdint.h', so there's no need to include `stdint.h' separately in
     a standard environment.  Many implementations have `inttypes.h'
     but not `stdint.h' (e.g., Solaris 7), but I don't know of any
     implementation that has `stdint.h' but not `inttypes.h'.  Nor do I
     know of any free software that includes `stdint.h'; `stdint.h'
     seems to be a creation of the committee.
----------------------------

Is this correct? In that case I'll just skip the stdint.h include.

> 2)
> OSF1 v4.0 doesn't really have snprintf() (it's hidden in libdb.a), 
> SunOS 5.5.1 doesn't have snprintf() at all.

It isn't there in VC++ either. OK, added. Will be in dvipng 1.2
/JÅ


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com