Women in Technology

Hear us Roar



Article:
  10 Reasons We Need Java 3.0
Subject:   pros and cons of properties
Date:   2002-08-12 11:37:33
From:   jacyg
Response to: pros and cons of properties

The biggest problem that I see with properties is that they are just another syntax for a method, but rather than enhancing clarity, they decrease it. For example, there is nothing in the signature of a C# class (C# being a good mainstream model for properties) that makes it clear that it is read-only, write-only, or read-write. However, the presence or absence of the appropriate get() and/or set() method makes that abundantly clear. Yes, it may take a few more characters, but the generated code is the same. We should not be introducing new features in to the language that accomplish the same thing other features do. The willingness to do so will eventually render the language confusing and bloated, rather than streamlined and easy to understand. The best example I can think of is the number of ways to specify a String in Windows C++ development. Do you think a multiplicity of ways to do that same task makes the language better? I don't.