9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Kurt H Maier <khm@sciops.net>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] Fix assert macro to not break on commas
Date: Sat, 25 Nov 2023 18:22:55 -0800	[thread overview]
Message-ID: <ZWKr_zDsVVVddLrz@wopr> (raw)
In-Reply-To: <CAEoi9W5PMU4wnA=8LgD=hq+JYGftsA83gjSgTFysgJxnD7axjQ@mail.gmail.com>

On Sat, Nov 25, 2023 at 03:39:57PM -0500, Dan Cross 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.

The statement is not 'factually wrong' according to this argument; it
would instead be irrelevant, which it very well might be.

I suppose this is an opportunity to be pedantic about where the line is
drawn between a language, the implementation of that language, and the
detritus that habitually grows around a language, but it's all
irrelevant, because I don't care.

Doing fancy shit with macros in places where you have the opportunity 
not to do fancy shit with macros is bad.  I know this goes against many
currently-popular dogmas, where we all love to build abstraction castles
into the sky, but there is a difference between making something
convenient and building yet another indirection layer some poor bastard
later has to unravel in order to understand what is happening.

This macro has been fine as it sits for a lot of use.  We have no
convincing demonstrations that this change will enable anything useful
that was not previously possible.  We have no arguments that it will
even make anything more convenient which isn't justifiably difficult at
the moment.  

Finally,I'm doubly suspicious of it because the submitter has a history 
of asshattery and obnoxious behavior in the irc channel.  If this patch
came from some drive-by rando I'd be less opposed to it; instead it
comes from someone with a recent history of willfully refusing to
communicate clearly, and is defended by someone who chose to support it
based on sophistry instead of any clear technical grounds.

I'm not gonna stop anyone from merging anything.  I don't have a dog in
this fight.  But the reasons given suck and further deponent sayeth
trash.

khm

  parent reply	other threads:[~2023-11-26  2:27 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
2023-11-26  2:22               ` Kurt H Maier [this message]
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=ZWKr_zDsVVVddLrz@wopr \
    --to=khm@sciops.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).