[TUHS] I can't drive 55: "GOTO considered harmful" 55thanniversary

Steffen Nurpmeso steffen at sdaoden.eu
Wed Mar 15 05:54:36 AEST 2023


Dave Horsfall wrote in
 <alpine.BSF.2.21.9999.2303131331350.67613 at aneurin.horsfall.org>:
 |[ 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 <alpine.BSF.2.21.9999.2303131331350.67613 at aneurin.horsfall.org>

--steffen
|
|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)


More information about the TUHS mailing list