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 (December 2008, week 3)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:   Tue, 16 Dec 2008 12:34:57 -0800
Reply-To:   "Pardee, Roy" <pardee.r@GHC.ORG>
Sender:   "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:   "Pardee, Roy" <pardee.r@GHC.ORG>
Subject:   Re: Enforcing good practices (e.g. variable declaration)?
In-Reply-To:   <22170333.1229457354033.JavaMail.SVC_SecMsg@WPSCV6CT>
Content-Type:   text/plain; charset="us-ascii"

Long ago someone on this list mentioned this guy:

options dsoptions="note2err" ;

Not sure what-all it does (where is this documented?), but it definitely produces ERRORs for undeclared variables. I think it does likewise with type coercion, but am not sure. It's in my new-sas-program header template...

HTH,

-Roy

-----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Marc Weinmann Sent: Tuesday, December 16, 2008 11:56 AM To: SAS-L@LISTSERV.UGA.EDU Subject: Enforcing good practices (e.g. variable declaration)?

Hi All - I have a simple question I've never seen answered for SAS. Many programming languages have options to force strict variable declaration and flag accidental type-o's more quickly, such as a variable used in only one spot of a program. In VB you have "Option Explicit" or in perl there is "use strict" or "use warnings". Are there any comparable options for SAS programs?

Thanks Marc


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