9front - general discussion about 9front
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] Re: removal of /lib/unicode
Date: Sun, 26 Mar 2023 16:52:19 +0200	[thread overview]
Message-ID: <27DA3049B946F86EEA8E40F8E12644FA@felloff.net> (raw)
In-Reply-To: <ZB+u9I79TA7yIV7y@alice>

IIRC, __func__ and #pragma once are for helping
some ape ports only.

I'd agree that these are kind of anti features...
These should never be used in native plan9 code.

On the other hand, if it makes the life easier
for porting ape stuff and ideally keeping stuff
upstreamed with the original authors i was not
against it.

The _Noreturn stuff is motivated by practical
problems.

It comes up often in the kernel which uses the
waserror() and error()/nexterror() handling logic.

Right now, we squelch the "used but not set"
warnings that it causes by initializing stuff
always. But this hides real bugs. 

As an experiment, i changed the error()/nexterror()
into macros wrapped in a infinite loop and removed
all these dummy initializers and actually found bugs
in the scsi driver in the kernel.

--
cinap

  parent reply	other threads:[~2023-03-26 14:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-26  2:23 [9front] " sl
2023-03-26  2:33 ` [9front] " Anthony Martin
2023-03-26  2:55   ` Jacob Moody
2023-03-26  3:05     ` sl
2023-03-26  3:25       ` Jacob Moody
2023-03-26  3:08     ` sl
2023-03-26  3:09   ` Sigrid Solveig Haflínudóttir
2023-03-26  4:37     ` Kurt H Maier
2023-03-26 13:26       ` qwx
2023-03-26 14:27         ` ori
2023-03-26 17:43           ` Jacob Moody
2023-03-26 14:52   ` cinap_lenrek [this message]
2023-03-26 19:27   ` hiro
2023-03-26 19:42     ` [9front] " Michael Misch
2023-03-26 20:46       ` hiro
2023-03-26 23:24       ` Kurt H Maier
2023-03-27 21:40       ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2023-03-27 22:15         ` hiro
2023-03-28  0:01           ` Sigrid Solveig Haflínudóttir

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=27DA3049B946F86EEA8E40F8E12644FA@felloff.net \
    --to=cinap_lenrek@felloff.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).