This isn't U2 specific, but one practice that I picked up from a professor way back when, is to pass the barest number of arguments to a function/subroutine.
For example, if you need to compute a variable based on the attributes of a customer, instead of passing all the attributes (address, gross sales, invoices, etc.), you would simply pass the key to the customer file and retrieve those attributes in the function/subroutine itself. I suspect this isn't overly efficient from a hardware point of view and it does take longer to program initially, but once it is in place, it makes the function/subroutine so much easier to call from different programs. FWIW Mick Mick Gahan Director, MIS Metropolitan Community College Omaha, NE -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin King Sent: Friday, September 30, 2005 9:05 AM To: [email protected] Subject: RE: [U2] Programming Metrics (was "Good Programming Practice Question.........") Can we shift this discussion just a bit? Rather than address specific programming practices, what are some metrics that you use to define what is "good" in your environment? ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
