Xref: utzoo comp.lang.c:37018 alt.sources:3470
Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uakari.primate.wisc.edu!sdd.hp.com!news.cs.indiana.edu!noose.ecn.purdue.edu!en.ecn.purdue.edu!steele@en.ecn.purdue.edu
From: steele@en.ecn.purdue.edu@en.ecn.purdue.edu (Richard A. Steele)
Newsgroups: comp.lang.c,alt.sources
Subject: Re: Small introspective program
Message-ID: <1991Mar13.151756.2885@en.ecn.purdue.edu>
Date: 13 Mar 91 15:17:56 GMT
References: <1991Mar10.231230.1301@casbah.acns.nwu.edu> <1991Mar12.050929.2870@research.canon.oz.au> <1991Mar13.032422.9438@cavebbs.gen.nz>
Organization: Purdue University
Lines: 30

In article <1991Mar13.032422.9438@cavebbs.gen.nz> clear@cavebbs.gen.nz (Charlie Lear) writes:
>In article <1991Mar12.050929.2870@research.canon.oz.au> andy@research.canon.oz.au (Andy Newman) writes:
>>The smaller the better! In many interpreted BASIC's of years ago you could do:
>>	1 LIST
>>Which when RUN would produce:
>>	1 LIST
>>(Using a single digit line number to make it as small as possible).
>
>Sorry, your entry is disqualified through being too large. REAL BASICs used
>to be able to tokenise, and the winner is:
>	1 L.
>which when run would produce
> 	1 L.
>
>Lets see you do THAT in C!
>

You sure?  If the BASIC is tokenized, then L. will be expanded to LIST
in the source code listing, so that you'd get
	1 LIST
when run.  I have to admit, my only experience with tokenized basics is
the old 8-bit Ataris; do other basics leave the abbreviation?

Rich

-- 
-------------------------------------------------------------------------------
Richard Steele          |  INTERNET : steele@ecn.purdue.edu
Electrical Engineering  |  BITNET   : steele%ecn.purdue.edu@purccvm
Purdue University       |  UUCP     : {purdue, pur-ee}!ecn.purdue.edu!steele