The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Steffen Nurpmeso <>
To: Dave Horsfall <>
Cc: The Eunuchs Hysterical Society <>
Subject: [TUHS] Re: I can't drive 55: "GOTO considered harmful" 55thanniversary
Date: Tue, 14 Mar 2023 20:54:36 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Dave Horsfall wrote in
 |[ Followups to COFF, as this is rapidly becoming a Unix tutorial ]
 |On Sun, 12 Mar 2023, Steffen Nurpmeso wrote:
 |> Even on a x86(-32) i have gnashed with my teeth.  And that with
 |You can read X86 assembler?  I can only do that after a few stiff

Unfortunately i stopped my ambitions (nasm was non-portable but
fun).  I never stepped to ARM, i hate that, i read according Net
and FreeBSD commits with lots of interest.  Many years ago there
was a thrilling commit series for string and memory ops on NetBSD
that i sometimes still speak of ... Matt Thomas i think it was.
("Thrilling" it was for me; by then.)

 |drinks...  I did buy the book (in order to debug a floating bug defect
 |in the optimiser -- hey, let's optimise this instruction right out! -- and

But floating-point i run away.

 |I've never trusted optimisers since).
 |Cue the saying about it being impossible to design a foolproof system.
 |-- Dave, the iconoclast

"Dawn Of The Iconoclast"; Lisa Gerrard is also an Aussie and
nuclear she is, isn't she.  (Shown with unforgotten Klaus Schulze
at the Loreley -- since most of the UNIX beards are surely some
kind of long haired beauties this could even go to TUHS.)

Yeah, signals, no.  Problems anywhere.  But i have a
  command PKILL_TMUX "pkill -CONT tmux"
in my ~/.cwmrc (when Linux sends ^Z to the wrong for whatever
reason), and enough ptys to go to when ogg123 again gets an
interruption wrong and hangs deadly, only killable via -KILL.
I think setting a flag plus EINTR is a way, but ERESTART is not
handable if you sit on something blocking but have to act upon the
signal; message passing -- if you do have an event loop based
program then this is nice; then again i woke up with horrors for
the (first) Linux thread library (i have looked in) over twenty
years ago, and they used a worker and serialization via such as
a regular thing; also owed to Butenhof's POSIX thread design of
course, which is too "free" in my eyes (i'd rather have
a dedicated main thread plus workers); just like C++ exceptions (i
saw software which "throws char*").

 --End of <>

|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

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

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-09 23:01 [TUHS] I can't drive 55: "GOTO considered harmful" 55th anniversary Steffen Nurpmeso
2023-03-09 23:18 ` [TUHS] " segaloco via TUHS
2023-03-09 23:21   ` Warner Losh
2023-03-09 23:31     ` Luther Johnson
2023-03-09 23:44       ` josh
2023-03-09 23:54       ` Warner Losh
2023-03-10  0:54         ` segaloco via TUHS
2023-03-10  1:08           ` Warner Losh
2023-03-10 10:08             ` Ralph Corderoy
2023-03-10 11:37               ` arnold
2023-03-10 11:56                 ` Ralph Corderoy
2023-03-10 11:59                   ` arnold
2023-03-10 12:11                     ` Ralph Corderoy
2023-03-10  6:15     ` Dave Horsfall
2023-03-10 16:55       ` Steffen Nurpmeso
2023-03-10 17:02         ` Bakul Shah
2023-03-12 20:47         ` Dave Horsfall
2023-03-12 21:50           ` Warner Losh
2023-03-12 22:27             ` Steffen Nurpmeso
2023-03-13  3:09               ` [TUHS] Re: I can't drive 55: "GOTO considered harmful" 55thanniversary Dave Horsfall
2023-03-14 19:54                 ` Steffen Nurpmeso [this message]
2023-03-10  1:31   ` [TUHS] Re: I can't drive 55: "GOTO considered harmful" 55th anniversary Rich Morin

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).