LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (October 2010, week 1)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Sat, 2 Oct 2010 14:42:23 -0700
Reply-To:     Sterling Paramore <gnilrets@GMAIL.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Sterling Paramore <gnilrets@GMAIL.COM>
Subject:      Re: Smallest SAS program working indefinitely?
In-Reply-To:  <70470.63953.qm@web55305.mail.re4.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1

Whenever I put unmatched quotation marks in an EG program, it runs indefinitely. So here's my proposal:

'

-Sterling

On Sat, Oct 2, 2010 at 1:16 PM, ajay ohri <ajayohri@yahoo.com> wrote:

> proc sql (oracle connect to bigbigbigoracledb) ; > select * > from *; > quit; > > regards > Ajay > > http://decisionstats.wordpress.com > > will run forever > > > > "If you have the guts, you will have the glory" > > > > > --- On Sun, 10/3/10, Arthur Tabachneck <art297@NETSCAPE.NET> wrote: > > > From: Arthur Tabachneck <art297@NETSCAPE.NET> > > Subject: Re: Smallest SAS program working indefinitely? > > To: SAS-L@LISTSERV.UGA.EDU > > Date: Sunday, October 3, 2010, 12:23 AM > > Jack, > > > > I don't think you can "store" and old style macro, but you > > can effectively > > accomplish the same functionality. According to the > > documentation: > > > > You can simulate a macro library facility by using the > > %INCLUDE > > statement or by putting your macros in a sequential data > > set that is > > concatenated to the front of the SYSIN file. (Note: VSE > > data sets > > cannot be concatenated. Under VSE, the macros must be > > included at the > > front of the input stream.) > > > > If anyone is interested in the documentation, take a look > > at: > > > > http://128.192.1.76/pub/sas/docs/technote/ts289.txt > > > > Is it 3:30 yet? > > > > Art > > --------- > > On Sat, 2 Oct 2010 09:05:13 -0700, Jack Hamilton <jfh@STANFORDALUMNI.ORG > > > > wrote: > > > > >It's Art's contest, not mine, but I would count every > > character you have > > to type anywhere as part of the total. That > > eliminates the old-style > > macro solution, because it's longer than just typing in the > > program. > > > > > >I think I'd also say that the solution has to be > > platform-independent, > > not relying on some trick of the operating system. > > And that eliminates > > the "x sas a" solution. How SAS is invoked is part of > > the OS, not part of > > SAS (where I work, for example, you don't start SAS by > > typing in "sas"). > > > > > > > > > > > >-- > > >Jack Hamilton > > >jfh@alumni.stanford.org > > >Caelum non animum mutant qui trans mare currunt. > > > > > > > > > > > > > > >On Oct 2, 2010, at 8:48 , Joe Matise wrote: > > > > > >> Did you disallow putting things in the autoexec? > > :) > > >> > > >> x 'sas' > > >> > > >> would be seven characters, and if put in the > > autoexec, would cause an > > infinite loop (if paths are appropriate to ensure windows > > finds SAS)... > > not sure if it should truly count though because Windows > > would run out of > > memory at some nontrivial point. > > >> > > >> (Could run x sas, in fact, couldn't you? > > Don't recall the rules for > > quotes around x commands. Then maybe you could get > > around the autoexec > > requirement by > > >> > > >> x sas a > > >> > > >> where a = this sas program.) > > >> > > >> -Joe > > >> > > >> On Sat, Oct 2, 2010 at 10:42 AM, Jack Hamilton > > <jfh@stanfordalumni.org> > > wrote: > > >> I don't think macros should be allowed in this > > challenge. Or if they > > are, the macro text should count as part of the program. > > >> > > >> Will old-style macros be found in an sasautos > > location? > > >> > > >> > > >> > > >> -- > > >> Jack Hamilton > > >> jfh@alumni.stanford.org > > >> Caelum non animum mutant qui trans mare currunt. > > >> > > >> > > >> > > >> > > >> On Oct 2, 2010, at 7:35 , Arthur Tabachneck > > wrote: > > >> > > >> > Jim, > > >> > > > >> > I've been continuously thinking about this > > problem for the past six > > years, > > >> > ever since you challenged SAS-L to create the > > shortest SAS program > > that > > >> > would run indefinitely (or at least until the > > computer died or someone > > >> > halted the process). > > >> > > > >> > I realize that you never took my original > > entry seriously, and later > > >> > included a number of constraints and > > restrictions that weren't part > > of the > > >> > original challenge, but the review board > > agreed that those extra > > >> > conditions constituted an unfair practice and > > would be discounted. > > >> > > > >> > Thus, based on the old style macro thread I > > read yesterday, I simply > > have > > >> > to submit another entry. A one > > character program: > > >> > > > >> > z > > >> > > > >> > where z is an old style macro, stored > > wherever one likes to keep their > > >> > macros, containing the following: > > >> > > > >> > macro z > > >> > data _null_; > > >> > a: i+1; > > >> > goto a; > > >> > run; > > >> > % > > >> > > > >> > Is it Friday yet? > > >> > > > >> > Art > > >> > --------- > > >> > On Wed, 1 Dec 2004 20:35:21 -0500, Arthur > > Tabachneck > > <art297@NETSCAPE.NET> > > >> > wrote: > > >> > > > >> >> Jim, > > >> >> > > >> >> I presume that your post, since it was in > > November-week 5, never got > > any > > >> >> takers. > > >> >> > > >> >> However, since it still isn't Friday, > > I'll propose my entry: > > >> >> > > >> >> x b; > > >> >> > > >> >> where 'b' is a dos batch file (stored in > > the C:\Program > > Files\SAS\SAS 9.1 > > >> >> directory) as follows: > > >> >> > > >> >> sas a > > >> >> > > >> >> and 'a' is a sas program (although most > > of its contents are > > irrelevant), > > >> >> labeled 'a.sas', and stored in the > > 'C:\Program Files\SAS\SAS 9.1' > > >> > directory > > >> >> as follows: > > >> >> > > >> >> data _null_; > > >> >> a: i+1; > > >> >> goto a; > > >> >> run; > > >> >> > > >> >> In short, 4 key strokes. Of course, > > as Richard will soon point out, > > the > > >> >> same program could be imbedded within any > > one of the potential SAS > > >> >> initialization routines (cfg, window's > > icon properties, etc.), thus > > not > > >> >> require any keystrokes. > > >> >> > > >> >> Art > > >> >> ------- > > >> >> On Tue, 30 Nov 2004 04:47:23 -0500, Jim > > Groeneveld > > <jim1stat@YAHOO.CO.UK> > > >> >> wrote: > > >> >> > > >> >>> Hi friends, > > >> >>> > > >> >>> I have deposited my current > > 7-character solution on my website in: > > >> >>> http://home.hccnet.nl/jim.groeneveld/Smallest/Eternal.ZIP > > >> >>> which you already can download, but > > not yet view. > > >> >>> Listing http://home.hccnet.nl/jim.groeneveld/Smallest > > >> >>> reveals the date and time of the > > deposit. > > >> >>> I have doubly encrypted the solution > > with a (ZIP file) password > > >> >>> which I will release on Friday on > > SAS-L.....................;-) > > >> >>> > > >> >>> I hope there are no password crackers > > around on SAS-L. > > >> >>> > > >> >>> Regards - Jim. > > >> >>> -- > > >> >>> Y. (Jim) Groeneveld, MSc., > > Biostatistician, Science Team > > >> >>> Vitatron B.V., Meander 1051, 6825 > > MJ Arnhem > > >> >>> P.O.Box 5227, 6802 EE Arnhem, the > > Netherlands > > >> >>> Tel: +31/0 26 376 7365, Fax: +31/0 26 > > 376 7305 > > >> >>> Jim.Groeneveld_AT_Vitatron.com > > (replace _AT_ by AT sign) > > >> >>> http://www.vitatron.com, http://home.hccnet.nl/jim.groeneveld > > >> >>> > > >> >>> Postponing distribution on SAS-L > > prevents more of these futile > > ideas. > > >> >>> > > >> >>> [common disclaimer] > > >> > > >


Back to: Top of message | Previous page | Main SAS-L page