As the first step in the decommissioning of sasCommunity.org the site has been converted to read-only mode.


Here are some tips for How to share your SAS knowledge with your professional network.


Difference between revisions of "Tips:Include Debugging Code in Your Programs"

From sasCommunity
Jump to: navigation, search
m (new submitted by template)
(add wikilinks)
 
Line 1: Line 1:
Many programmers will add debugging features (e.g., '''PROC PRINT''', '''PROC FREQ''', '''PROC CONTENTS''') to their programs and then remove them or comment them out when they '''''think''''' they are done testing. Instead of doing this, consider using macros that can be controlled by a global macro variable to turn debugging output on/off.
+
Many programmers will add debugging features (e.g., '''PROC PRINT''', '''PROC FREQ''', '''PROC CONTENTS''') to their programs and then remove them or comment them out when they '''''think''''' they are done testing. Instead of doing this, consider using [[macros]] that can be controlled by a global [[macro variable]] to turn debugging output on/off.
  
 
<div style="float:right">Submitted By [[User:Donh|Don Henderson]]</div>  
 
<div style="float:right">Submitted By [[User:Donh|Don Henderson]]</div>  

Latest revision as of 14:41, 2 June 2017

Many programmers will add debugging features (e.g., PROC PRINT, PROC FREQ, PROC CONTENTS) to their programs and then remove them or comment them out when they think they are done testing. Instead of doing this, consider using macros that can be controlled by a global macro variable to turn debugging output on/off.

Submitted By Don Henderson

....read more