From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,27e79426c7fe2b67
X-Google-Attributes: gid103376,public
From: vladimir@speedy.intrepid.com (Vladimir Vukicevic)
Subject: Re: GNAT 2.04 Linux binaries?
Date: 1995/04/20
Message-ID: <VLADIMIR.95Apr19211236@speedy.intrepid.com>#1/1
X-Deja-AN: 101283315
references: <RBREWER.95Apr13234004@rwb114.rh.psu.edu>
 <3mm4vn$f52@mica.inel.gov>
organization: Intrepid Technology, Inc.
newsgroups: comp.lang.ada
Date: 1995-04-20T00:00:00+00:00
List-Id: <comp.lang.ada>

In article <D747BK.FCJ@nntpa.cb.att.com> ka@socrates.hr.att.com (Kenneth Almquist) writes:

> (In traditional C setjmp is a library routine.  In ANSI C, setjmp
> is a macro defined in setjmp.h.  Linux follows the ANSI C standard
> and defines setjmp to be __setjmp.)
> 					Kenneth Almquist

Speaking of this, does anyone know of any reason -why- ANSI C specifies
this? Or did someone just go off on a whim and say "Hey! Let's make
setjmp a macro, and break interfacing to every other language! Yeah!"?

	Vladimir