<?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 for Porkrind Dot Org Missives</title>
	<atom:link href="http://porkrind.org/missives/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://porkrind.org/missives</link>
	<description>Portal For The Masses</description>
	<lastBuildDate>Thu, 26 Jan 2012 00:00:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on The Core Memory Module from my dad&#8217;s homebuilt PDP-11/05 by Frank</title>
		<link>http://porkrind.org/missives/the-core-memory-module-from-my-dads-homebuilt-pdp-1105/comment-page-1/#comment-511</link>
		<dc:creator>Frank</dc:creator>
		<pubDate>Thu, 26 Jan 2012 00:00:39 +0000</pubDate>
		<guid isPermaLink="false">http://porkrind.org/missives/?p=291#comment-511</guid>
		<description>Your guess that core memory was protected since fragile is correct, but not the only reason.
The fragility was acceptable, I&#039;ve travelled large distances with core memory in my car and upon arrival all the data would still be there. People were the problem, especially types who wanted to clean core memory with compressed air.
The protection also helped to keep a constant temperature, core memory being very temperature sensitive.
The very early core memory even required good programming to avoid reading the same memory location too often (in a loop). The cores being read and rewritten would heat up and lose the data. 
That is why core memory would always have a parity bit ( and parity bit error light) to indicate such errors.
Awesome job to build this thing from various components! DEC as well as the russians who copied it worked with large teams.</description>
		<content:encoded><![CDATA[<p>Your guess that core memory was protected since fragile is correct, but not the only reason.<br />
The fragility was acceptable, I&#8217;ve travelled large distances with core memory in my car and upon arrival all the data would still be there. People were the problem, especially types who wanted to clean core memory with compressed air.<br />
The protection also helped to keep a constant temperature, core memory being very temperature sensitive.<br />
The very early core memory even required good programming to avoid reading the same memory location too often (in a loop). The cores being read and rewritten would heat up and lose the data.<br />
That is why core memory would always have a parity bit ( and parity bit error light) to indicate such errors.<br />
Awesome job to build this thing from various components! DEC as well as the russians who copied it worked with large teams.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Closures In Straight C by hopia</title>
		<link>http://porkrind.org/missives/closures-in-straight-c/comment-page-1/#comment-485</link>
		<dc:creator>hopia</dc:creator>
		<pubDate>Wed, 14 Dec 2011 17:25:33 +0000</pubDate>
		<guid isPermaLink="false">http://porkrind.org/missives2/?p=13#comment-485</guid>
		<description>As a long time C developer, I totally agree that callbacks and cookies are the closest thing to closures in the C world.  Of course, we all know it&#039;s not part of the language, so it&#039;s not as intuitive and natural to use.  However, I think the point of the article is that C developers can and have been able to &quot;simulate&quot; the behavior.</description>
		<content:encoded><![CDATA[<p>As a long time C developer, I totally agree that callbacks and cookies are the closest thing to closures in the C world.  Of course, we all know it&#8217;s not part of the language, so it&#8217;s not as intuitive and natural to use.  However, I think the point of the article is that C developers can and have been able to &#8220;simulate&#8221; the behavior.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Core Memory Module from my dad&#8217;s homebuilt PDP-11/05 by Theodric</title>
		<link>http://porkrind.org/missives/the-core-memory-module-from-my-dads-homebuilt-pdp-1105/comment-page-1/#comment-414</link>
		<dc:creator>Theodric</dc:creator>
		<pubDate>Wed, 23 Nov 2011 19:50:34 +0000</pubDate>
		<guid isPermaLink="false">http://porkrind.org/missives/?p=291#comment-414</guid>
		<description>That&#039;s amazingly cool. You see a lot of FPGA reimplementations of (particularly) DEC stuff, and I have a piece that used to live in a PDP-8 home-built in a wooden box from *cough* &#039;relocated offsite&#039; boards by a DEC engineer, but it&#039;s quite spectacular to see someone go to the effort of actually recreating a system at the component level. Mega kudos to your dad.</description>
		<content:encoded><![CDATA[<p>That&#8217;s amazingly cool. You see a lot of FPGA reimplementations of (particularly) DEC stuff, and I have a piece that used to live in a PDP-8 home-built in a wooden box from *cough* &#8216;relocated offsite&#8217; boards by a DEC engineer, but it&#8217;s quite spectacular to see someone go to the effort of actually recreating a system at the component level. Mega kudos to your dad.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Core Memory Module from my dad&#8217;s homebuilt PDP-11/05 by Rod Smallwood</title>
		<link>http://porkrind.org/missives/the-core-memory-module-from-my-dads-homebuilt-pdp-1105/comment-page-1/#comment-413</link>
		<dc:creator>Rod Smallwood</dc:creator>
		<pubDate>Wed, 23 Nov 2011 11:17:06 +0000</pubDate>
		<guid isPermaLink="false">http://porkrind.org/missives/?p=291#comment-413</guid>
		<description>Who is this guy?  
He designed and built a PDP-11 clone by himself?
Truly amazing!</description>
		<content:encoded><![CDATA[<p>Who is this guy?<br />
He designed and built a PDP-11 clone by himself?<br />
Truly amazing!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Core Memory Module from my dad&#8217;s homebuilt PDP-11/05 by Lyle Bickley</title>
		<link>http://porkrind.org/missives/the-core-memory-module-from-my-dads-homebuilt-pdp-1105/comment-page-1/#comment-408</link>
		<dc:creator>Lyle Bickley</dc:creator>
		<pubDate>Wed, 23 Nov 2011 00:24:54 +0000</pubDate>
		<guid isPermaLink="false">http://porkrind.org/missives/?p=291#comment-408</guid>
		<description>Terrific! Your Dad creating his own PDP-11 from scratch - particularly via wirewrap - took a lot of good design  and vast quantities of patience! Bringing it &quot;back to life&quot; sounds like a super father-son project!!!</description>
		<content:encoded><![CDATA[<p>Terrific! Your Dad creating his own PDP-11 from scratch &#8211; particularly via wirewrap &#8211; took a lot of good design  and vast quantities of patience! Bringing it &#8220;back to life&#8221; sounds like a super father-son project!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Core Memory Module from my dad&#8217;s homebuilt PDP-11/05 by Pádraig Brady</title>
		<link>http://porkrind.org/missives/the-core-memory-module-from-my-dads-homebuilt-pdp-1105/comment-page-1/#comment-400</link>
		<dc:creator>Pádraig Brady</dc:creator>
		<pubDate>Mon, 21 Nov 2011 23:26:19 +0000</pubDate>
		<guid isPermaLink="false">http://porkrind.org/missives/?p=291#comment-400</guid>
		<description>Very cool. You might find this interesting too http://www.corememoryshield.com/</description>
		<content:encoded><![CDATA[<p>Very cool. You might find this interesting too <a href="http://www.corememoryshield.com/" rel="nofollow">http://www.corememoryshield.com/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Core Memory Module from my dad&#8217;s homebuilt PDP-11/05 by Pinky</title>
		<link>http://porkrind.org/missives/the-core-memory-module-from-my-dads-homebuilt-pdp-1105/comment-page-1/#comment-397</link>
		<dc:creator>Pinky</dc:creator>
		<pubDate>Mon, 21 Nov 2011 08:43:46 +0000</pubDate>
		<guid isPermaLink="false">http://porkrind.org/missives/?p=291#comment-397</guid>
		<description>Thanks for posting these pics. Amazing!</description>
		<content:encoded><![CDATA[<p>Thanks for posting these pics. Amazing!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Core Memory Module from my dad&#8217;s homebuilt PDP-11/05 by Jose Rodriguez</title>
		<link>http://porkrind.org/missives/the-core-memory-module-from-my-dads-homebuilt-pdp-1105/comment-page-1/#comment-396</link>
		<dc:creator>Jose Rodriguez</dc:creator>
		<pubDate>Mon, 21 Nov 2011 08:37:31 +0000</pubDate>
		<guid isPermaLink="false">http://porkrind.org/missives/?p=291#comment-396</guid>
		<description>Awesome! I want your dad to be my uncle!</description>
		<content:encoded><![CDATA[<p>Awesome! I want your dad to be my uncle!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Core Memory Module from my dad&#8217;s homebuilt PDP-11/05 by ori</title>
		<link>http://porkrind.org/missives/the-core-memory-module-from-my-dads-homebuilt-pdp-1105/comment-page-1/#comment-395</link>
		<dc:creator>ori</dc:creator>
		<pubDate>Mon, 21 Nov 2011 08:12:00 +0000</pubDate>
		<guid isPermaLink="false">http://porkrind.org/missives/?p=291#comment-395</guid>
		<description>This is way cool. Your dad sounds awesome.</description>
		<content:encoded><![CDATA[<p>This is way cool. Your dad sounds awesome.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Core Memory Module from my dad&#8217;s homebuilt PDP-11/05 by david</title>
		<link>http://porkrind.org/missives/the-core-memory-module-from-my-dads-homebuilt-pdp-1105/comment-page-1/#comment-393</link>
		<dc:creator>david</dc:creator>
		<pubDate>Mon, 21 Nov 2011 07:13:41 +0000</pubDate>
		<guid isPermaLink="false">http://porkrind.org/missives/?p=291#comment-393</guid>
		<description>You&#039;re right. Fixed. Thanks!</description>
		<content:encoded><![CDATA[<p>You&#8217;re right. Fixed. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Core Memory Module from my dad&#8217;s homebuilt PDP-11/05 by Nick</title>
		<link>http://porkrind.org/missives/the-core-memory-module-from-my-dads-homebuilt-pdp-1105/comment-page-1/#comment-392</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Mon, 21 Nov 2011 05:45:18 +0000</pubDate>
		<guid isPermaLink="false">http://porkrind.org/missives/?p=291#comment-392</guid>
		<description>I think you mean &quot;discrete&quot; rather than &quot;discreet&quot;.</description>
		<content:encoded><![CDATA[<p>I think you mean &#8220;discrete&#8221; rather than &#8220;discreet&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Emacs For OS X . com gets a new Mac Mini by Bill Robertson</title>
		<link>http://porkrind.org/missives/emacs-for-os-x-com-gets-a-new-mac-mini/comment-page-1/#comment-388</link>
		<dc:creator>Bill Robertson</dc:creator>
		<pubDate>Sun, 13 Nov 2011 05:11:35 +0000</pubDate>
		<guid isPermaLink="false">http://porkrind.org/missives/?p=280#comment-388</guid>
		<description>You saved Emacs for me on the mac. I was happy to give. Thanks!</description>
		<content:encoded><![CDATA[<p>You saved Emacs for me on the mac. I was happy to give. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Emacs For OS X . com gets a new Mac Mini by Arno Smit</title>
		<link>http://porkrind.org/missives/emacs-for-os-x-com-gets-a-new-mac-mini/comment-page-1/#comment-387</link>
		<dc:creator>Arno Smit</dc:creator>
		<pubDate>Sat, 12 Nov 2011 11:47:17 +0000</pubDate>
		<guid isPermaLink="false">http://porkrind.org/missives/?p=280#comment-387</guid>
		<description>Thanks for an awesome article!</description>
		<content:encoded><![CDATA[<p>Thanks for an awesome article!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Emacs For OS X . com gets a new Mac Mini by Daniel Daboczy</title>
		<link>http://porkrind.org/missives/emacs-for-os-x-com-gets-a-new-mac-mini/comment-page-1/#comment-386</link>
		<dc:creator>Daniel Daboczy</dc:creator>
		<pubDate>Sat, 12 Nov 2011 10:55:51 +0000</pubDate>
		<guid isPermaLink="false">http://porkrind.org/missives/?p=280#comment-386</guid>
		<description>We are so proud that you chose FundedByMe for your crowdfunding.
We&#039;ve been global from day one and love to see american projects reach their goals in recordtime, and also surpass them!

Daniel Daboczy/ founder of Funded By Me</description>
		<content:encoded><![CDATA[<p>We are so proud that you chose FundedByMe for your crowdfunding.<br />
We&#8217;ve been global from day one and love to see american projects reach their goals in recordtime, and also surpass them!</p>
<p>Daniel Daboczy/ founder of Funded By Me</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Calling Applescript from Perl by Caravan</title>
		<link>http://porkrind.org/missives/calling-applescript-from-perl/comment-page-1/#comment-384</link>
		<dc:creator>Caravan</dc:creator>
		<pubDate>Thu, 10 Nov 2011 15:21:54 +0000</pubDate>
		<guid isPermaLink="false">http://porkrind.org/missives2/?p=17#comment-384</guid>
		<description>I see exactly the same from Data::Dumper

&lt;pre&gt;$VAR1 = [
          &#039;osascript&#039;,
          &#039;-e&#039;,
          &#039;tell application &quot;Finder&quot;
 display dialog &quot;Hello&quot;
 end tell&#039;
        ];
&lt;/pre&gt;</description>
		<content:encoded><![CDATA[<p>I see exactly the same from Data::Dumper</p>
<pre>$VAR1 = [
          'osascript',
          '-e',
          'tell application "Finder"
 display dialog "Hello"
 end tell'
        ];
</pre>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Calling Applescript from Perl by david</title>
		<link>http://porkrind.org/missives/calling-applescript-from-perl/comment-page-1/#comment-383</link>
		<dc:creator>david</dc:creator>
		<pubDate>Thu, 10 Nov 2011 15:16:51 +0000</pubDate>
		<guid isPermaLink="false">http://porkrind.org/missives2/?p=17#comment-383</guid>
		<description>Caravan, try adding this to your script:
&lt;pre&gt;use Data::Dumper;
sub osascript($) { print Dumper([&#039;osascript&#039;, map { (&#039;-e&#039;, $_) } split(/\r/, $_[0])]); }
&lt;/pre&gt;

When I run it I get:

&lt;pre&gt;$VAR1 = [
          &#039;osascript&#039;,
          &#039;-e&#039;,
          &#039;tell application &quot;Finder&quot;
display dialog &quot;Hello&quot;
end tell&#039;
        ];
&lt;/pre&gt;

That passes the newlines embedded in the command line (which apparently works). But it makes the whole map/split part pointless (since there are no &#039;\r&#039; chars in the string to split on). At that point you may as well just do:

&lt;pre&gt;system(&#039;osascript&#039;, &#039;-e&#039;,
&#039;tell application &quot;Finder&quot;
display dialog &quot;Hello&quot;
end tell&#039;)
&lt;/pre&gt;

I haven&#039;t seen Mac::Glue before. It looks cool. I don&#039;t have a problem with Apple Events per se—I like the idea of universal API for applications. I just don&#039;t like AppleScript itself. The natural language part of it never set well with me—the whole thing feels hacky. The idea of elevating AppleEvents to native (and fairly idiomatic) Perl is a good one.</description>
		<content:encoded><![CDATA[<p>Caravan, try adding this to your script:</p>
<pre>use Data::Dumper;
sub osascript($) { print Dumper(['osascript', map { ('-e', $_) } split(/\r/, $_[0])]); }
</pre>
<p>When I run it I get:</p>
<pre>$VAR1 = [
          'osascript',
          '-e',
          'tell application "Finder"
display dialog "Hello"
end tell'
        ];
</pre>
<p>That passes the newlines embedded in the command line (which apparently works). But it makes the whole map/split part pointless (since there are no &#8216;\r&#8217; chars in the string to split on). At that point you may as well just do:</p>
<pre>system('osascript', '-e',
'tell application "Finder"
display dialog "Hello"
end tell')
</pre>
<p>I haven&#8217;t seen Mac::Glue before. It looks cool. I don&#8217;t have a problem with Apple Events per se—I like the idea of universal API for applications. I just don&#8217;t like AppleScript itself. The natural language part of it never set well with me—the whole thing feels hacky. The idea of elevating AppleEvents to native (and fairly idiomatic) Perl is a good one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Calling Applescript from Perl by Caravan</title>
		<link>http://porkrind.org/missives/calling-applescript-from-perl/comment-page-1/#comment-381</link>
		<dc:creator>Caravan</dc:creator>
		<pubDate>Thu, 10 Nov 2011 14:06:41 +0000</pubDate>
		<guid isPermaLink="false">http://porkrind.org/missives2/?p=17#comment-381</guid>
		<description>Hi David,

I didn&#039;t really think that one through.  I&#039;m working on BBEdit 9.6.3 and I have line endings set to Unix (LF) but what is actually in my script is \r. My Perl scripts created on this work on both OSX and various flavours of linux.

The reason I happened upon your page was because I&#039;m doing a project using Mac::Glue. If you are not keen on Applescript or you want to have access to Perl&#039;s text processing power and  massive back catalogue of modules, including powerful encryption Mac::Glue is brilliant. Mac::Glue is a Perl Module that allows you to Control Mac apps with Apple event terminology from Perl. 

You can write a small Applescript that runs your Perl script all it has to say is:

do shell script &quot;perl /pathto/perlscript.pl&quot;

Your Perl script can then do anything and everything that a Perl script can do and then tell a Mac application to do something with the result.</description>
		<content:encoded><![CDATA[<p>Hi David,</p>
<p>I didn&#8217;t really think that one through.  I&#8217;m working on BBEdit 9.6.3 and I have line endings set to Unix (LF) but what is actually in my script is \r. My Perl scripts created on this work on both OSX and various flavours of linux.</p>
<p>The reason I happened upon your page was because I&#8217;m doing a project using Mac::Glue. If you are not keen on Applescript or you want to have access to Perl&#8217;s text processing power and  massive back catalogue of modules, including powerful encryption Mac::Glue is brilliant. Mac::Glue is a Perl Module that allows you to Control Mac apps with Apple event terminology from Perl. </p>
<p>You can write a small Applescript that runs your Perl script all it has to say is:</p>
<p>do shell script &#8220;perl /pathto/perlscript.pl&#8221;</p>
<p>Your Perl script can then do anything and everything that a Perl script can do and then tell a Mac application to do something with the result.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Calling Applescript from Perl by david</title>
		<link>http://porkrind.org/missives/calling-applescript-from-perl/comment-page-1/#comment-380</link>
		<dc:creator>david</dc:creator>
		<pubDate>Thu, 10 Nov 2011 12:19:16 +0000</pubDate>
		<guid isPermaLink="false">http://porkrind.org/missives2/?p=17#comment-380</guid>
		<description>Caravan, you changed the \n to \r, which means your script doesn&#039;t have unix end-of-line characters. &#039;od -c &lt;i&gt;thescript.pl&lt;/i&gt;&#039; to check your end of lines. Normally Mac OS X text files use unix-style &#039;\n&#039; but if you were editing on an old Mac program (carbon based, from the pre-OS X days) then it might use the old Mac OS 9 style &#039;\r&#039; end-of-lines.

To completely fix it you could also do:
&lt;pre&gt;sub osascript($) { system ‘osascript’, map { (‘-e’, $_) } split(/[\r\n]+/, $_[0]); } 
&lt;/pre&gt;
which would handle &#039;\n&#039; (unix), &#039;\r&#039; (old-mac) and &#039;\r\n&#039; (windows) eols. It would also skip blank lines which is probably good too (-e &#039;&#039; would be pointless).</description>
		<content:encoded><![CDATA[<p>Caravan, you changed the \n to \r, which means your script doesn&#8217;t have unix end-of-line characters. &#8216;od -c <i>thescript.pl</i>&#8216; to check your end of lines. Normally Mac OS X text files use unix-style &#8216;\n&#8217; but if you were editing on an old Mac program (carbon based, from the pre-OS X days) then it might use the old Mac OS 9 style &#8216;\r&#8217; end-of-lines.</p>
<p>To completely fix it you could also do:</p>
<pre>sub osascript($) { system ‘osascript’, map { (‘-e’, $_) } split(/[\r\n]+/, $_[0]); }
</pre>
<p>which would handle &#8216;\n&#8217; (unix), &#8216;\r&#8217; (old-mac) and &#8216;\r\n&#8217; (windows) eols. It would also skip blank lines which is probably good too (-e &#8221; would be pointless).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Calling Applescript from Perl by Caravan</title>
		<link>http://porkrind.org/missives/calling-applescript-from-perl/comment-page-1/#comment-379</link>
		<dc:creator>Caravan</dc:creator>
		<pubDate>Thu, 10 Nov 2011 11:15:36 +0000</pubDate>
		<guid isPermaLink="false">http://porkrind.org/missives2/?p=17#comment-379</guid>
		<description>This works on OS X 10.5.8 for me.

&lt;pre&gt;#!/usr/bin/perl

sub osascript($) { system &#039;osascript&#039;, map { (&#039;-e&#039;, $_) } split(/\r/, $_[0]); } 
 
&amp;osascript (
 &#039;tell application &quot;Finder&quot;
 display dialog &quot;Hello&quot;
 end tell&#039;
)
&lt;/pre&gt;</description>
		<content:encoded><![CDATA[<p>This works on OS X 10.5.8 for me.</p>
<pre>#!/usr/bin/perl

sub osascript($) { system 'osascript', map { ('-e', $_) } split(/\r/, $_[0]); } 

&amp;osascript (
 'tell application "Finder"
 display dialog "Hello"
 end tell'
)
</pre>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What I had to do to get Snow Leopard to install on my MacBook by Ethagnawl</title>
		<link>http://porkrind.org/missives/what-i-had-to-do-to-get-snow-leopard-to-install-on-my-macbook/comment-page-1/#comment-375</link>
		<dc:creator>Ethagnawl</dc:creator>
		<pubDate>Sat, 05 Nov 2011 19:41:13 +0000</pubDate>
		<guid isPermaLink="false">http://porkrind.org/missives2/?p=35#comment-375</guid>
		<description>Thanks!

This worked on my MacBook 3,2 (black).</description>
		<content:encoded><![CDATA[<p>Thanks!</p>
<p>This worked on my MacBook 3,2 (black).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  porkrind.org/missives/comments/feed/ ) in 0.15697 seconds, on Feb 9th, 2012 at 9:01 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 9th, 2012 at 10:01 am UTC -->
