Xref: utzoo comp.lang.misc:5470 comp.unix.internals:251 Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!wuarchive!uunet!unhd!unhtel!paul From: paul@unhtel.uucp (Paul S. Sawyer) Newsgroups: comp.lang.misc,comp.unix.internals Subject: Re: Unix error handling Message-ID: <1990Sep11.171644.2740@unhtel.uucp> Date: 11 Sep 90 17:16:44 GMT References: <1990Aug31.190751.12522@dg-rtp.dg.com> <556:Aug3122:09:3290@kramden.acf.nyu.edu> <1990Sep2.050854.12008@nixtdc.uucp> <1990Sep4.004307.12274@Neon.Stanford.EDU> Distribution: usa Organization: UNH Telecommunications and Network Services Lines: 22 In article tim@Xsys..uucp (Tim Dawson) writes: >david@Neon.Stanford.EDU (David M. Alexander) writes: > >>You must have been reading about AIXv3 setjmp() and longjmp() recently. >>You can use these calls to do exactly that. >>AIXv3 is turning out to be a really nice OS. > >I hate to pop this bubble, but setjmp() and longjmp() are NOT from AIX - they >are a part of the SysVR3 release from AT&T and are utilized within Unix, among >other places. Source of my information: AT&T System 5 Release 3 internals >training. I have not checked too many OS ports, but this (based on the above) >exists in AIX, and also exists in Motorola SysV68 and SysV88, and I suspect in >most all ports of System V Release 3! Let's not give IBM credit for something >that they definitely did NOT come up with! >-- They were in System V Release 2.0 and 2.1, also; Prog. Ref. Manual, setjmp(3C). Wait - - Release [1.]5.3 had it too - - guess SysV "always" did! -- Paul S. Sawyer uunet!unh!unhtel!paul paul@unhtel.UUCP UNH Telecommunications attmail!psawyer p_sawyer@UNHH.BITNET Durham, NH 03824-3523 VOX: +1 603 862 3262 FAX: +1 603 862 2030