Does anyone else think it's bad practice to have code in INCLUDES? Surely it would be much better to have the INITIATE.FEEDBACK & GIVE.FEEDBACK routines written as subroutines, and then simply call them from the appropriate spots.
If the code in either of those routines needs to be changed, you'll need to also recompile all the programs using the include. But as subroutines all you need to do is recompile the subroutine in question. Although, INCLUDES are fantastic for things like common & equate definitions. Adrian DISCLAIMER: Disclaimer. This e-mail is private and confidential. If you are not the intended recipient, please advise us by return e-mail immediately, and delete the e-mail and any attachments without using or disclosing the contents in any way. The views expressed in this e-mail are those of the author, and do not represent those of this company unless this is clearly indicated. You should scan this e-mail and any attachments for viruses. This company accepts no liability for any direct or indirect damage or loss resulting from the use of any attachments to this e-mail. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
