I think the best compromise is to respond in kind to the question asked. If it's a simple straightforward question - even if the approach doesn't seem really sound - it might be best to answer it concisely and then add, "however that might not be the best design." See if the person bites and asks for more info. What might frustrate a lot of new users is when people launch into lengthy posts explaining all kinds of OO concepts that are way over their head. No one should be discouraged from providing valuable info, but in every case the question-asker might not be interested. It's just a matter of trying to gauge that I suppose.
I'm writing documentation for my development team on CFCs including a lot of the best practices I've pulled from various sources (including all the great responses to my question today). I think a lot of those practices can be presented very concisely and answer a lot of questions that newbies have about using CFCs. I think it would be a cool resource to start up a Wiki on CFCzone.org and just direct users to that post. That would save a lot of us typing and also not open up these big debates about OO design :)
-Cliff
---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com).
An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
