> They can be good for both, can't they? ;^) Fair enough -- I guess I meant that always using them as a library of functions is the trap many new users (e.g. me) fall into when first using CFCs.
You can create utility CFCs that don't maintain state and are effectively just a collection of related methods. CFCs for manipulating images are often like this. In JavaScript, the Math class is a good example. I would suggest that as a general guideline, very few of your CFCs should be written like this. I'd also recommend you keep them in a separate folder, so you know you don't have to initialise them. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:221752 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=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
