From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=0.2 required=5.0 tests=DKIM_ADSP_CUSTOM_MED,
	DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,T_SCC_BODY_TEXT_LINE
	autolearn=no autolearn_force=no version=3.4.4
Received: (qmail 28335 invoked from network); 26 Nov 2023 23:33:46 -0000
Received: from 9front.inri.net (168.235.81.73)
  by inbox.vuxu.org with ESMTPUTF8; 26 Nov 2023 23:33:46 -0000
Received: from mail-oo1-f52.google.com ([209.85.161.52]) by 9front; Sun Nov 26 18:31:03 -0500 2023
Received: by mail-oo1-f52.google.com with SMTP id 006d021491bc7-58d6b0df182so474588eaf.0
        for <9front@9front.org>; Sun, 26 Nov 2023 15:31:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20230601; t=1701041461; x=1701646261; darn=9front.org;
        h=content-transfer-encoding:in-reply-to:content-language:references
         :to:subject:user-agent:mime-version:date:message-id:from:from:to:cc
         :subject:date:message-id:reply-to;
        bh=w/z5dIPOhs3eSinipuOZ9enFCYMYnNZuGsJwSOi9+94=;
        b=ILkAWQ51K9ZP2RTC5VHUNGX481ASJ1CMI6rtyE8VMet5wELU8eX6PraCBkVlJwHA5D
         2VjNOc0irYtC2h4+BHtGXB5SrzWlHOhg1o6LVJoLfRjPRPyKwDKCaSkptQSo1CyjiKaY
         tFiMvP8a6fwNf+dURjh8k9HDCnooFGWbhyM12uXD9vnPGUW8XHak3D1koQMOJTlFZNYJ
         jr2bMx9WwLOwan2R8v8bhY/66BQzgWG31Bs9X1sSOAy/g3MY0qw23MimywNjM9xQdIMs
         +AjiujxsLK97SjD/3NWXHEDyrarQKN+1JwmdQfnjqBvg1TLEdYwtDjYB9p5K8o/F0vAm
         b4Cw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20230601; t=1701041461; x=1701646261;
        h=content-transfer-encoding:in-reply-to:content-language:references
         :to:subject:user-agent:mime-version:date:message-id:from
         :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
        bh=w/z5dIPOhs3eSinipuOZ9enFCYMYnNZuGsJwSOi9+94=;
        b=ffS93negkLV2cqYx+MPpbfXCKO8azTtyxa5eTkIBoDtcmMJXApU9JAQ18qEeEwxZrI
         BD+/SLnXp+DS0qTzWe04OUnwMqp6V7fUYg7vA3IRJDcidQ897eTXiwHwL37CpLdBwHQP
         Bm8RiQW9VtJ2MobqohCjsHrC0/1Qbhzwq6qGB+f+qDRNKtMVUAEvO2XOd0Nd6MgasNXI
         v/eHDCvFxgsCn9AaXGUK5OnQld4qLZVoDX6I65wpEqinoXd7FIt8RY4vVD+Gi2u8QOp1
         QgxcpFQPrASlpKBNvNiDFdLqRknXDWIKcHQAedX6ehYOMaGTNxZoi7lpU8sqYN6Dh6nG
         LZLw==
X-Gm-Message-State: AOJu0YzWO8fGQIdajcgPS8MntZz178tcGUgRUaM7xJ2b299qB69qbZD7
	tMEdUm7gMYAqxBrldHYbBVck3ucSWWukgQ==
X-Google-Smtp-Source: AGHT+IGLg7AhiF+ZZ0AdSTnkUn7n0MoXnbbict37rrSft2zBcw8p24kPsXPKn/x+4PWw5MYl/yVl7w==
X-Received: by 2002:a05:6820:1ca5:b0:589:d6c7:8573 with SMTP id ct37-20020a0568201ca500b00589d6c78573mr12136195oob.3.1701041460734;
        Sun, 26 Nov 2023 15:31:00 -0800 (PST)
Return-Path: <bluemanedhawk@gmail.com>
Received: from ?IPV6:2600:1700:e4c0:9ea0::5f6? ([2600:1700:e4c0:9ea0::5f6])
        by smtp.gmail.com with ESMTPSA id y9-20020a4aaa49000000b0058a0809ea25sm1314861oom.21.2023.11.26.15.31.00
        for <9front@9front.org>
        (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
        Sun, 26 Nov 2023 15:31:00 -0800 (PST)
From: Blue-Maned_Hawk <bluemanedhawk@gmail.com>
X-Google-Original-From: Blue-Maned_Hawk <bluemanedhawk@invalid.invalid>
Message-ID: <98891211-9bff-441d-a1f0-f1607a99bd70@invalid.invalid>
Date: Sun, 26 Nov 2023 18:30:59 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: 9front@9front.org
References: <8C8881A0ADB4FC714B2D0DBD3F1D1D7A@eigenstate.org>
Content-Language: en-US
In-Reply-To: <8C8881A0ADB4FC714B2D0DBD3F1D1D7A@eigenstate.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: virtual social ORM over ActivityPub rails-based package 
Subject: Re: [9front] [PATCH] Fix assert macro to not break on commas
Reply-To: 9front@9front.org
Precedence: bulk

On 11/26/23 17:52, ori@eigenstate.org wrote:
> Quoth Blue-Maned_Hawk <bluemanedhawk@gmail.com>:
>> What reason have y'all for avoiding macros?
> 
> Well, the fact that you need hacks like the one that started this
> thread, for one;

I don't see how it's a hack, but maybe i've just become numb to macro 
shenaniganry.

>                  what if you had  macro that took *two* arguments?
> 
> 	#define assert_msg(cond, msg) \
> 		...what here?
> 
> I don't see how you can avoid just saying "it's a macro, it's going
> to be weird, don't even try".
> 

Don't even try writing the macro or don't even try making it not weird? 
Because i can thing of a way to define such a thing:

	#define assert_msg(cond, msg) ((cond) ? (void)0 : (print(msg), exits(msg)))

and i don't think that that's a particularly weird way to do so.