1. Should my functions be returning something instead of setting values of globals? (er.. FSL: file-scope lexicals, that is)At least you don't have the globals in the body of functions definitions. You can now analyze the functions in separation from the rest of the code - this is a clear win. The next step is to move more code into the functions - and you'll get mostly global free code....
(1) If you say "yes" to the first one, then what does that buy me? Instead of setting an FSL somewhere, I'm returning values, and so need to create an FSL to hold the value anyway!
In reply to Re^3: What are the core points of good procedural software design? (functions, code structuring)
by zby
in thread What are the core points of good procedural software design? (functions, code structuring)
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |