> Mostly because if you're looking for a field, > you're not going to look in the methods section > of the class docs, even if the "field" is > actually a method, as you proposed. Just a > differentiation between > state and behaviour that you'd sacrifice.
If I knew the data was in that class (or should be) I would definately check the methods if I didn't see it listed in the fields... For that matter, I always check the methods for what I need first before looking for fields as I consider this a best practice since a method provides encapsulation that a field doesn't, and when a method is created initially there's no need to modify code referencing the method if it's later determined that there are conditions in which a different value should be returned. So no I wouldn't lose anything. s. isaac dealey 954.927.5117 new epoch : isn't it time for a change? add features without fixtures with the onTap open source framework http://macromedia.breezecentral.com/p49777853/ http://www.sys-con.com/story/?storyid=44477&DE=1 http://www.sys-con.com/story/?storyid=45569&DE=1 http://www.fusiontap.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:196293 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
