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.
cheers, barneyb On Wed, 23 Feb 2005 18:37:09 -0500, S. Isaac Dealey <[EMAIL PROTECTED]> wrote: > I'm not sure why having it listed as a function in the documentation > would be terribly bad... especially if it is a function and not a > variable... I'd use a hint attribute to indicate the purpose of the > function. I could see some developers thinking it was an odd practice, > but I'd be hard pressed to imagine the developer for whom it was a > challenge to decypher. -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 50 invites. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:196273 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
