By bloid
via rickyclarkson.blogspot.com
Published: Feb 20 2007 / 14:23
While I think there should be some language change to make properties really useful, it's worth looking at how close we can get to properties without changing the language, to work out what needs changing.
-
Wyse CEO to Discuss Leading Trends in Mobility and Cloud Computing at the Stifel Nicolaus Technology & Telecom Conference 2012
-
The New 'Too Big to Fail': How Google, Tech Companies Are Transforming the Economy
-
Jelastic vs. Heroku
-
Bloomberg Open Sources its Market Data Distribution Technology
-
8 Features That Could Make Windows 8 Great
-
Comparing Heap Dumps with NetBeans 7.1
Comments
Ricky Clarkson replied ago:
Suppose I should vote for this. ;)
sproket replied ago:
I still don't understand this obsession with adding properties in Java. It was a dumb idea in VB and it's a dumb idea in C#. Why should Java follow dumb ideas?
Could someone supply a clear example of how this benefits anyone?
Ricky Clarkson replied ago:
Properties remove the readability price that we currently pay for using accessors instead of public fields.
Properties remove the code duplication price that we currently pay for getters and setters. That price is better measured in time to read code than keypresses.
sproketboy replied ago:
See comments in your blog since this crud service doesn't support formatting.
Voters For This Link (5)
Voters Against This Link (0)