<?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/"
	
	xmlns:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	
	>
<channel>
	<title>
	Comments on: Large initializers/ctors?	</title>
	<atom:link href="https://www.robg3d.com/2012/01/large-initializersctors/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.robg3d.com/2012/01/large-initializersctors/</link>
	<description>Blog of Rob Galanakis (@robgalanakis)</description>
	<lastBuildDate>Tue, 14 Feb 2012 12:03:53 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.4.1</generator>
	<item>
		<title>
		By: Rob Galanakis		</title>
		<link>https://www.robg3d.com/2012/01/large-initializersctors/#comment-8199</link>

		<dc:creator><![CDATA[Rob Galanakis]]></dc:creator>
		<pubDate>Tue, 14 Feb 2012 12:03:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.robg3d.com/?p=847#comment-8199</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.robg3d.com/2012/01/large-initializersctors/#comment-8197&quot;&gt;Ben Sizer&lt;/a&gt;.

Whoops you&#039;re right. I should be adding &#039;btn&#039; to FooControl somewhere (so it would be &quot;Button(&#039;PressMe!!&#039;, self)&quot;). I&#039;ve fixed the post. Does it make more sense now?]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.robg3d.com/2012/01/large-initializersctors/#comment-8197">Ben Sizer</a>.</p>
<p>Whoops you&#8217;re right. I should be adding &#8216;btn&#8217; to FooControl somewhere (so it would be &#8220;Button(&#8216;PressMe!!&#8217;, self)&#8221;). I&#8217;ve fixed the post. Does it make more sense now?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Rob Galanakis		</title>
		<link>https://www.robg3d.com/2012/01/large-initializersctors/#comment-8198</link>

		<dc:creator><![CDATA[Rob Galanakis]]></dc:creator>
		<pubDate>Tue, 14 Feb 2012 12:01:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.robg3d.com/?p=847#comment-8198</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.robg3d.com/2012/01/large-initializersctors/#comment-8196&quot;&gt;Ben Sizer&lt;/a&gt;.

Done, sorry about that.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.robg3d.com/2012/01/large-initializersctors/#comment-8196">Ben Sizer</a>.</p>
<p>Done, sorry about that.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Ben Sizer		</title>
		<link>https://www.robg3d.com/2012/01/large-initializersctors/#comment-8197</link>

		<dc:creator><![CDATA[Ben Sizer]]></dc:creator>
		<pubDate>Tue, 14 Feb 2012 11:37:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.robg3d.com/?p=847#comment-8197</guid>

					<description><![CDATA[What stops Python from destroying btn in the latter case? btn may have a reference to FooControl.onClick, but there don&#039;t appear to be any references to btn, which makes me think that whether it gets destroyed or not is down to an implementation detail in the addListener() functionality.]]></description>
			<content:encoded><![CDATA[<p>What stops Python from destroying btn in the latter case? btn may have a reference to FooControl.onClick, but there don&#8217;t appear to be any references to btn, which makes me think that whether it gets destroyed or not is down to an implementation detail in the addListener() functionality.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Ben Sizer		</title>
		<link>https://www.robg3d.com/2012/01/large-initializersctors/#comment-8196</link>

		<dc:creator><![CDATA[Ben Sizer]]></dc:creator>
		<pubDate>Tue, 14 Feb 2012 11:33:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.robg3d.com/?p=847#comment-8196</guid>

					<description><![CDATA[It&#039;s hard to read the example as the code loses its formatting. Are you able to fix it?]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s hard to read the example as the code loses its formatting. Are you able to fix it?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Rob Galanakis		</title>
		<link>https://www.robg3d.com/2012/01/large-initializersctors/#comment-7924</link>

		<dc:creator><![CDATA[Rob Galanakis]]></dc:creator>
		<pubDate>Fri, 27 Jan 2012 22:09:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.robg3d.com/?p=847#comment-7924</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.robg3d.com/2012/01/large-initializersctors/#comment-7921&quot;&gt;Daniel&lt;/a&gt;.

Yeah I wish lambdas looked nicer in python (like, say, C#)... they&#039;re so clunky. However, the very nicer inner def usage makes these larger inner functions much more appealing. Having to write &#039;Action&lt;string, int, int&gt; inner = (a, b, c) =&gt; {...}&#039; for an inner function is hideous, but IMO &#039;(a, b, c) =&gt; ...&#039; is really, really nice.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.robg3d.com/2012/01/large-initializersctors/#comment-7921">Daniel</a>.</p>
<p>Yeah I wish lambdas looked nicer in python (like, say, C#)&#8230; they&#8217;re so clunky. However, the very nicer inner def usage makes these larger inner functions much more appealing. Having to write &#8216;Action<string, int, int> inner = (a, b, c) => {&#8230;}&#8217; for an inner function is hideous, but IMO &#8216;(a, b, c) => &#8230;&#8217; is really, really nice.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Daniel		</title>
		<link>https://www.robg3d.com/2012/01/large-initializersctors/#comment-7921</link>

		<dc:creator><![CDATA[Daniel]]></dc:creator>
		<pubDate>Fri, 27 Jan 2012 19:01:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.robg3d.com/?p=847#comment-7921</guid>

					<description><![CDATA[I prefer to keep namespaces uncluttered, especially when your only form of information hiding at the class level is name mangling and politeness on the part of your clients.

Plus as you say, it&#039;s not much fun to rely on calling a set of methods, quite possibly in a fixed order, before you&#039;ve actually got valid objects. It feels brittle. I quite like using builder-like patterns in compiled languages to allow both division of code and ensure well-formed objects, but that&#039;s not particularly relevant.

Closures are in general one of the nicer ways to store state in Python, IMO. Were the lambda feature less... interesting?... in this language I&#039;d even balk at inner functions. The function definition boilerplate doesn&#039;t really add anything.]]></description>
			<content:encoded><![CDATA[<p>I prefer to keep namespaces uncluttered, especially when your only form of information hiding at the class level is name mangling and politeness on the part of your clients.</p>
<p>Plus as you say, it&#8217;s not much fun to rely on calling a set of methods, quite possibly in a fixed order, before you&#8217;ve actually got valid objects. It feels brittle. I quite like using builder-like patterns in compiled languages to allow both division of code and ensure well-formed objects, but that&#8217;s not particularly relevant.</p>
<p>Closures are in general one of the nicer ways to store state in Python, IMO. Were the lambda feature less&#8230; interesting?&#8230; in this language I&#8217;d even balk at inner functions. The function definition boilerplate doesn&#8217;t really add anything.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
