<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: RubyCocoa Parses Multiple Return Values!</title>
	<link>http://andymatuschak.org/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fandymatuschak.org%2Farticles%2F2007%2F12%2F12%2Frubycocoa-parses-multiple-return-values%2F&amp;seed_title=RubyCocoa+Parses+Multiple+Return+Values%21</link>
	<description>Flying through the universe of code on a talking spaceship!</description>
	<pubDate>Mon, 06 Oct 2008 13:14:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>By: Andy Matuschak</title>
		<link>http://andymatuschak.org/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fandymatuschak.org%2Farticles%2F2007%2F12%2F12%2Frubycocoa-parses-multiple-return-values%2F&amp;seed_title=RubyCocoa+Parses+Multiple+Return+Values%21#comment-4574</link>
		<dc:creator>Andy Matuschak</dc:creator>
		<pubDate>Thu, 13 Dec 2007 18:58:53 +0000</pubDate>
		<guid>http://andymatuschak.org/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fandymatuschak.org%2Farticles%2F2007%2F12%2F12%2Frubycocoa-parses-multiple-return-values%2F&amp;seed_title=RubyCocoa+Parses+Multiple+Return+Values%21#comment-4574</guid>
		<description>Ohman, another one? :)

I like Nu in theory, but native arrays and hashes are important to me and, well, I find myself having a lot of trouble keeping a sense of scope in big s-exprs.

But yeah, there will always be some level of disconnect. Unless... maybe Ruby 2.0's named parameters will help.</description>
		<content:encoded><![CDATA[<p>Ohman, another one? :)</p>
<p>I like Nu in theory, but native arrays and hashes are important to me and, well, I find myself having a lot of trouble keeping a sense of scope in big s-exprs.</p>
<p>But yeah, there will always be some level of disconnect. Unless&#8230; maybe Ruby 2.0&#8217;s named parameters will help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Ryland</title>
		<link>http://andymatuschak.org/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fandymatuschak.org%2Farticles%2F2007%2F12%2F12%2Frubycocoa-parses-multiple-return-values%2F&amp;seed_title=RubyCocoa+Parses+Multiple+Return+Values%21#comment-4536</link>
		<dc:creator>Chris Ryland</dc:creator>
		<pubDate>Thu, 13 Dec 2007 14:23:22 +0000</pubDate>
		<guid>http://andymatuschak.org/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fandymatuschak.org%2Farticles%2F2007%2F12%2F12%2Frubycocoa-parses-multiple-return-values%2F&amp;seed_title=RubyCocoa+Parses+Multiple+Return+Values%21#comment-4536</guid>
		<description>I think there's always going to be a disconnect between non-Objective-C interfaces to Cocoa for exactly this reason (the message-passing syntax). You can paper over it with dictionary-style name/value mapping, etc., but it'll never be as good as the original.

That's why I'm off designing a new dynamic language that exactly matches Objective-C's syntax &#38; general semantics... ;-)</description>
		<content:encoded><![CDATA[<p>I think there&#8217;s always going to be a disconnect between non-Objective-C interfaces to Cocoa for exactly this reason (the message-passing syntax). You can paper over it with dictionary-style name/value mapping, etc., but it&#8217;ll never be as good as the original.</p>
<p>That&#8217;s why I&#8217;m off designing a new dynamic language that exactly matches Objective-C&#8217;s syntax &amp; general semantics&#8230; ;-)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
