From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 19 13:16:09 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CF6E3106566C for ; Tue, 19 Jul 2011 13:16:09 +0000 (UTC) (envelope-from rmh.aybabtu@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 982D88FC1A for ; Tue, 19 Jul 2011 13:16:09 +0000 (UTC) Received: by iwr19 with SMTP id 19so4942622iwr.13 for ; Tue, 19 Jul 2011 06:16:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=HKBPmifs5I3Gm/8x+imWywjrGUlv0Uaz1ELIrHB5bMA=; b=UGC7m77aJ3yGRzqTIpLEUx95kkdvQxwpTFNXZ/cMXe74NH1RJYCiV3o5lX3+yWEPLJ VPk4aKRMnLQj3dlt0uqwsVgFk98Am3ppA/A9WENqZg25WOy8q+Rb6G6Gyd44ZLiNDSFl pQmb3h1bdOaZBaAXhZZgQowd2CLu1/SmhefWk= MIME-Version: 1.0 Received: by 10.42.100.72 with SMTP id z8mr8631894icn.448.1311081368782; Tue, 19 Jul 2011 06:16:08 -0700 (PDT) Sender: rmh.aybabtu@gmail.com Received: by 10.42.224.70 with HTTP; Tue, 19 Jul 2011 06:16:08 -0700 (PDT) In-Reply-To: <20110705134447.493e0bf1@kan.dnsalias.net> References: <20110702193724.5c55a6c9@kan.dnsalias.net> <20110703103925.0bdf255a@kan.dnsalias.net> <20110705134447.493e0bf1@kan.dnsalias.net> Date: Tue, 19 Jul 2011 15:16:08 +0200 X-Google-Sender-Auth: QsGrsSgxjo9nRtJAt1_uDdCrtXs Message-ID: From: Robert Millan To: Alexander Kabaev Content-Type: text/plain; charset=UTF-8 Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] __FreeBSD_kernel__ X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2011 13:16:09 -0000 2011/7/5 Alexander Kabaev : > The slow way would be the right way if you were inclined to really take > it. Once old releases of tools that can be broken by the new macro > use are long and forgotten we can start on relying on said macro, but > not before. Given that your main concern is backward compatibility, is it an inconvenient to you if 3rd party compilers such as GCC or Clang begin adding this macro? If you're still not comfortable with this macro by the time you want to import one of those, it just takes a minute to remove it. The purpose of this, of course, is to start the clock count (as you've put it: "Once old releases of tools that can be broken by the new macro use are long and forgotten we can start on relying on said macro"). -- Robert Millan