× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




On 20/12/2005, at 6:42 PM, Scott Klement wrote:

Second, you can (if you like) use the method I described above. A naming convention like that one helps when troubleshooting problems because it's easy to tell from error messages where to look for a subproedure. For example, if you have a subprocedure called "calcTax" how do you know which module it's in? However, if you name it "invoice_calcTax" and your convention is to always start with the module name, then you'll know that it's in the INVOICE module.

Not that I particularly object to using the module name as the prefix on a procedure but this reasoning is specious. The error message itself contains the procedure, module, and object names so it's always easy to know where a message originated as long as it was sent directly from the procedure and not from some common sendMessage procedure. If the message was sent from a common procedure then no naming convention will help determine where it really originated unless that information is also passed into the common sendMessage function and is then included in the message text itself.

Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists

   http://www.flybynight.com.au/
   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175                                   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.