<?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: How to Think About Object Oriented Design</title>
	<atom:link href="http://blogs.teamb.com/craigstuntz/2005/06/29/20023/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.teamb.com/craigstuntz/2005/06/29/20023/</link>
	<description>News of interest to Delphi, .NET, and InterBase programmers</description>
	<pubDate>Tue, 06 Jan 2009 20:10:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Lars</title>
		<link>http://blogs.teamb.com/craigstuntz/2005/06/29/20023/#comment-229</link>
		<dc:creator>Lars</dc:creator>
		<pubDate>Mon, 16 Oct 2006 23:09:12 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.teamb.com/craigstuntz/2005/06/29/20023/#comment-229</guid>
		<description>Object orientation in &lt;a title="Borland Delphi home page" href="http://www.borland.com/delphi" &gt;Delphi&lt;/a&gt; is mainly procedural programming with SELF being passed as a hidden parameter and a few other /syntactic sugars/ going on under the hood.&lt;br&gt;&lt;br&gt;Enough syntactic sugars to make it worthwhile. You can really have code reuse go on with procedural code to - it just gets messy because you have to pass in more parameters into the procedures. With OO code, it hides the self paramater and the get/set properties are hidden using the assign := operator.  &lt;br&gt;&lt;br&gt;Inhertance? again, it can be done in procedural code by reusing subprocedures - just that OO tidies it up and makes it neater.</description>
		<content:encoded><![CDATA[<p>Object orientation in <a title="Borland Delphi home page" href="http://www.borland.com/delphi" >Delphi</a> is mainly procedural programming with SELF being passed as a hidden parameter and a few other /syntactic sugars/ going on under the hood.</p>
<p>Enough syntactic sugars to make it worthwhile. You can really have code reuse go on with procedural code to - it just gets messy because you have to pass in more parameters into the procedures. With OO code, it hides the self paramater and the get/set properties are hidden using the assign := operator.  </p>
<p>Inhertance? again, it can be done in procedural code by reusing subprocedures - just that OO tidies it up and makes it neater.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: orwah</title>
		<link>http://blogs.teamb.com/craigstuntz/2005/06/29/20023/#comment-159</link>
		<dc:creator>orwah</dc:creator>
		<pubDate>Tue, 26 Jul 2005 05:20:01 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.teamb.com/craigstuntz/2005/06/29/20023/#comment-159</guid>
		<description>the most important think is :&lt;br&gt;reusibility &lt;br&gt;then :&lt;br&gt;extedibility &lt;br&gt;&lt;br&gt;so oo design mean to separate between class user and class writer &lt;br&gt;&lt;br&gt;-----------&lt;br&gt;orwah issa</description>
		<content:encoded><![CDATA[<p>the most important think is :<br />
<br />reusibility<br />
<br />then :<br />
<br />extedibility </p>
<p>so oo design mean to separate between class user and class writer </p>
<p>&#8212;&#8212;&#8212;&#8211;<br />
<br />orwah issa</p>
]]></content:encoded>
	</item>
</channel>
</rss>
