From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings Newsgroups: gmane.emacs.devel Subject: Re: master 37889523278: Add new `swap` macro and use it Date: Fri, 12 Jan 2024 00:50:28 +0000 Message-ID: <4719da9bc2bbcffdb634@heytings.org> References: <170452579053.27998.16123231327386305897@vcs2.savannah.gnu.org> <20240106072311.28B8FC0034E@vcs2.savannah.gnu.org> <87plye9ahs.fsf@yahoo.com> <83o7dyua0d.fsf@gnu.org> <87le9297ei.fsf@yahoo.com> <87cyue92fx.fsf@yahoo.com> <877ckm8uzz.fsf@yahoo.com> <83v886sgtl.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15798"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Po Lu , stefankangas@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jan 12 01:51:16 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rO5lU-0003rS-7j for ged-emacs-devel@m.gmane-mx.org; Fri, 12 Jan 2024 01:51:16 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rO5ku-0004Zp-AY; Thu, 11 Jan 2024 19:50:40 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rO5kn-0004Yg-H0 for emacs-devel@gnu.org; Thu, 11 Jan 2024 19:50:34 -0500 Original-Received: from heytings.org ([95.142.160.155]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rO5kl-0006FI-9m; Thu, 11 Jan 2024 19:50:33 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1705020628; bh=PgBP/HrZe+2y1edosQR8a0i4e8BNAU4li5pC5lWqttY=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=LXwTmY/8CawxHhvhhUKq46ErJAMHOkgLd+IkdjkKteqBByPZFmm/JKeQngI+WV3zq 8yJKEDjYyPTXwDSCUsape0lC9WKA8s1U/aDy3nqC7AZpN8jspR3t0QuoLV2YYw/UdE QJWo2Xf06pgQ/sHsBcxGfKTse22Cw1F+hCtT463RgNw3a1/zg3xxRZat0r6xSPvdqh rKZxopRVNl1Fk9BH8D17YorkuvHObFuzwJKpnzTKG22AL0KC+Ljc9Dg4B40wKRPpJZ qqWEeGR/FWkVYip9v0OApjuD/Mc2gOx+CCAg4QaxRH9OVKIFzfqMrybSXjb2nK+sTQ bJ9NC+thEtjVg== In-Reply-To: <83v886sgtl.fsf@gnu.org> Received-SPF: pass client-ip=95.142.160.155; envelope-from=gregory@heytings.org; helo=heytings.org X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:314884 Archived-At: > > Did Stefan's change break some build? If so, which build became broken > and why? > FYI, Stefan's change did not break any build. "typeof" is supported by all compilers with which Emacs can be built, either with the keyword "typeof" or with the keyword "__typeof__". The only notable compiler that does not support "typeof" is MSVC, with which Emacs cannot be built. "typeof" will, moreover, officially become part of Standard C in a few weeks. In doing so, the standard committee did not add something new to the language, but instead codified existing practice. You can see this in the rationale for that change [1], which says: "Every implementation in existence since C89 has an implementation of typeof. Some compilers (GCC, Clang, EDG, tcc, and many, many more) expose this with the implementation extension typeof. [...] This feature is the most "existing practice"-iest feature to be proposed to the C Standard, possibly in the entire history of the C standard. The feature was also mentioned in an "extension round up" paper that went over the state of C Extensions in 2007. typeof was also considered an important extension during the discussion of that paper, but nobody brought forth the paper previously to make it a reality." [1] https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2619.htm