True, if you just change the value of a field directly like Czar Flavius says, no "action" is taken after the change because the functions or methods within the type are called after the change. In this case, it is better to have a set/get method/function that does the change, updates whatever it needs to and can also do bounds checking on the parameter as an extra precaution.
That being said, there are cases where Czar's example is valid and basically safe. ;)
Russell
That being said, there are cases where Czar's example is valid and basically safe. ;)
Russell