I (or anyone else) is in a position to say whether that's a
good or a bad design decision, but in general it's a bad one. If I'm
looking for quick and dirty, I output in methods all the time (both CFCs and
Java). I even occasionally do it in production code. But that's not
to say that I'll ever take "never output in a CFC unless that's all the CFC
does" off my mental design guidelines sheet, even if I don't always follow
it. Better to preach the ideal and break the rules where situations
demand, IMO.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Raymond Camden
Sent: Tuesday, March 16, 2004 1:26 PM
To: [EMAIL PROTECTED]
Subject: RE: [CFCDev] OUTPUT="false", WAS: RFC, CFC Best PracticesObviously my ToString comparison was bad, and I do agree that it is better to return a string than simply output, it just didn't make sense to me to say that if I had one method that output to the screen I should completely separate it from the rest of the CFC. I had a CFC for my bug tracker that had one method, render(), that would allow for a quick and dirty implementation of the tracker. It just made more sense to me at that time to bundle it with the CFC itself since it was just one method.=======================================================================
Raymond Camden, ColdFusion Jedi Master for Mindseye, Inc
Member of Team Macromedia
Email : [EMAIL PROTECTED]
Blog : www.camdenfamily.com/morpheus/blog
Yahoo IM : morpheus
"My ally is the Force, and a powerful ally it is." - Yoda
