From: Steve Simon <steve@quintile.net>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] Fix assert macro to not break on commas
Date: Sat, 25 Nov 2023 22:47:53 +0000 [thread overview]
Message-ID: <449F794D-F393-4DF8-B182-B3C8C48EE516@quintile.net> (raw)
In-Reply-To: <CAEoi9W5PMU4wnA=8LgD=hq+JYGftsA83gjSgTFysgJxnD7axjQ@mail.gmail.com>
iyou are quite right, assert() is part of the standard plan9 library, not the language.
however i honestly doubt this has caused a significant number of issues for plan9 programmers. i suggest it is just not worth changing.
i liked the general sentiment of kurt’s comments, but perhaps i am just a curmudgeon after all.
-Steve
> On 25 Nov 2023, at 8:40 pm, Dan Cross <crossd@gmail.com> wrote:
>
> On Sat, Nov 25, 2023, 3:12 PM Steve Simon <steve@quintile.net> wrote:
>> i strongly agree with kurt.
>>
>> this should go into the fortunes file imho.
>>
>>> Making the language dumber because someone wants to do something stupid
>>> is the wrong plan.
>
> The statement is factually wrong. The language is already the way that
> it is, and this change just makes a macro useful in more contexts;
> that's not "changing the language" unless someone is adding the
> variadic macro stuff to the compilers to do it.
>
> - Dan C.
next prev parent reply other threads:[~2023-11-25 22:51 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 23:11 Blue-Maned_Hawk
2023-11-23 4:20 ` Jacob Moody
2023-11-25 0:27 ` Blue-Maned_Hawk
2023-11-25 1:09 ` Jacob Moody
2023-11-25 4:34 ` ori
2023-11-25 12:09 ` Blue-Maned_Hawk
2023-11-25 18:46 ` Kurt H Maier
2023-11-25 20:06 ` Steve Simon
2023-11-25 20:39 ` Dan Cross
2023-11-25 22:47 ` Steve Simon [this message]
2023-11-26 2:22 ` Kurt H Maier
2023-11-26 17:31 ` Blue-Maned_Hawk
2023-11-26 18:13 ` ori
2023-11-26 22:39 ` Blue-Maned_Hawk
2023-11-26 22:52 ` ori
2023-11-26 23:30 ` Blue-Maned_Hawk
2023-11-27 0:00 ` ori
2023-11-27 11:20 ` Blue-Maned_Hawk
2023-11-27 15:38 ` ori
2023-11-27 15:59 ` Dan Cross
2023-11-27 22:21 ` Blue-Maned_Hawk
2023-11-27 23:59 ` ori
2023-11-28 0:30 ` Blue-Maned_Hawk
2023-11-28 0:34 ` ori
2023-11-29 9:14 ` Blue-Maned_Hawk
2023-11-26 19:58 ` Kurt H Maier
2023-11-26 22:37 ` Blue-Maned_Hawk
2023-11-25 4:49 ` ori
2023-11-26 18:59 ` Amavect
[not found] ` <7025e6e9-fca5-4648-aaea-a80260c35739@sirjofri.de>
2023-11-26 21:11 ` sirjofri
2023-11-26 22:41 ` Blue-Maned_Hawk
2023-11-27 15:44 ` Amavect
2023-11-26 22:36 ` ori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=449F794D-F393-4DF8-B182-B3C8C48EE516@quintile.net \
--to=steve@quintile.net \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).