Path: ...!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.arch Subject: Re: except what, is Vax addressing sane today Date: Tue, 24 Sep 2024 00:41:39 -0000 (UTC) Organization: A noiseless patient Spider Lines: 14 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Tue, 24 Sep 2024 02:41:40 +0200 (CEST) Injection-Info: dont-email.me; posting-host="43fa132f54fd9f5c91573130fd9389bf"; logging-data="3066240"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/IOBs9rllaPAJENP4Z0Wr2" User-Agent: Pan/0.160 (Toresk; ) Cancel-Lock: sha1:smkbxRlDs8mc0vJVxVCmOktEyAo= Bytes: 1844 On Sun, 22 Sep 2024 09:14:04 -0700, Lars Poulsen wrote: > From a programmer's perspective, VAX exception handling was very nice. > It may have been high overhead, though. Very high overhead. But it was also language-independent, and integrated into the procedure-calling convention, which also managed to be language- independent. There is an internal memo on Bitsavers somewhere, critiquing a proposal to adopt the MIPS architecture (which DEC did, for just one machine, the DECstation 3000 if I recall rightly), and one of the points against MIPS was that it didn’t have language-independent exception handling. But then no other architecture, before the VAX or since, has been able to do that.