Somebody may have a better idea than I do, but I think it is to make the
code easier to maintain and *enhance*. If at some point in the future a
different developer working on the same package may need to make what seems
like a simple enahancement involving a call to a Fileman entry point inside
the function there could be a problem with un-namespace variables.
That said, I have written code like your example using the variable I as an
iteration variable.
Jim Gray
----- Original Message -----
From: "Kevin Toppenberg" <[EMAIL PROTECTED]>
To: "Hardhats Sourceforge" <[email protected]>
Sent: Sunday, September 04, 2005 10:07 PM
Subject: [Hardhats-members] Namespacing rationale?
What is the rationale behind the SAC mandate to use namespaced
variables in one's functions.
If I write this code:
MyFunction(x)
new i
for i=1:1:10 write x,!
quit
Is there any way I can have a name collision if I "new" all my
variables? It seems that if one is not using variables with global
scope, there shouldn't be a need to use namespaced variables.
Is it that VistA code does not reliably NEW it's variables, and thus
might collide with my variables should I call its functions?
Thanks
Kevin
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members
