The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Steve <>
Subject: [TUHS] GOTO etc.
Date: Sun, 19 Mar 2023 11:41:10 -0400	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1: Type: text/plain, Size: 1495 bytes --]

After some digging - in the Algol68C compiler we used the names setmp and longjmp for the code 
generation routines to implement non local goto.  So as you say they were not part of the Algol68 
language. Steve
From: Bakul Shah<>
Subject: [TUHS] Re: GOTO etc

Perhaps you’re talking about non-local GOTOs in Algol68, where you can jump from a nested procedure to a label in a lexically enclosing procedure. Pascal has this too. C has no nested procedures but its setjmp/longjmp is much more powerful (& dangerous). Though both can be used to the top level of a REPL or to jump to a known place after an error.

> On Mar 12, 2023, at 11:24 AM, Steve<>  wrote:
>  Dennis added setjmp() and longjmp() so the shell could handle errors in a reasonable way.
> There are two places where setjmp was used in the original shell (7th edition) code as I recall.  Both at the top level
> in main.c.
> The idea came from Algol68 but I do not know where it was originally invented.  longjmp() was used in the "exitsh"
> function that got called on the exit command, default trap routine and a fault with no trap set.
> It was also used when executing a subshell to avoid a fork and exec.  In this case the setjmp() was at top level
> in the initial sh setup.
> Hope this makes sense.  But these were two different uses.  One for error recovery and one to reset the execution environment
> back to initial state.
> Steve

[-- Attachment #2: Type: text/html, Size: 2067 bytes --]

             reply	other threads:[~2023-03-19 15:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-19 15:41 Steve [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-12 18:23 Steve

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