Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!olivea!orc!inews!pima!bhoughto
From: bhoughto@pima.intel.com (Blair P. Houghton)
Newsgroups: comp.lang.c
Subject: Re: Strings as function names (again)
Message-ID: <2426@inews.intel.com>
Date: 10 Feb 91 21:42:22 GMT
References: <14972@smoke.brl.mil> <wolfram.666028267@ikki> <596@taumet.com>
Sender: news@inews.intel.com
Organization: Intel Corp, Chandler, AZ
Lines: 20

gwyn@smoke.brl.mil (Doug Gwyn) writes:
>One is that you have to tell it a path to the executable file, and
>that is not in general available for the currently-executing process.

wolfram@ikki.informatik.rwth-aachen.de (Wolfram Roesler) writes:
>Sure? How about argv[0] ?

In article <596@taumet.com> steve@taumet.com (Stephen Clamage) writes:
>How about it?  In an ANSI-conforming implementation (2.1.2.2.1):
>a.  argc may be 0, and argv a null pointer.
>b.  argv[0] may point to a null character.
>c.  argv[0] may contain the program name with no path information.

d.  argv[0] may contain grot.

e.g., `execl("/bin/sh","my dog has fleas","-c","/bin/echo $0",0);'
(using execl(3) under Ultrix).

				--Blair
				  "my dog has fleas"