Printable View
What's wrong with having a public variable in a class? I'm not asking what are the advantages of having a property, but why shouldnt we have a public variable?
I was analyzing a small project with Project Analyzer and it said:
"Variables that aren't Private should be avioded in classes. Read/Write access to a Class's memeber variables should only be allowed via properties."
why!?!:confused:
The idea is aimed at application development teams really, where Joe can work on parts of an app with variables named X and Y, and Bob next door can work on different parts of the same app and not care if his variable names are unique from Joe's. Basically variable scoping is a development safety tool (at least imo).
When developing large applications, it is unsafe to allow non-private variables in a class module.
The value of the variable can be changed without your application knowing it has been changed. With properties, however, your application knows when a statement is setting or retrieving the value of a property and you can run any extra processing required before returning or setting the property value for the calling statement.
Hope this clarifies this issue...:D
Catch you later!
I always use public variables when I can be sure that I cannot create an error just by setting that variable to an unexpected value.
I use properties when I want to do data validation, or run some specialized code when I want to change a value.
I dont see what variable scope has to do with it. Wouldn't Joe and Bob be working on different classes?Quote:
Posted by Slow_Learner:
The idea is aimed at application development teams really, where Joe can work on parts of an app with variables named X and Y, and Bob next door can work on different parts of the same app and not care if his variable names are unique from Joe's. Basically variable scoping is a development safety tool (at least imo).
I agree 'Hu Flung Dung', when I read Slow_Learner's post, I just thought to myself..."what the f*** is this guy on about?!"
Variable scoping has nothing to do with team development and besides, team programmers almost always work on seperate classes as 'Hu Flung Dung' already stated.
Good luck...;)
Like said before, to validate the data being set. Lets say you have a variable that you only want to be set to a number between 1 and 10. But it is an integer, and we know that there are a lot of numbers that the integer can hold. How do we control so that it only holds the numbers between 1 and 10, we use a property. When someone sets the propery to 100, you know it is out of range so you go ahead and set the value to 10 for the variable, thus illiminating errors later when processing code that thinks it is only going to get a number from 1 to 10. You can also choose to raise an error, raise an event in your class, or just disreguard the value. With a property, you get all those options. You don't get those with a public variable.
Well explained hellswraith...with a nice example too! :p
This explained it :)Quote:
Originally posted by Hu Flung Dung
I always use public variables when I can be sure that I cannot create an error just by setting that variable to an unexpected value.
That's what I was doing. This stupid project analyzer was saying I'm evil and I should die because I'm a bad coder:p
This just comes from me not knowing what I'm talking about. :)Quote:
Originally posted by Hu Flung Dung
II dont see what variable scope has to do with it. Wouldn't Joe and Bob be working on different classes?