From nobody Mon Nov 20 04:24:15 2023
X-Original-To: freebsd-arch@mlmmj.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
	by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SYZCQ49phz51s4V
	for <freebsd-arch@mlmmj.nyi.freebsd.org>; Mon, 20 Nov 2023 04:24:18 +0000 (UTC)
	(envelope-from fuz@fuz.su)
Received: from fuz.su (fuz.su [IPv6:2001:41d0:8:e508::1])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256
	 client-signature RSA-PSS (2048 bits) client-digest SHA256)
	(Client CN "fuz.su", Issuer "fuz.su" (not verified))
	by mx1.freebsd.org (Postfix) with ESMTPS id 4SYZCQ2sQxz4Y7F;
	Mon, 20 Nov 2023 04:24:18 +0000 (UTC)
	(envelope-from fuz@fuz.su)
Authentication-Results: mx1.freebsd.org;
	none
Received: from fuz.su (localhost [127.0.0.1])
	by fuz.su (8.17.1/8.17.1) with ESMTPS id 3AK4OGK0098314
	(version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO);
	Mon, 20 Nov 2023 05:24:16 +0100 (CET)
	(envelope-from fuz@fuz.su)
Received: (from fuz@localhost)
	by fuz.su (8.17.1/8.17.1/Submit) id 3AK4OF6c098313;
	Mon, 20 Nov 2023 05:24:15 +0100 (CET)
	(envelope-from fuz)
Date: Mon, 20 Nov 2023 05:24:15 +0100
From: Robert Clausecker <fuz@freebsd.org>
To: Jessica Clarke <jrtc27@freebsd.org>
Cc: Robert Clausecker <fuz@freebsd.org>, Warner Losh <imp@bsdimp.com>,
        freebsd-arch@freebsd.org
Subject: Re: Some K&R support to be removed from sys/cdefs.h
Message-ID: <ZVrfb856IA6nH0T1@fuz.su>
References: <CANCZdfpZNaC6vqaLkOk2hbtFpmi6oLEVWNQgK2RTVofsJr+e9A@mail.gmail.com>
 <ZVrdSxgDZdepRZeL@fuz.su>
 <50B3506F-B0BF-4695-A0B5-CFDB918D6DAB@freebsd.org>
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-arch
List-Help: <mailto:freebsd-arch+help@freebsd.org>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Subscribe: <mailto:freebsd-arch+subscribe@freebsd.org>
List-Unsubscribe: <mailto:freebsd-arch+unsubscribe@freebsd.org>
Sender: owner-freebsd-arch@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <50B3506F-B0BF-4695-A0B5-CFDB918D6DAB@freebsd.org>
X-Spamd-Bar: ----
X-Rspamd-Pre-Result: action=no action;
	module=replies;
	Message is reply to one we originated
X-Spamd-Result: default: False [-4.00 / 15.00];
	REPLY(-4.00)[];
	ASN(0.00)[asn:16276, ipnet:2001:41d0::/32, country:FR]
X-Rspamd-Queue-Id: 4SYZCQ2sQxz4Y7F

Hi Jessica,

Am Mon, Nov 20, 2023 at 04:19:11AM +0000 schrieb Jessica Clarke:
> On 20 Nov 2023, at 04:15, Robert Clausecker <fuz@freebsd.org> wrote:
> > 
> > Hi Warner,
> > 
> > __STRING and __CONCAT are still needed with ANSI C to change evaluation order.
> > For example, I recently used __CONCAT in lib/libc/amd64/amd64_archlevel.h to
> > build function names from pieces.  ## cannot be used as that doesn't work if
> > the argument passed to the macro is in turn a macro.  Similar things apply to
> > __STRING.
> 
> You mean __XSTRING; __CONCAT is to __XSTRING what __CONCAT1 is to __STRING,
> confusingly (though __CONCAT1 is unused except for implementing __CONCAT).

It could be that __XSTRING is the one for stringification.  I didn't have a need
for it so far if I remember correctly.

Yours,
Robert Clausecker

-- 
()  ascii ribbon campaign - for an 8-bit clean world 
/\  - against html email  - against proprietary attachments