Xref: utzoo comp.lang.misc:5467 comp.unix.internals:200 Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!evax!utacfd!letni!doug From: doug@letni.UUCP (Doug Davis) Newsgroups: comp.lang.misc,comp.unix.internals Subject: Re: Unix error handling Message-ID: <13061@letni.UUCP> Date: 10 Sep 90 19:33:07 GMT References: <1990Sep2.050854.12008@nixtdc.uucp> <1990Sep4.004307.12274@Neon.Stanford.EDU> Followup-To: comp.unix.internals Distribution: usa Organization: Logic Process, Dallas Tx 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. >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 Uh, just to streighten the record a bit more, setjmp()/longjmp() in user programs have been around since at least V7. Basicly all they are is a save/recover of the register states of a process, kinda like push & pop or movem instructions, but from within a C program. Additionally some os's may have special handling for external things, like signals for instance, when returning to a state via a longjmp(). doug __ Doug Davis/4409 Sarazen/Mesquite Texas, 75150/214-270-9226 {texsun|lawnet|smu}!letni!doug doug@letni.lonestar.org "Be seeing you..."