|
Ron,
My translation for "recursion" is "Your memory has been chewed to ....".
Consequently, when I am doing anything serious interactively I promptly get
out of SAS. On the other hand, I ran
1046 %let x =
1047 %let y=x ;
ERROR: Open code statement recursion detected.
1048
1049 %put ok ;
ok
1050 %q
abc ; def
1051 %let x =
1052 %let y=x ;
ERROR: Open code statement recursion detected.
1053
1054 %put ok ;
ERROR: Open code statement recursion detected.
1055 %q
abc ; def
So why did 1049 work correctly and 1054 did not? Well I did something
different. 1049 was submitted separately, 1054 was not. Sometimes it may
just be the enhanced editor quirks that gives one the jitters.
IanWhitlock@westat.com
-----Original Message-----
From: Fehd, Ronald J. (PHPPO) [mailto:rjf2@CDC.GOV]
Sent: Friday, December 13, 2002 1:09 PM
To: SAS-L@LISTSERV.UGA.EDU
Subject: Re: recruiting cheesy, sleasy SAS tricks
> From: Larry Hoyle [mailto:lhoyle@KU.EDU]
> How about the classic trick of submitting some string like
> *'; *"; */; *\;run
> or
> *); */; /*'*//*"*/;%mend;
>
> to "reset" an interactive SAS session which is waiting for a
> closing quote etc.
anyone figured out to recover from
1 %let x=
2 %let y=x;
ERROR: Open code statement recursion detected.
Ron Fehd the macro maven CDC Atlanta GA USA RJF2@cdc.gov
do not fold, spindle, or mutilate -- IBM punch card
... the mVar assignment statements.
| 
