Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!spool.mu.edu!snorkelwacker.mit.edu!ai-lab!opal!net
From: net@opal.cs.tu-berlin.de (Oliver Laumann)
Newsgroups: comp.lang.c
Subject: Re: Small introspective program
Message-ID: <2871@kraftbus.cs.tu-berlin.de>
Date: 15 Mar 91 13:10:55 GMT
References: <1991Mar12.050929.2870@research.canon.oz.au> <SCOTTH.91Mar12125443@harlie.corp.sgi.com> <15462@smoke.brl.mil>
Organization: Technical University of Berlin, Germany
Lines: 23

In article <15462@smoke.brl.mil> gwyn@smoke.brl.mil (Doug Gwyn) writes:
> >And in any sh|csh|tcsh on unix, this one is about as short as you can get:
> >        cat $0
> 
> No, the program contained between the following quotation marks is shorter: ""

Hmmm...

% /bin/sh
$ > foo
$ chmod +x foo
$ ./foo
Cannot exec binary file.
sh: ./foo: cannot execute
$ ^D

This is what happens under SunOS 4.1.  Yes, I know, the original
poster said "on UNIX", but I found the fact that the SunOS shell
refuses to execute an empty file so funny that I wanted to share
it with you.

Don't tell me that this has something to do with the fact that Sun
switched to POSIX with SunOS 4.1...