----------------------------------------------------------- New Message on BDOTNET
----------------------------------------------------------- From: Sampath_Kumar Message 2 in Discussion Hi AnandRaj , By making a member public you are breaking the rules of OOP. It's not always true that public properties are private members. You could declare a public property called Xyz in a class which really does not have a private member called Xyz . This property could do some processing and give you the result . Secondly properties are a good way for abstraction , even if your members change your properties could still work the way it worked before . I personally feel that accessor methods , methods with a single parameter returning some type get better if they are rewritten as Properties. Remember that your code becomes more readable when you use them in expressions. int c = (obj.getX() / 5 ) - (obj.getY() * 8 ) as to int c = obj.X / 5 - obj.Y * 8 Regards Sampath ----------------------------------------------------------- To stop getting this e-mail, or change how often it arrives, go to your E-mail Settings. http://groups.msn.com/BDOTNET/_emailsettings.msnw Need help? If you've forgotten your password, please go to Passport Member Services. http://groups.msn.com/_passportredir.msnw?ppmprop=help For other questions or feedback, go to our Contact Us page. http://groups.msn.com/contact If you do not want to receive future e-mail from this MSN group, or if you received this message by mistake, please click the "Remove" link below. On the pre-addressed e-mail message that opens, simply click "Send". Your e-mail address will be deleted from this group's mailing list. mailto:[EMAIL PROTECTED]
