Path: utzoo!attcan!sobmips!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!purdue!decwrl!shelby!eos!amelia!prandtl.nas.nasa.gov!mfuller
From: mfuller@prandtl.nas.nasa.gov (Mike J. Fuller)
Newsgroups: comp.unix.wizards
Subject: Re:  How do you tell a wizard?
Message-ID: <3832@amelia.nas.nasa.gov>
Date: 15 Nov 89 20:43:32 GMT
References: <1989Oct31.133417.2409@lsuc.on.ca> <4417@condict.cs.vu.nl>
Sender: news@amelia.nas.nasa.gov
Reply-To: mfuller@prandtl.nas.nasa.gov (Mike J. Fuller)
Organization: NASA Ames Research Center
Lines: 24

In article <4417@condict.cs.vu.nl> condict@cs.vu.nl (Michael Condict) writes:
>In article <1989Oct31.133417.2409@lsuc.on.ca> jim@lsuc.UUCP (Jim Mercer) writes:
>>> Actually, real programmers don't bother storing the
>>> code.  Why do you think I linked /dev/tty to /dev/tty.c
>>> on this system several years ago?  Handy for those simple
>>> C tests.
>> seriously?
. . .
>I'm afraid this is an example of cleverness run amok.  Simpler and better
>would be the following "compile and execute" filter, which I've just
>put in my bin directory as the ce command:
. . .

How about a little program consisting of:

#include "/dev/tty"

Or is that abusing the rules a little too much :-)

/-----------------------------------------------------------------------------\
| Mike J. Fuller |Internet: mikef@sarah.lerc.nasa.gov     |You'd be paranoid, |
|----------------|          mikef@zippysun.math.uakron.edu|too, if everyone   |
|/\/\/\/\/\/\/\/\|Bitnet:   r3mjf1@akronvm                |was out to get you!|
\-----------------------------------------------------------------------------/