I still fail to understand why it's considered messy / nasty. > If you let the 'final' part of 'public static final' weigh > in > slightly, then Isaac's proposal kind of gives you static. > Because > it's a method not a variable, there is only one instance > (so it's a > class "thing"), you can't change it like a non-final > variable. It's > messy and nasty, which is why I prefer to just use a > variable in the > 'this' scope.
> cheers, > barneyb > On Wed, 23 Feb 2005 17:04:35 -0500, Joe Rinehart > <[EMAIL PROTECTED]> wrote: >> That doesn't really cover "static," though - what makes a >> static >> member static is that it belongs to the type instead of >> one instance >> of a type. I.e.: >> >> InstanceOne.StaticVar = 1 >> InstanceTwo.StaticVar = 2 >> >> <!--- Would show "2" if we had statics ---> >> <cfoutput>#InstanceOne.StaticVar#</cfoutput> 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:196294 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
