Advanced Coding (from Fraktal SAS Programming): Unterschied zwischen den Versionen

Aus phenixxenia.org
Zur Navigation springen Zur Suche springen
(Die Seite wurde neu angelegt: „While the crude approach to MACRO programming is 1st choice for any ad-hoc implementation it will never result in a piece of software that will survive in a qu…“)
 
K
 
(Eine dazwischenliegende Version desselben Benutzers wird nicht angezeigt)
Zeile 1: Zeile 1:
While the crude approach to MACRO programming is 1st choice for any ad-hoc implementation it will never result in a piece of software that will survive in a quality controlled environment. Moreover, when used as component in a modularized system it will not produce predictable results and very likely mess things up at run-time.  
+
[[Kategorie:zazy]]
 +
{{SeitenNavigation1
 +
|links=xx_left.png
 +
|zurück=Generalized Approach (from Fraktal SAS Programming)
 +
|rechts=xx_right.png
 +
|vorwärts=Symbol Tables (from Fraktal SAS Programming)
 +
|hoch=Duck_zazy_com.png
 +
|übersicht=Macro (from Fraktal SAS Programming)
 +
}}
 +
 
 +
While the crude approach to MACRO programming is 1st choice for any ad-hoc implementation it will quite unlikely result in a piece of software that will survive in a quality controlled environment. Moreover, when used as component in a modularized system it will not produce predictable results and very likely mess things up at run-time.  
  
 
'''Why?'''
 
'''Why?'''
Zeile 8: Zeile 18:
  
 
'''That’s why!'''
 
'''That’s why!'''
 +
 +
{{SeitenNavigation1
 +
|links=xx_left.png
 +
|zurück=Generalized Approach (from Fraktal SAS Programming)
 +
|rechts=xx_right.png
 +
|vorwärts=Symbol Tables (from Fraktal SAS Programming)
 +
|hoch=Duck_zazy_com.png
 +
|übersicht=Macro (from Fraktal SAS Programming)
 +
}}

Aktuelle Version vom 9. Mai 2014, 10:16 Uhr

Zurück

Übersicht

Vorwärts

While the crude approach to MACRO programming is 1st choice for any ad-hoc implementation it will quite unlikely result in a piece of software that will survive in a quality controlled environment. Moreover, when used as component in a modularized system it will not produce predictable results and very likely mess things up at run-time.

Why?

The key reason is, that SAS languages – like other programming languages – do use variable properties, but without forcing the programmer to deliver this information by declaring everything forehand in a header section or similar place.

SAS code is executed regardless whether explicit declaration is found or not. When none is found, SAS applies built-in rules to perform automatic declaration on which it then operates. Properties given that way might not conform with programmers’ expectations or the system’s design requirements.

That’s why!

Zurück

Übersicht

Vorwärts