<?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"
	>
<channel>
	<title>Comments on: Using Sections in Java Classes</title>
	<atom:link href="http://www.blog.dannynet.net/archives/36/feed" rel="self" type="application/rss+xml" />
	<link>http://www.blog.dannynet.net/archives/36</link>
	<description>Pondering Programming and Poetry</description>
	<pubDate>Sat, 04 Feb 2012 22:15:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Eugene Kuleshov</title>
		<link>http://www.blog.dannynet.net/archives/36#comment-8425</link>
		<dc:creator>Eugene Kuleshov</dc:creator>
		<pubDate>Fri, 15 Dec 2006 23:17:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.blog.dannynet.net/?p=36#comment-8425</guid>
		<description>I agree with murphee. Annotations are much more suitable for categorization. You can have more then one parallel classifications, and then use IDE to visualize code slice interesting in particular moment. 

Also see FEAT and ConcernMapper tools for Eclipse:
http://www.cs.ubc.ca/labs/spl/projects/feat/
http://www.cs.mcgill.ca/~martin/cm/</description>
		<content:encoded><![CDATA[<p>I agree with murphee. Annotations are much more suitable for categorization. You can have more then one parallel classifications, and then use IDE to visualize code slice interesting in particular moment. </p>
<p>Also see FEAT and ConcernMapper tools for Eclipse:<br />
<a href="http://www.cs.ubc.ca/labs/spl/projects/feat/" rel="nofollow">http://www.cs.ubc.ca/labs/spl/projects/feat/</a><br />
<a href="http://www.cs.mcgill.ca/~martin/cm/" rel="nofollow">http://www.cs.mcgill.ca/~martin/cm/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danny</title>
		<link>http://www.blog.dannynet.net/archives/36#comment-93</link>
		<dc:creator>Danny</dc:creator>
		<pubDate>Fri, 06 Jan 2006 13:26:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.blog.dannynet.net/?p=36#comment-93</guid>
		<description>Annotations could indeed be used to categorize methods; but that wasn't my intention. I'm looking for a way to bring (visible) structure to classes. Besides, you can't do things like access control, inheriting and documenting as well when you would use annotations for this. I'm not a big fan anyway of 'using annotations for anything new in Java we come up with from now on'...</description>
		<content:encoded><![CDATA[<p>Annotations could indeed be used to categorize methods; but that wasn&#8217;t my intention. I&#8217;m looking for a way to bring (visible) structure to classes. Besides, you can&#8217;t do things like access control, inheriting and documenting as well when you would use annotations for this. I&#8217;m not a big fan anyway of &#8216;using annotations for anything new in Java we come up with from now on&#8217;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: murphee</title>
		<link>http://www.blog.dannynet.net/archives/36#comment-92</link>
		<dc:creator>murphee</dc:creator>
		<pubDate>Tue, 03 Jan 2006 14:26:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.blog.dannynet.net/?p=36#comment-92</guid>
		<description>Why add to the Java syntax? You could use Annotations to add Category Metadata to methods.</description>
		<content:encoded><![CDATA[<p>Why add to the Java syntax? You could use Annotations to add Category Metadata to methods.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

