Article View: comp.std.c
Article #4318Re: setjmp.h
From: Christopher R. Volpe
Date: Wed, 01 Nov 1995 17:46
Date: Wed, 01 Nov 1995 17:46
13 lines
939 bytes
939 bytes
In article <815241910snz@soliton.demon.co.uk>, Ian Cargill <ian@soliton.demon.co.uk> writes: > >The standard allows setjmp to be either a macro or an 'identifier >with external linkage'. Why the latter? Why not the latter? Why should an implementer be forced to make setjmp a macro rather than an ordinary function call? -- Chris Volpe Phone: (518) 387-7766 (Dial Comm 8*833 GE Corporate R&D Fax: (518) 387-6560 PO Box 8, Schenectady, NY 12301 Email: volpecr@crd.ge.com
Technical Details
Message-ID:
<478bqi$nb3@rdsunx.crd.ge.com>Path:
arc1-ca.pugleaf.net!bart.crd.ge.com!volpeReferences:
<815241910snz@soliton.demon.co.uk>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!bart.crd.ge.com!volpe From: volpe@bart.crd.ge.com (Christopher R. Volpe) Newsgroups: comp.std.c Subject: Re: setjmp.h Date: 1 Nov 1995 17:46:58 GMT Organization: GE Corporate Research & Development Sender: volpe@bart (Christopher R. Volpe) Distribution: world Message-ID: <478bqi$nb3@rdsunx.crd.ge.com> References: <815241910snz@soliton.demon.co.uk> Reply-To: volpe@ausable.crd.ge.com NNTP-Posting-Host: bart.crd.ge.com