Date: Fri, 24 Feb 2006 14:14:52 -0500
Reply-To: "data _null_;" <datanull@GMAIL.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: "data _null_;" <datanull@GMAIL.COM>
Subject: Re: array or other (concerns the future of the Do Over statement)
Content-Type: text/plain; charset=ISO-8859-1
Aren't you forgetting about _N_ _ERROR_ _I_.
Add a PUT _ALL_;
Doesn't sound(look) like a bug at all to me.
On 2/24/06, Nat Wooding <Nathaniel_Wooding@dom.com> wrote:
> This thread appeared during the summer of 2005 and the last comment appears
> to have been from Paul Choate. You may find the summary at
> I have not been through all of the comments but it is noted that starting
> with V6, the Do Over statement has been relegated to the status of "we will
> support it for legacy code but do expect new code to work with it). Many of
> the contributers to the thread were lamenting such treatment of a useful
> For those who have not seen a do over, here is a simple untested example;
> data a;
> input vals v1-v5;
> array v: ;
> do over vals;
> 1 2 3 4 5
> 56 7 8 9 10
> This past week I found an apparent bug in the way the array implicit arrays
> are built when using a colon operator in the array spec. Try the following
> DATA TABLE;
> INPUT id _0 $2. _1 $2. ; * note that the underscore vars are
> array able _:;
> 1 a b
> 2 c d
> proc print;run;
> You should receive an error message stating that all of the variables in
> the array should be of the same type (numeric or character). If you change
> the array to read
> array able _0: _1: ;
> the array is processed properly.
> The problem occurs in both V8 and V9. FWIW, V9 appears to have no other
> problems with Implicit arrays.
> I reported this to SAS tech support and, after the problem was
> investigated, received a message that included the passage
> "Unfortunately this is not something that would be considered for a fix
> since Implicit Arrays/Do Over has been kept around for compatibility
> reasons beginning in Version 6."
> The positive note for those of us who find implicit arrays useful is that
> SAS is continuing to maintain them, sort of. At least, the situation that I
> found that broke them is a little uncommon.
> However, it looks like some of old dogs are going to have to get used to
> jumping through different hoops.
> ps -- isn't someone going to start a decent OT Friday afternoon thread?
> CONFIDENTIALITY NOTICE: This electronic message contains
> information which may be legally confidential and/or privileged and
> does not in any case represent a firm ENERGY COMMODITY bid or offer
> relating thereto which binds the sender without an additional
> express written confirmation to that effect. The information is
> intended solely for the individual or entity named above and access
> by anyone else is unauthorized. If you are not the intended
> recipient, any disclosure, copying, distribution, or use of the
> contents of this information is prohibited and may be unlawful. If
> you have received this electronic transmission in error, please
> reply immediately to the sender that you have received the message
> in error, and delete it. Thank you.