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.0 required=5.0 tests=T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 23342 invoked from network); 26 Nov 2023 21:14:40 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 26 Nov 2023 21:14:40 -0000 Received: from sirjofri.de ([5.45.105.127]) by 9front; Sun Nov 26 16:11:32 -0500 2023 Received: from dummy.faircode.eu ([31.16.254.78]) by sirjofri.de; Sun Nov 26 22:11:30 +0100 2023 Date: Sun, 26 Nov 2023 22:11:22 +0100 (GMT+01:00) From: sirjofri To: 9front@9front.org Message-ID: <58ac8e46-4677-4dc9-a323-691698afd6ff@sirjofri.de> In-Reply-To: <7025e6e9-fca5-4648-aaea-a80260c35739@sirjofri.de> References: <904397cf-6c3f-46c4-9139-7f80823ec064@invalid.invalid> <4eeba9d4-12f2-4938-b0b3-5a8404653282@posixcafe.org> <8708ecaa-0b89-430d-ad06-2fd272680660@invalid.invalid> <7025e6e9-fca5-4648-aaea-a80260c35739@sirjofri.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Correlation-ID: <58ac8e46-4677-4dc9-a323-691698afd6ff@sirjofri.de> List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: storage GPU descriptor Subject: Re: [9front] [PATCH] Fix assert macro to not break on commas Reply-To: 9front@9front.org Precedence: bulk Hello, My 2 cents: I think having that change is unnecessary, at least. It only makes the code look nicer a little bit, and not having it makes the programmer recognize the "bug" pretty early. I'm pretty sure the compiler will just complain and the programmer adds another set of parentheses, and that's it. Furthermore, it makes it clear that assert is a macro and not a function, leading to further care when developing applications (which is the job of a programmer anyways; having assert as is and dealing with extra parentheses and compiler errors is too small to cry for a change of how things are currently, in my humble opinion). In addition to that, programmers should always be able to look at the functions they use. In this case it's obvious that assert is a macro. Furthermore, changing that macro makes 9front code that depends on that change incompatible with other 9 systems. Again, just a small thing that's easy to "fix", but it's incompatible. Changing assert to a function is something I don't like to see. I know it's just a fancy way to add the point of error to the error output, but I'd like to have that. Bug reports suck, and most users don't know about crash dumps etc, they just paste the error and in that case I'd like to have that extra bit of information, in the rare cases I don't capture the error earlier with proper output for the user. Also, it's a common functionality that's well known across environments and also programming languages. Last words that are important: It's not bad if a patch is rejected. Most of the time it's good, and also it's fine to do any changes in your local environment, or even distribute your own version of 9 with any changes you like. Gate keepers try their best to judge about the incoming patches to keep a minimum (or higher level) of quality. Of course it's also fine to argue, so keep up the good work on both sides. (Maybe I should've argued more about my factotum totp stuff, but I see the point: there's no application currently using it). sirjofri