> Forgive me Sean but I can't see the problem. It's one of those things that really can't be explained if you don't 'get' it... encapsulation is a good thing... it helps you build more reusable code. Referencing external stuff (like request scope or server scope) from inside an object is a violation of encapsulation. That's just a fact. Whether or not that violation of encapsulation is important to you depends on how much you value encapsulation. If you don't 'get' encapsulation then you won't value it so it's kinda moot...
> <cfreturn request.kernel.utils.arrayostructs(qry) /> That's a violation of encapsulation, plain and simple. Something Barney and I wouldn't do because we value the benefits of encapsulation but something that others would do if they don't yet view encapsulation as important. > but isn't instanciation of objects a performance hit? Depends. And even if it is, the performance hit may well be irrelevant compared to the benefits of maintaining encapsulation. It's that old saw about never optimize unless you know you have a problem and you've tracked it down to something specific... ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
