<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Structures in Java</title>
	<atom:link href="http://nutrun.com/weblog/structures-in-java/feed/" rel="self" type="application/rss+xml" />
	<link>http://nutrun.com/weblog/structures-in-java/</link>
	<description>nutrun</description>
	<lastBuildDate>Mon, 28 Jun 2010 07:35:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: James Law</title>
		<link>http://nutrun.com/weblog/structures-in-java/comment-page-1/#comment-231</link>
		<dc:creator>James Law</dc:creator>
		<pubDate>Sat, 04 Nov 2006 12:24:11 +0000</pubDate>
		<guid isPermaLink="false">http://new-site.nutrun.com/?p=61#comment-231</guid>
		<description>Akshay,
As a fellow setter eradicator, check out access=field in hibernate...

J</description>
		<content:encoded><![CDATA[<p>Akshay,<br />
As a fellow setter eradicator, check out access=field in hibernate&#8230;</p>
<p>J</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean-Marie Dautelle</title>
		<link>http://nutrun.com/weblog/structures-in-java/comment-page-1/#comment-226</link>
		<dc:creator>Jean-Marie Dautelle</dc:creator>
		<pubDate>Fri, 03 Nov 2006 13:53:30 +0000</pubDate>
		<guid isPermaLink="false">http://new-site.nutrun.com/?p=61#comment-226</guid>
		<description>C struct/union are intended for memory mapping.
The equivalent capability for Java is currently provided by Javolution Struct/Union classes (http://javolution.org/api/javolution/io/Struct.html)</description>
		<content:encoded><![CDATA[<p>C struct/union are intended for memory mapping.<br />
The equivalent capability for Java is currently provided by Javolution Struct/Union classes (<a href="http://javolution.org/api/javolution/io/Struct.html" rel="nofollow">http://javolution.org/api/javolution/io/Struct.html</a>)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ricky Clarkson</title>
		<link>http://nutrun.com/weblog/structures-in-java/comment-page-1/#comment-225</link>
		<dc:creator>Ricky Clarkson</dc:creator>
		<pubDate>Thu, 02 Nov 2006 21:11:00 +0000</pubDate>
		<guid isPermaLink="false">http://new-site.nutrun.com/?p=61#comment-225</guid>
		<description>&#039;Dumb&#039; Getters and setters aren&#039;t needed in internal code, only library code, as IDEs can automatically refactor public fields to private fields with accessors.

Delphi (and C#?) provide properties, which allow you to specify what happens when a &#039;variable&#039; is written to or read from.

Netbeans (not that I run it) has refactoring scripts, which you can give to your clients when you change your library - they run it over their codebase and the IDE applies the refactors to match the change that you made.

Obviously this is of limited use because it doesn&#039;t work on all 3 Java IDEs.</description>
		<content:encoded><![CDATA[<p>&#8216;Dumb&#8217; Getters and setters aren&#8217;t needed in internal code, only library code, as IDEs can automatically refactor public fields to private fields with accessors.</p>
<p>Delphi (and C#?) provide properties, which allow you to specify what happens when a &#8216;variable&#8217; is written to or read from.</p>
<p>Netbeans (not that I run it) has refactoring scripts, which you can give to your clients when you change your library &#8211; they run it over their codebase and the IDE applies the refactors to match the change that you made.</p>
<p>Obviously this is of limited use because it doesn&#8217;t work on all 3 Java IDEs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Guillaume Laforge</title>
		<link>http://nutrun.com/weblog/structures-in-java/comment-page-1/#comment-230</link>
		<dc:creator>Guillaume Laforge</dc:creator>
		<pubDate>Thu, 02 Nov 2006 17:51:21 +0000</pubDate>
		<guid isPermaLink="false">http://new-site.nutrun.com/?p=61#comment-230</guid>
		<description>Even with an IDE, getters and setters are painful, even for your eyes. Groovy decided to make this simpler with auto-generated getters and setters:

class Line {
  int width
  String color
}</description>
		<content:encoded><![CDATA[<p>Even with an IDE, getters and setters are painful, even for your eyes. Groovy decided to make this simpler with auto-generated getters and setters:</p>
<p>class Line {<br />
  int width<br />
  String color<br />
}</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: n8han</title>
		<link>http://nutrun.com/weblog/structures-in-java/comment-page-1/#comment-229</link>
		<dc:creator>n8han</dc:creator>
		<pubDate>Thu, 02 Nov 2006 16:26:07 +0000</pubDate>
		<guid isPermaLink="false">http://new-site.nutrun.com/?p=61#comment-229</guid>
		<description>We need something like ruby&#039;s attr_accessor method. I&#039;ve always hated writing (or generating, or just seeing) brain-dead getters and setters for Java, but I don&#039;t make fields public because 1) people would freak out 2) sometimes you add unanticipated logic to an existing getter or setter.</description>
		<content:encoded><![CDATA[<p>We need something like ruby&#8217;s attr_accessor method. I&#8217;ve always hated writing (or generating, or just seeing) brain-dead getters and setters for Java, but I don&#8217;t make fields public because 1) people would freak out 2) sometimes you add unanticipated logic to an existing getter or setter.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Akshay</title>
		<link>http://nutrun.com/weblog/structures-in-java/comment-page-1/#comment-228</link>
		<dc:creator>Akshay</dc:creator>
		<pubDate>Thu, 02 Nov 2006 13:00:10 +0000</pubDate>
		<guid isPermaLink="false">http://new-site.nutrun.com/?p=61#comment-228</guid>
		<description>I am also sick of frameworks like webwork and hibernate which impose the need of getters and setters on an object. In an ideal world a single object domain object should be used across all layers from db to presentation without breaking any encapsulation.</description>
		<content:encoded><![CDATA[<p>I am also sick of frameworks like webwork and hibernate which impose the need of getters and setters on an object. In an ideal world a single object domain object should be used across all layers from db to presentation without breaking any encapsulation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Brown</title>
		<link>http://nutrun.com/weblog/structures-in-java/comment-page-1/#comment-227</link>
		<dc:creator>Chris Brown</dc:creator>
		<pubDate>Thu, 02 Nov 2006 11:58:50 +0000</pubDate>
		<guid isPermaLink="false">http://new-site.nutrun.com/?p=61#comment-227</guid>
		<description>This is why superior languages like C# have them.</description>
		<content:encoded><![CDATA[<p>This is why superior languages like C# have them.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
