On 17/07/2010, at 8:16 AM, Jeff Coughlin wrote: > But, yeah. That one change in arrayTable.cfc (setting bRefObjects="false") > breaks a lot of extended array use we have. Sure we can manually turn it on > for all extended array components, but is there a specific reason for > disabling that? Just wondering. Although it breaks backwards compatibility, > if there is a reason to have it there then we'll just have to live with it.
Every time FarCry doesn't know the typename it has to do a findType() look up on refObjects. This can be avoided by providing the typename in your code, assuming you have it available. We really should know the typename in almost all internal core operations, so we've been trying to remove core content types (plus rules etc) dependence on refobjects to improve overall performance. We've been implementing these progressive performance enhancements ever since 6.0 was released. Note these are supposed to be transparent to users and should not be causing compatibility issues in the maintenance branch. Apologies for the inconvenience -- it looks like we've over stepped the mark on this recent revision and we should have a patch out shortly. Regards, -- geoff http://www.daemon.com.au/ -- You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry
