> fyi, here is the link i was referring to (sorry should have posted it
> before):
>
> http://www.chapter31.com/2007/06/14/using-variablesinstance-inside-your-components/
Oh yeah... Michael wasn't recommending a separate struct for each class
in the inheritance chain (as far as I can tell). He was just saying that,
since it's an option, you might not want to put composed objects in the
instance structure so that if you want to debug the instance data with a
dump, you can get just the simple values in your dump without having to
also get those other objects.
I tend to do that also, simple values go in the properties struct (I
don't remember if it's called "instance" - I don't generally reference
it directly), and other objects get put directly into the variables
scope next to the private functions. Although in my case I don't think
it was that deliberate, I think I just "had a feeling" it would be
better to do it that way and started doing it and then it became habit.
It's interesting to see other folks now writing blogs explaining that
they do the same thing and that they have described specific reasons for
it that I hadn't really thought of at the time. :)
--
s. isaac dealey ^ new epoch
isn't it time for a change?
ph: 781.769.0723
http://onTap.riaforge.org/blog
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to
date
Get the Free Trial
http://ad.doubleclick.net/clk;203748912;27390454;j
Archive:
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:312493
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
