[Top][All Lists]

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

Re: double inclusion guard

From: Eric Blake
Subject: Re: double inclusion guard
Date: Mon, 11 Oct 2010 19:54:53 -0600
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100921 Fedora/3.1.4-1.fc13 Mnenhy/0.8.3 Thunderbird/3.1.4

On 10/11/2010 07:39 PM, Gary V. Vaughan wrote:
There are only two options to make both cases behave the same -

   1. always hardcode the full path to the system header, even on machines
      with include_next support;

(1) is not viable. If a system header itself uses include_next, then we MUST include that header via system_include, or the nested include_next tries to include the same absolute name (itself) instead of its intended target. That's why we had to start using include_next throughout gnulib in the first place.

Eric Blake   address@hidden    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

reply via email to

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