<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Docs on Hashbang.ca</title>
		<link>https://hashbang.ca/tag/docs</link>
		<description>Recent content in Docs on Hashbang.ca</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Fri, 29 Jul 2011 01:16:00 -0400</lastBuildDate>
		
			<atom:link href="https://hashbang.ca/tag/docs/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Revising perlopentut</title>
				<link>https://hashbang.ca/post/revising-perlopentut</link>
				<pubDate>Fri, 29 Jul 2011 01:16:00 -0400</pubDate>
				<guid>https://hashbang.ca/post/revising-perlopentut/</guid>
				<description>&lt;p&gt;At YAPC::NA 2011, I &lt;a href=&#34;https://hashbang.ca/post/my-yapcna-2011-lightning-talk&#34;&gt;whined&lt;/a&gt; about the lack of codification of tribal knowledge in Perl. One area that&amp;rsquo;s ripe for fixing is the documentation on &lt;code&gt;open&lt;/code&gt;. There&amp;rsquo;s a section in &lt;code&gt;perlfunc&lt;/code&gt; for &lt;code&gt;open&lt;/code&gt;, and a tutorial: &lt;a href=&#34;http://perldoc.perl.org/perlopentut.html&#34;&gt;&lt;code&gt;perlopentut&lt;/code&gt;&lt;/a&gt;. That tutorial is where I&amp;rsquo;ve started my campaign to have the tutorials and FAQs give good advice.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
