Re: problem with #include_next<stdint.h> in /usr/include/idn-int.h

help-libidn

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

Re: problem with #include_next<stdint.h> in /usr/include/idn-int.h

From:	Paul Eggert
Subject:	Re: problem with #include_next<stdint.h> in /usr/include/idn-int.h
Date:	Wed, 20 Jun 2007 09:53:00 -0700
User-agent:	Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)

Simon Josefsson <address@hidden> writes:

> Perhaps #include_next is simply not reliable to use in generated *.h
> files?

We need to handle it better, yes.  I'll look into it.

[Prev in Thread]

Current Thread

[Next in Thread]

problem with #include_next<stdint.h> in /usr/include/idn-int.h, Remko van der Vossen, 2007/06/20
- Re: problem with #include_next<stdint.h> in /usr/include/idn-int.h, Simon Josefsson, 2007/06/20
  - Re: problem with #include_next<stdint.h> in /usr/include/idn-int.h, Paul Eggert <=
  - Re: problem with #include_next<stdint.h> in /usr/include/idn-int.h, Bruno Haible, 2007/06/21
    - proposed changes to fchdir, iconv_open, locale, netinet_in, sys_select, sys_socket, sysexits, Paul Eggert, 2007/06/21
    - Re: proposed changes to fchdir, iconv_open, locale, netinet_in, sys_select, sys_socket, sysexits, Bruno Haible, 2007/06/21
    - Re: proposed changes to fchdir, iconv_open, locale, netinet_in, sys_select, sys_socket, sysexits, Paul Eggert, 2007/06/21
    - Re: problem with #include_next<stdint.h> in /usr/include/idn-int.h, Paul Eggert, 2007/06/21

Prev by Date: Re: problem with #include_next<stdint.h> in /usr/include/idn-int.h
Next by Date: proposed changes to fchdir, iconv_open, locale, netinet_in, sys_select, sys_socket, sysexits
Previous by thread: Re: problem with #include_next<stdint.h> in /usr/include/idn-int.h
Next by thread: Re: problem with #include_next<stdint.h> in /usr/include/idn-int.h
Index(es):
- Date
- Thread