<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" 
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  xmlns:admin="http://webns.net/mvcb/"
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
<title>Squawks of the Parrot/Tornado</title>
<link>archives/rooms/tornado/</link>
<description>Tornado-related posts from Squawks of the Parrot</description>
<dc:language>en-us</dc:language>
<dc:creator>Mark Pilgrim (f8dy@diveintomark.org)</dc:creator>
<dc:rights>Copyright 2011 Mark Pilgrim</dc:rights>
<dc:date>2011-02-21T21:23:32-05:00</dc:date>
<admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=2.661" />
<admin:errorReportsTo rdf:resource="mailto:f8dy@diveintomark.org"/>
<sy:updatePeriod>daily</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>
<item>
<title>On the utility of benchmark implementations</title>
<link>archives/000482.html</link>
<description> One thing that&apos;s really useful to have, when experimenting with new things, is an existing thing that does something like what you&apos;re trying to build. I don&apos;t mean something to copy, but rather something that you can judge your performance against as you work on an alternate implementation. There are many different ways to do a task, but it&apos;s silly to spend much time working on a way that&apos;s slow and clunky. As a for example, as I dive back into working on Tornado, I dusted off the implementation of Conway&apos;s Game of Life. It&apos;s a nice piece to... ( words)</description>
<dc:subject>Tornado</dc:subject>
<dc:date>2011-02-21T21:23:32-05:00</dc:date>
</item><item>
<title>The game of life</title>
<link>archives/000466.html</link>
<description> Okay, so, I&apos;m unimaginative, but I like the game of life. It&apos;s nifty, looks cool, captures the attention of people (like, say, me) who&apos;re attracted to shiny things going &quot;Pling!&quot;, and stresses interesting parts of a system. It was one of the first real things we did for Parrot, and for the longest time it was one of the benchmark programs. Who knows, maybe it still is, I dunno. Anyway, I&apos;ve been working on a GOL for Tornado. It works too, which is cool, and it&apos;s a little surreal to do a full generation with no explicit loops in... ( words)</description>
<dc:subject>Tornado</dc:subject>
<dc:date>2006-11-16T07:12:21-05:00</dc:date>
</item><item>
<title>Tornado 0.05</title>
<link>archives/000462.html</link>
<description> So, I&apos;ve released Tornado 0.05. This release, in addition to a few bug fixes, now properly handles callbacks into the embedding application. The perl module&apos;s been rev&apos;d to handle this as well. This means you can call tornado code from your perl, you can get results back from that tornado code, and you can register perl subs as callbacks for that tornado code. Nifty! There&apos;s one big limitation, which I&apos;m unhappy with. For reasons that annoy me, when waiting on a handle for results, only callbacks posted in the function the handle represents will be processed. I&apos;d hoped to... ( words)</description>
<dc:subject>Tornado</dc:subject>
<dc:date>2006-09-26T19:06:22-05:00</dc:date>
</item><item>
<title>There&apos;s something just not right about that...</title>
<link>archives/000461.html</link>
<description> I know it&apos;s an act of supreme, if likely wrongheaded, laziness, but rather than trying to figure out how to build libraries on Windows, or get libraries loading via relative paths right on OS X, I just hacked up the makefiles for the perl module and the main tornado distribution to directly reference the objects. That means you get the whole wad just linked into your perl module, and at some point I&apos;ll get library building done in a proper cross-platform way so you can have your .so / .dll / .dylib again. In the mean time, I get... ( words)</description>
<dc:subject>Tornado</dc:subject>
<dc:date>2006-08-29T19:07:59-05:00</dc:date>
</item><item>
<title>Now with perly goodness</title>
<link>archives/000460.html</link>
<description> Just cut a release of Tornado 0.04 -- http://www.sidhe.org/~dan/things/tornado-0.04.tar.gz. More fixed bugs and whatnot, but the fun new thing now is that the perl module (in the perl subdirectory) builds and tests, and that includes assembling a sample program, invoking it, and getting the results back. This is, I think, a pretty cool thing. Unfortunately there&apos;s still some manual bits, like you have to copy the tornado shared library into the lib/ directory in the perl module&apos;s build directory when you&apos;re building and testing, but that&apos;s only because I&apos;ve forgotten the Weird Magic needed to get MakeMaker to add... ( words)</description>
<dc:subject>Tornado</dc:subject>
<dc:date>2006-08-27T20:33:13-05:00</dc:date>
</item>
</channel>
</rss>