[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: stdint module rewrite

From: Bruno Haible
Subject: Re: stdint module rewrite
Date: Tue, 13 Jun 2006 20:13:43 +0200
User-agent: KMail/1.9.1

Simon Josefsson wrote:
> Is there anything in this that would enable me to install a "stdint.h"
> file in $prefix

We could just need to change all
  #if HAVE_...
  #if @HAVE_...@
and use more substitutions in the creation of the stdint.h file.

But there are two problems:
- It's compiler dependent. On the same platform, a compiler can have
  uint32_t (or 'long long' etc.) and another can lack it.
- Even with the same compiler, the choice of the int_fastN_t types
  is arbitrary. Another person might create an <stdint.h> that
  defines them differently.

> (called something like "idn-int.h")

Why not call it "stdint.h"?

> Compare the AX_CREATE_STDINT_H macro:
> http://autoconf-archive.cryp.to/ax_create_stdint_h.html
> The essential difference is that the installed "idn-int.h" should work
> without assuming any config.h symbols, but instead rely on a
> combination of install-time "guesses" and CPP symbol checks to define
> the proper uint32_t types for the host and the compilers on that host.

Sorry, I cannot see how a CPP symbol test can tell whether uint32_t is
defined, if I don't know the compiler a priori. And #ifdefs of known
systems is not the right approach - not autoconfiguring, hard to maintain.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]