<?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: Sealed classes in .NET &#8230; but why?</title>
	<atom:link href="http://www.chrishowie.com/2006/07/04/sealed-classes-in-net-but-why/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.chrishowie.com/2006/07/04/sealed-classes-in-net-but-why/</link>
	<description>Trading social skills for technical prowess since 1994</description>
	<pubDate>Tue, 06 Jan 2009 04:55:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chris</title>
		<link>http://www.chrishowie.com/2006/07/04/sealed-classes-in-net-but-why/comment-page-1/#comment-7958</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Fri, 10 Oct 2008 03:05:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrishowie.com/2006/07/04/sealed-classes-in-net-but-why/#comment-7958</guid>
		<description>@Jeevan:

If the CLR does in fact optimize the layout of the fields across an entire hierarchy, it could certainly ensure that the position of the string fields remains the same.</description>
		<content:encoded><![CDATA[<p>@Jeevan:</p>
<p>If the CLR does in fact optimize the layout of the fields across an entire hierarchy, it could certainly ensure that the position of the string fields remains the same.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeevan</title>
		<link>http://www.chrishowie.com/2006/07/04/sealed-classes-in-net-but-why/comment-page-1/#comment-7957</link>
		<dc:creator>Jeevan</dc:creator>
		<pubDate>Mon, 06 Oct 2008 06:02:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrishowie.com/2006/07/04/sealed-classes-in-net-but-why/#comment-7957</guid>
		<description>I am not sure if this is the correct answer, but I think this is not just because of the immutability that the System.String class is sealed. To improve performance, it is required that the CLR should know the exact layout of the fields defined within the String class (CLR accesses them directly, unlike other classes). Now, if someone derives a class from String and defines his/her own fields, it would be impossible for the CLR to make any assumptions about the internal layout of the class. 

Hope this helps. And if anyone thinks this is not the fact, I would be very happy to know the actual reason.</description>
		<content:encoded><![CDATA[<p>I am not sure if this is the correct answer, but I think this is not just because of the immutability that the System.String class is sealed. To improve performance, it is required that the CLR should know the exact layout of the fields defined within the String class (CLR accesses them directly, unlike other classes). Now, if someone derives a class from String and defines his/her own fields, it would be impossible for the CLR to make any assumptions about the internal layout of the class. </p>
<p>Hope this helps. And if anyone thinks this is not the fact, I would be very happy to know the actual reason.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
