From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 96919 invoked by alias); 10 Jan 2019 14:21:04 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 96909 invoked by uid 89); 10 Jan 2019 14:21:04 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:268 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 10 Jan 2019 14:21:03 +0000 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 4A4DBC0B2000 for ; Thu, 10 Jan 2019 14:21:02 +0000 (UTC) Received: from oldenburg2.str.redhat.com (ovpn-116-78.ams2.redhat.com [10.36.116.78]) by smtp.corp.redhat.com (Postfix) with ESMTPS id B89DE5D6AA for ; Thu, 10 Jan 2019 14:21:01 +0000 (UTC) From: Florian Weimer To: gcc@gcc.gnu.org Subject: __has_include__ is problematic Date: Thu, 10 Jan 2019 14:21:00 -0000 Message-ID: <87ef9kk304.fsf@oldenburg2.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes X-SW-Source: 2019-01/txt/msg00070.txt.bz2 Can we remove __has_include__? Its availability results in code which is needlessly non-portable because for some reason, people write __has_include__ instead of __has_include. (I don't think there is any difference.) Thanks, Florian