"Good" code. What (TF) is that and how does that relate to a statements inclusion in a manual or not? Explain yourself and - the rules for you are - don't peek in a dictionary or use an electronic grammar or spell checker. ;-) Stuart Boydell
>-----Original Message----- >> Yeah - I remember thinking on some of those conversion questions that I >> did not really know what they did - when it comes to strange or complex >> conversions like that I just get the manual out. It is certainly not >> something one does every day. >Exactly the point I was making - if something you've written requires the >next person to get the manual out to understand it then it's not good code, >regardless of whether it's more efficient or not. Just because you *can* do >it doesn't mean you *should* do it! ********************************************************************** This email message and any files transmitted with it are confidential and intended solely for the use of addressed recipient(s). If you have received this communication in error, please reply to this e-mail to notify the sender of its incorrect delivery and then delete it and your reply. It is your responsibility to check this email and any attachments for viruses and defects before opening or sending them on. Spotless collects information about you to provide and market our services. For information about use, disclosure and access, see our privacy policy at http://www.spotless.com.au Please consider our environment before printing this email. ********************************************************************** ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
