Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!eris.berkeley.edu!mwm
From: mwm@eris.berkeley.edu (Mike (I'll think of something yet) Meyer)
Newsgroups: comp.sys.amiga.tech
Subject: setjmp/longjmp (Was: M2/C discussion)
Message-ID: <26034@agate.BERKELEY.EDU>
Date: 5 Jul 89 22:03:06 GMT
References: <4524@crash.cts.com> <18213@usc.edu> <8673@pyr.gatech.EDU> <413@xdos.UUCP>
Sender: usenet@agate.BERKELEY.EDU
Reply-To: mwm@eris.berkeley.edu (Mike (I'll think of something yet) Meyer)
Organization: Missionaria Phonibalonica
Lines: 23

In article <413@xdos.UUCP> doug@xdos.UUCP (Doug Merritt) writes:
<They're also defined cleanly enough that it's hard to imagine a modern
<day general purpose cpu that would have trouble allowing their
<implementation, so I wonder why they didn't get included.

Actually, I wonder why people think they weren't. They are in the
February 20th, 1987 draft (one of these days, I'll get a more recent
copy).

BTW, what makes you think the committee is only paying attention to
general purpose CPUs? "noalias" was added at the behest of people doing
implementations for vector processors.

In any case, setjmp/longjmp have changed slightly. I vaguely recall
hearing that it was at the behest of people doing C compilers for
LISPMs.

	<mike
--
Here's a song about absolutely nothing.			Mike Meyer
It's not about me, not about anyone else,		mwm@berkeley.edu
Not about love, not about being young.			ucbvax!mwm
Not about anything else, either.			mwm@ucbjade.BITNET