<?xml version="1.0" encoding="UTF-8" ?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>parsexs at Yahoo! Groups</title>
    <link>http://groups.yahoo.com/group/parsexs/</link>
    <description>ExtUtils::ParseXS Developers</description>

    <item>
      <title>ParseXS Changes and Strawberry Perl</title>
      <pubDate>Mon, 23 Aug 2010 23:28:35 GMT</pubDate>
      <dc:creator>James E Keenan</dc:creator>
      <link>http://groups.yahoo.com/group/parsexs/message/97</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/parsexs/message/97</guid>
      <description>At YAPC::NA::2010 in Columbus, Ohio, in June, Curtis Jewell of the Strawberry Perl project attended my presentation.  Curtis subsequently gave our proposed</description>
    </item>
    <item>
      <title>Final draft of YAPC talk</title>
      <pubDate>Wed, 09 Jun 2010 23:31:17 GMT</pubDate>
      <dc:creator>James E Keenan</dc:creator>
      <link>http://groups.yahoo.com/group/parsexs/message/96</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/parsexs/message/96</guid>
      <description>What I hope will be the final draft of my YAPC talk can found in the Attachments section of our Y! groups site. jimk</description>
    </item>
    <item>
      <title>Revised version of YAPC talk</title>
      <pubDate>Sun, 06 Jun 2010 15:01:31 GMT</pubDate>
      <dc:creator>James E Keenan</dc:creator>
      <link>http://groups.yahoo.com/group/parsexs/message/95</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/parsexs/message/95</guid>
      <description>3rd draft of YAPC talk.  Revised to reflect comments from David Golden.</description>
    </item>
    <item>
      <title>Attachments Problem Should Now Be Fixed</title>
      <pubDate>Sun, 30 May 2010 18:54:34 GMT</pubDate>
      <dc:creator>James E Keenan</dc:creator>
      <link>http://groups.yahoo.com/group/parsexs/message/94</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/parsexs/message/94</guid>
      <description>According to email I have received from Yahoo! customer care, the problem with attachments going out with email when they are supposed to be uploaded to the</description>
    </item>
    <item>
      <title>Attachments went with email, unexpectedly</title>
      <pubDate>Sun, 23 May 2010 17:45:27 GMT</pubDate>
      <dc:creator>jimkeenan</dc:creator>
      <link>http://groups.yahoo.com/group/parsexs/message/93</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/parsexs/message/93</guid>
      <description>Hmm.  I expected that the attachments to the last post would have been posted to the Attachments page at our Yahoo site, rather than being included with the</description>
    </item>
    <item>
      <title>Slides for YAPC Talk</title>
      <pubDate>Sun, 23 May 2010 17:03:20 GMT</pubDate>
      <dc:creator>James E Keenan</dc:creator>
      <link>http://groups.yahoo.com/group/parsexs/message/92</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/parsexs/message/92</guid>
      <description>In the Attachments section of our Yahoo! Groups site, you should be able to find: 1. The first draft of my slides for my YAPC::NA::2010 talk on refactoring</description>
    </item>
    <item>
      <title>ParseXS:  What Got Refactored</title>
      <pubDate>Wed, 12 May 2010 01:34:28 GMT</pubDate>
      <dc:creator>James E Keenan</dc:creator>
      <link>http://groups.yahoo.com/group/parsexs/message/91</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/parsexs/message/91</guid>
      <description>Rafael Garcia-Suarez requested a summary of the changes represented by the previously posted diff.  Here&#39;s a quick attempt at such a summary.  Please see my</description>
    </item>
    <item>
      <title>Re: diff for ParseXS running under use strict</title>
      <pubDate>Wed, 12 May 2010 00:56:47 GMT</pubDate>
      <dc:creator>James E Keenan</dc:creator>
      <link>http://groups.yahoo.com/group/parsexs/message/90</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/parsexs/message/90</guid>
      <description>... We formulated those plans before embarking on serious refactoring. See these posts to our parsexs group list: </description>
    </item>
    <item>
      <title>Re: ExtUtils::ParseXS running under &#39;use strict&#39;</title>
      <pubDate>Mon, 10 May 2010 23:36:14 GMT</pubDate>
      <dc:creator>James E Keenan</dc:creator>
      <link>http://groups.yahoo.com/group/parsexs/message/89</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/parsexs/message/89</guid>
      <description>... Attached.  This is one of the first big diffs I&#39;ve generated with git, so if it&#39;s not in the proper format, please let me know.  It was generated with this</description>
    </item>
    <item>
      <title>ExtUtils::ParseXS running under &#39;use strict&#39;</title>
      <pubDate>Sun, 09 May 2010 13:29:48 GMT</pubDate>
      <dc:creator>James E Keenan</dc:creator>
      <link>http://groups.yahoo.com/group/parsexs/message/88</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/parsexs/message/88</guid>
      <description>Friends, I am writing to you at the suggestion of David Golden.  Since last July, as part of the Corehackers project and at David&#39;s request, I have been</description>
    </item>
    <item>
      <title>Re: Progress Report (second draft of presentation)</title>
      <pubDate>Thu, 06 May 2010 00:50:52 GMT</pubDate>
      <dc:creator>James E Keenan</dc:creator>
      <link>http://groups.yahoo.com/group/parsexs/message/87</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/parsexs/message/87</guid>
      <description>... Slides will come once I know what I&#39;m going to say. ... Alas, even the refactored code is intimidating! jimk</description>
    </item>
    <item>
      <title>Re: Progress Report (second draft of presentation) [1 Attachment]</title>
      <pubDate>Wed, 05 May 2010 14:01:02 GMT</pubDate>
      <dc:creator>arocker@...</dc:creator>
      <link>http://groups.yahoo.com/group/parsexs/message/86</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/parsexs/message/86</guid>
      <description>I finally figured out who to get around my mail&#39;s filters to look at the attachment and read the contents. Very interesting. I hope you have some pictures to</description>
    </item>
    <item>
      <title>Progress Report (second draft of presentation)</title>
      <pubDate>Wed, 05 May 2010 01:30:30 GMT</pubDate>
      <dc:creator>James E Keenan</dc:creator>
      <link>http://groups.yahoo.com/group/parsexs/message/85</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/parsexs/message/85</guid>
      <description>Attached (and available on our Yahoo! Groups site) is a second draft of my presentation at YAPC::NA::2010 in Columbus, OH.  This talk is scheduled for 3:30 PM</description>
    </item>
    <item>
      <title>Progress Report (first draft of presentation)</title>
      <pubDate>Tue, 20 Apr 2010 01:53:28 GMT</pubDate>
      <dc:creator>James E Keenan</dc:creator>
      <link>http://groups.yahoo.com/group/parsexs/message/84</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/parsexs/message/84</guid>
      <description>Once again I&#39;m using the Archive Attachments feature of our Yahoo! group to upload a plain-text file to our site.  This is the first draft of my presentation</description>
    </item>
    <item>
      <title>Re: What does this code do?</title>
      <pubDate>Sun, 04 Apr 2010 17:29:32 GMT</pubDate>
      <dc:creator>James E Keenan</dc:creator>
      <link>http://groups.yahoo.com/group/parsexs/message/83</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/parsexs/message/83</guid>
      <description>... No, AFAICT, it&#39;s not used in a string eval.  It seems to be used only in statements that print line number indications in the C output file: $ grep -nC3</description>
    </item>

  </channel>
</rss>
<!-- rss1.grp.bf1.yahoo.com uncompressed Tue May 21 10:51:00 PDT 2013 -->
