Isaac, I respect your opinion, but I just don't agree.
Kevin. -----Original Message----- From: S. Isaac Dealey [mailto:[EMAIL PROTECTED] Sent: Tue 8/16/2005 6:59 PM To: CF-Talk Subject: RE: CFEclipse 1.2 > Why do we have any error catching tools? > If we all wrote perfect code we wouldn't > need them, but at least cf is flexible > enough to provide them. Sure we should > keep our code small, but the ide should > be able to handle it regardless. Just > because you shouldn't run into a problem > doesn't mean you avoid it. Umm... yes, yes it does... If a problem is caused by a poor coding habbit, then I adopt a better coding habbit. The same way that, if I discover that I'm spending a lot of money on tires as a result of frequently driving over broken glass, I will try and reduce the amount of broken glass I drive over. Can I drive over broken glass? Yes. Does it always puncture the tire? No. Do I ignore the glass in the road because it may not puncture the tire? No. And sure, I may buy fixaflat and tires that are advertised as being more puncture resistant, but I'm not going to bitch to the tire company because the tires don't last if I pave my driveway with broken glass. The example of error handling tools in CF isn't a good one... Errors often occur during normal operation -- this is analogous to fix-aflat or more puncture resistant tires. Error handling tools are used in normal operating conditions. Editing a code template that's the size of an Oxford English Dictionary should not be a normal operating condition and therefore does not deserve the kind of attention devoted to tasks performed under normal operating conditions. Moreover, it's also not something that occurs accidentally like a bug or glass in the road... you don't look up one morning and say "woooops! that ColdFusion template just ougrew a CD" -- it's something you have absolute control over at all times, and can easily avoid. It takes all of a few seconds to slice it up into a couple includes. I'd much prefer the couple seconds to do that over continuing to struggle and argue and bitch about the fact that the IDE has problems with it for hours or days on end. It's a quick, easy, simple and obvious solution which at the same time means better code. Why fight doing something that's an inate improvement, has no drawbacks and requires almost no time to implement? And if you're not fighting it, then you have no reason to complain about any given IDE having a problem with the alternative. s. isaac dealey 954.522.6080 new epoch : isn't it time for a change? add features without fixtures with the onTap open source framework http://www.fusiontap.com http://coldfusion.sys-con.com/author/4806Dealey.htm ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:215365 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
