> The point I was trying to make (unsuccessfully by the look of it) is > that large organizations which have far more experience than I do of > writing software often have very strong opinions that what you're > advocating is a bad idea. I'm not sure how they formed those opinions, > but I'd bet previous experience played a big part in it.
No, I knew that's what you meant. My take on this is twofold: 1) you cite a couple that have that policy. How many *don't* have that policy? I don't know the answer to this, but it's relevant. 2) my experience of these policies is *quite often* they are actually not based on anything particularly well thought out, and just based on someone's personal preference (the person writing the document), or bad information. Take this very thread "don't use iif() because it's slower than <cfif>, and if you use it you'll be fired". Our OWN coding standard used to have that in it. I challenged it; we amended the coding standard. We're just a small organisation, though, and our CS was just seat-of-the-pants stuff (I wrote it), and not nearly as well thought out as something Sean and his ilk would come up with, but it demonstrates that these things aren't AUTOMATICALLY correct. It's not the Bible (ahem). I fully agree that CSs are A Good Thing, and should be adhered to. But they should also be open to modification, and can't be taken as the One True Way, just because someone has written it down. -- Adam --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
