<?xml version="1.0"?>
<!-- name="generator" content="blosxom/2.0" -->
<!DOCTYPE rss PUBLIC "-//Netscape Communications//DTD RSS 0.91//EN" "http://my.netscape.com/publish/formats/rss-0.91.dtd">

<rss version="0.91">
  <channel>
    <title>e dot dot dot 10 04 2006</title>
    <link>http://www.jamesraposa.com/index</link>
    <description>e dot dot dot - a mostly about the Internet weblog by James Raposa</description>
    <language>en</language>

  <item>
    <title>Unraveling Code with the Debugger</title>
    <link>http://www.jamesraposa.com/index/2006/04/10#auto___unraveling_code_with_the_debugger</link>
    <description>&lt;a href='http://www.perl.com/pub/a/2006/04/06/debugger.html?CMP=OTC-BD0016219291&amp;amp;ATT=Unraveling+Code+with+the+Debugger'&gt;&lt;img src='http://www.perl.com/2006/04/06/graphics/111-unravelling-code.gif' width='111px' height='91px' alt='tile image' align='left' border='0'/&gt;&lt;/a&gt;Reading other people's code can be difficult, especially if you have no idea what happens when and where. Understanding code flow is vital to maintenance and bug fixes, but littering code with print and debugging statements is tedious and prone to error. There's another way: use the debugger! Daniel Allen demonstrates how to pinpoint a problem with Perl's debugger.&lt;br /&gt;&lt;br /&gt;Read the entire article &lt;a href=&quot;http://www.perl.com/pub/a/2006/04/06/debugger.html?CMP=OTC-BD0016219291&amp;ATT=Unraveling+Code+with+the+Debugger&quot; target=&quot;_blank&quot;&gt;here&lt;/a&gt;&lt;br /&gt;&lt;!--ttag:perl, programming, scripting--&gt;</description>
  </item>
  </channel>
</rss>