|
Lim Hock-Chai wrote: > If editScreenInput() > ... Do something > Else > ... Do something else > endif Well, if function were named 'screenInputValid', then it would be pretty obvious. *IMHO* (emphasis mine), this makes for far clearer and easier to understand code. My biggest problem with having variables that are used to indicate logical results is that it's not always obvious what the value of those variables are? Just the other day I ran into some code that was testing the result of a function ... 'if result = True' (where true was a variable in the program), but result was a boolean variable and True was a alpha initialized to 'Y'. david
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.