|
Paul, I think Ward Cunnigham's wiki has a good discussion about this topic. http://c2.com/cgi/wiki?DontRepeatYourself Basically, if you have to change the read or exfmt statement, you could forget to change the other one. It happened to me once or twice last year. Regards. -- Antoine CONTAL [...] Most programmers seem to code with the single read/exfmt style which IMHO complicates the code. In a DoU/Read loop the body of the loop is nested two deep inside the DoU and an If statement. In a Read/DoW/Read loop the body of the loop is nested one deep inside a DoW. Doesn't this reduction in the nesting of the body of the loop improve the program? Readability is improved. Performance is also improved (although minor) with the removal of one test against the end of loop. Other programmers I work with are adamant about not coding more than one read statement. Why is coding more than one read statement such a problem? Paul -- Paul Morgan Senior Programmer Analyst - Retail J. Jill Group 100 Birch Pond Drive, PO Box 2009 Tilton, NH 03276-2009 Phone: (603) 266-2117 Fax: (603) 266-2333 Les informations contenues dans ce message sont confidentielles et peuvent constituer des informations privilegiees. Si vous n etes pas le destinataire de ce message, il vous est interdit de le copier, de le faire suivre, de le divulguer ou d en utiliser tout ou partie. Si vous avez recu ce message par erreur, merci de le supprimer de votre systeme, ainsi que toutes ses copies, et d en avertir immediatement l expediteur par message de retour. Il est impossible de garantir que les communications par messagerie electronique arrivent en temps utile, sont securisees ou denuees de toute erreur ou virus. En consequence, l expediteur n accepte aucune responsabilite du fait des erreurs ou omissions qui pourraient en resulter. --- ----------------------------------------------------- --- The information contained in this e-mail is confidential. It may also be legally privileged. If you are not the addressee you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return e-mail. E-mail communications cannot be guaranteed to be timely secure, error or virus-free. The sender does not accept liability for any errors or omissions which arise as a result. $!4$!
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.