Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!paperboy!hsdndev!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: prototypes, NULL, and magic
Message-ID: <15588@smoke.brl.mil>
Date: 26 Mar 91 22:19:28 GMT
References: <1991Mar20.174710.4405@zoo.toronto.edu> <11202@dog.ee.lbl.gov> <1490@sheol.UUCP>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 7

In article <1490@sheol.UUCP> throopw@sheol.UUCP (Wayne Throop) writes:
>... I am moved to ask: what about the execl(2) family of functions, ...

These are specified in IEEE Std 1003.1.  Yes, in general they might not
work right if invoked without a prototype in scope.  Note also that the
often-seen practice of using an unadorned "0" to terminate the execl()
list has always been incorrect; a null pointer of type char* is needed.