|
Kurt, My two cents. A subprocedure has no business controlling the flow of anything that calls it. It's a poorly designed procedure if it forces any caller into behavior that isn't really wanted. You may be writing both the caller and the subprocedure but what if some other programmer wants to lift your subprocedure code for use in another program? You're just asking for trouble. Instead of ending the program the procedure should notify the caller then let the caller decide what to do with the error. Have the procedure return one value. If it needs to return more than one value pass the rest as non-const parameters to the procedure. In this case I would return the indicator as the result value and pass the variable that is also to be returned as the last parameter in the procedure call. Paul
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.