quarry 0.4.0 → 0.5.0

data/doc/assets/styles/index.css

@@ -1,138 +0,0 @@
-body {
-  position: relative;
-  margin: 0; padding: 0;
-  font: 10pt sans-serif;
-  color: white;
-  background: #222;
-}
-
-a { text-decoration: underline; }
-img { border: none; }
-td { text-align: left; vertical-align: top; }
-
-pre { color: #f2b; margin: 10px 0; padding-top: 10px; 
-      background: black; 
-}
-
-.red { color: #b05; }
-
-h1{border-left: 20px solid #222; padding-left: 10px;}
-h2{border-bottom: 0px dotted white; text-style: italic; padding-top: 20px;}
-
-/* header */
-
-#header {
-  height: 200px;
-  background: #000; 
-  padding: 0 0; 
-  border-right: 200px solid transparent;
-}
-
-#header_inner {
- width: 800px;
- height: 200px;
- margin: 0 auto;
- text-align: left;
- background: url(assets/images/rbrylmtrx.png) no-repeat right;
-}
-
-#title {
-  position: relative;
-  /* margin-left: 190px; */
-  text-align: left;
-  padding: 20 0;
-}
-
-#title0 {
-  font: normal 24pt sans-serif;
-  color: #ffe;
-  margin-bottom: 0px;
-  text-align: left;
-}
-
-#title1 {
-  font: normal 48pt sans-serif;
-  color: #fff;
-  letter-spacing: 8pt;
-  margin-bottom: 5;
-  text-align: left;
-}
-
-#title2 {
-  padding: 0 5px;
-  font: normal 11pt sans-serif;
-  color: #ffe;
-  letter-spacing: 4px;
-  text-align: left;
-}
-
-/* menu */
-
-#menu { margin-top: 25px;  text-align: left; margin-left: -30px; }
-#menu ul {list-style-type:none;margin:0px;padding-bottom:10px;background:transparent;position:relative;}
-#menu ul li {display: inline; margin: 5 5 5 0; background: #222; padding: 5 1;}
-#menu ul li a {font:bold .9em sans-serif; color:#fff; text-decoration:none; padding: 5; }
-#menu ul li a:hover { text-decoration: underline; }
-#menu ul li a:active { text-decoration: underline; }
-
-/* sidebar */
-
-#aside {
-  float: right; 
-  text-align: center; font: 1em monospace; line-height: 1.5em;
-  padding: 5; margin-left: 20px; width: 200px; height: 950px;
-  background: #222;
-}
-
-#aside a { color: pink; font: bold 1em sans-serif; text-decoration: none; }
-
-#aside iframe { width: 200px; height: 950px; }
-
-#tigerops {
-  float: right; height: 890px; width: 200px; border: 0px solid yellow;
-}
-
-/* main */
-
-#main { padding: 0px; border-right: 200px solid transparent; background: url(assets/images/darksilver.png) repeat-x #222; }
-
-/* container */
-
-#container { margin: 0 auto; width: 800px; padding: 50px 0 50px 0; background: transparent; }
-#container a { color: pink; font-size: 1em; }
-#container a:hover { text-decoration: underline; }
-#container p { text-align: left; color: #eee; font: 1em sans-serif; line-height: 1.4em; }
-#container h1 { color: #fff; font-size: 2em; font-weight: bold; }
-#container h1 img { margin: 0 0 0 0; }
-
-.section-img { float: right; text-align: left; margin: 10px; }
-
-/* footer */
-
-#footer { width: 100%; background: black; }
-
-#footer div { 
-  margin: 0 auto; width: 800px; padding: 30px 0px 35px 0px;
-  font: normal .8em sans-serif; color: #aaaaaa;
-  border-right: 200px solid transparent;
-}
-
-#footer b { color: #b05; }
-
-    /*
-    #rivets { width: 100%; }
-    #rivets td { width: 25%; text-align: center; }
-
-    a#projButton div { background: url(images/rivet/folder-gray.png) center top no-repeat; }
-    a#projButton:hover div { background-image: url(images/rivet/folder-green.png); }
-
-    a#taskButton div { background: url(images/rivet/board-gray.png) center top no-repeat; }
-    a#taskButton:hover div { background-image: url(images/rivet/board-green.png); }
-
-    a#toolButton div { background: url(images/rivet/paper-gray.png) center top no-repeat; }
-    a#toolButton:hover div { background-image: url(images/rivet/paper-green.png); }
-
-    a#testButton div { background: url(images/rivet/board-gray.png) center top no-repeat; }
-    a#testButton:hover div { background-image: url(images/rivet/board-green.png); }
-    */
-

data/doc/guide/stubs.md

@@ -1,125 +0,0 @@
-How to Implement Stubs
-======================
-
-The most direct approach to creating stubs is to directly
-"inject" the stubbing methods into a given object. This 
-means there is only one possible set of stub definitions
-per object. Here is an example.
-
-   obj = "hello"
-
-   obj.stub.upcase == "HeLLo"
-
-   obj.upcase  #=> "HeLLo"
-
-Becuase we are effecting the object directly, if it carries
-over to other parts of the system, as opposed to being
-a temporary object, then we need to remove the stub methods
-when we are finished with it.
-
-   obj.remove_stubs
-
-This approach to createing stubs is not ver reusable. At best
-we can make copies ot the stubbed object.
-
-   obj2 = obj.copy
-
-This kind of implementation means using singleton methods or
-alias_method override on the original methods. However these
-approaches are not that robust, b/c the SUT may be using singleton
-methods itself and there is a chance of name clashing, in which
-case the stubs would be lost. (Of course if the SUT did things
-properly and used modules to extend objects it wouldn't
-be an issue, but we can't fully count on that.)
-
-Now, let's consider delegation. With delegation, we make a new
-object that wraps the original and we use that in it's place,
-for example.
-
-   obj = "hello"
-
-   alt = orig.to_stub
-
-   alt.stub.upcase == "HeLLo"
-
-   alt.upcase  #=> "HeLLo"
-
-While we can remove the stub methods if we want.
-
-   alt.remove_stubs
-
-we really don't need to do so b/c the original is still intact.
-
-   obj.upcase  #=> "HELLO"
-
-This works very well. However an issue arises when we need to stub
-an internally used SUT object. In other words, if there is an object
-in the SUT that we need to stub, perhaps to safely run a test, rather
-then just stubbing it directly, we need to find where it is coming
-from (at least in so far as our tests are concerned) so that we
-can drop a stub in it's place. This can be tricky. For example,
-stubbing a Module object, rather than:
-
-   MyModule.stub.some_method == "foo"
-
-We would need to do:
-
-   myStub = MyModule.to_stub
-
-   myStub.stub.some_method == "foo"
-
-   const_set(MyModule, mystub)
-
-This is less than elegant and it will even throw out a nasty warning
-message in this case b/c we are redefining a constant. This issue
-can be further complicated if it is difficult to track down where
-exactly the object we want to stub is originating.
-
-Granted stubbing internal SUT objects is not as common, in fact,
-excpet as a means of neccessry object faking, it should be avoided.
-Nonetheless is a required capability of any stubbing system.
-
-Another approach, that in a respect addresses all the issues we've
-come across this far, is the use of annonymous stubs that can be 
-applied to objects as needed. This would allow us to reuse the stub
-definitions. Consider:
-
-   obj = "hello"
-
-   stb = Stub.new
-
-   stb.upcase == "HeLLo"
-
-   alt = orig.stub(stb)
-
-   alt.upcase  #=> "HeLLo"
-
-   obj.upcase  #=> "HELLO"
-
-This is using delegation, just as our last approach, but does so
-with a reusable "stub module". To support direct stubbing as well,
-we could use #extend, thus injecting singleton methods directly into
-the object.
-
-   obj.extend(stb)
-
-   obj.upcase  #=> "HeLLo"
-
-   obj.remove(stb)
-
-We might be able to support the first approaches syntax too if we
-support a default per-object Stub (not used unless at least one 
-direct stub is defined).
-
-   obj = "hello"
-
-   obj.stub.upcase == "HeLLo"
-
-   # implict obj.extend(obj.stub) here
-
-   obj.upcase  #=> "HeLLo"
-
-   obj.remove  # imples obj.remove(obj.stub)
-
-QED.
-

data/doc/index.html

@@ -1,285 +0,0 @@
-<HTML>
-<HEAD>
-  <TITLE>Ruby Quarry</TITLE>
-
-  <LINK REL="SHORTCUT ICON" HREF="assets/images/rbrylmtrx.png"/>
-  <LINK href="assets/styles/index.css" rel="stylesheet" type="text/css"/>
-
-  <SCRIPT language="javascript" src="http://tigerops.org/libraries/jquery/jquery.js"></script>
-
-  <!-- SHJS -->
-  <script type="text/javascript" src="http://tigerops.org/libraries/shjs/sh_main.js"></script>
-  <script type="text/javascript" src="http://tigerops.org/libraries/shjs/lang/sh_ruby.js"></script>
-  <script type="text/javascript" src="http://tigerops.org/libraries/shjs/lang/sh_cpp.js"></script>
-  <script type="text/javascript" src="http://tigerops.org/libraries/shjs/lang/sh_sh.js"></script>
-  <link type="text/css" rel="stylesheet" href="http://tigerops.org/libraries/shjs/css/sh_bipolar.css">
-
-  <SCRIPT type="text/javascript">
-    $(document).ready(function() {
-      section('Home');
-      sh_highlightDocument();
-    });
-
-    function section(n) {
-      $('#sectionHome').hide();
-      $('#sectionDownload').hide();
-      $('#sectionDocumentation').hide();
-      $('#sectionDevelopment').hide();
-      $('#section' + n).show();
-    };
-  </SCRIPT>
-
-</HEAD>
-<BODY>
-
-<!-- SIDE BAR -->
-
-<div id="aside" class="bkg">
-  <iframe id="tigerops" src="http://tigerops.org/ads/side-sm-blk.html"></iframe> 
-</div>
-
-<!-- HEADER -->
-
-<div id="header">
-  <div id="header_inner">
-    <div id="title" style="text-align: left;">
-
-      <div id="title0">r u b y</div>
-      <div id="title1">Q U A R R Y</div>
-      <div id="title2">BDD Specifications & Development Tools</div>
-    </div>
-
-    <div id="menu">
-      <ul>
-        <li><a href="javascript: section('Home');">Welcome</a></li>
-        <li><a href="javascript: section('Download');">Download</a></li>
-        <li><a href="javascript: section('Documentation');">Documentation</a></li>
-        <li><a href="javascript: section('Development');">Development</a></li>
-        <!--
-        <li>&middot;</li>
-        <li><a href="rdoc/index.html">API</a> &nbsp;&nbsp;</li>
-        <li><a href="https://rubyforge.org/projects/ratchets/">Devsite</a></li>
-        <li><a href="src/">Source</a></li>
-        -->
-      </ul>
-    </div>
-
-  </div>
-</div>
-
-<!-- MAIN -->
-
-<div id="main" class="bkg">
-
-  <!-- MAIN TEXT -->
-  <div id="container" class="bkg">
-
-    <div id="sectionHome">
-      <!-- <img class="section-img" src="assets/images/runneth.png" style="border: 1px dotted #ccc; margin-left: 15px;"/> -->
-      <img class="section-img" src="assets/images/icon/software.png" style="margin-left: 15px;"/>
-
-      <h1>Weclome to the <b class="red">Ruby Quarry</b>!</h1>
-
-      <p><b class="red">Ruby Quarry</b> is a developers testing and debuging suite.
-      It features a flexible BDD specification system and a number of other useful tools.</p>
-
-      <p>Quarry's BDD system is uniqe in two ways. First it utilizes Ruby's
-      Execption system to catch Assertions which are defined as <i>functors</i>. Eg.<p>
-
-      <pre class="sh_ruby">
-        require 'quarry/assert'
-
-        4.assert == 5
-      </pre>
-
-      <p>And secondly Quarry's sepcifications are completely free form. In fact, they
-         are an application of <i>literate programming</i>. Unlike other BDD spec
-         libraries, Quarry has no special DSL. Rather specifications are in the form
-         of markup text files (typically RDoc). A specification might look something like:</p>
-
-      <pre class="sh_ruby">
-      = Example Specification
-
-      Concerning the Number 5, it is not 4.
-
-          5.assert! == 4
-
-      But it is itself.
-
-          5.assert == 5
-
-      QED.
-      </pre>
-
-      <p>As you can see, the core assertion nomenclature is <code>assert</code>,
-         but we are considering how and if to support others such as
-         <code>should</code>, <code>must</code> and <code>does</code>.</p>
-
-      <p>Quarry also provides a flexible stubbing facility. The most basic example:</p>
-
-      <pre class="sh_ruby">
-       obj = "example"
-
-       obj.stub.literal(1) == "one"
-       obj.stub.literal(2) == "two"
-
-       obj.literal(1)  #=> "one"
-       obj.literal(2)  #=> "two"
-      </pre>
-
-      <p>We are are also working on a few other tools, include a breakpoint library,
-         a comment extraction and execution tool, a method probe / test spy,
-         which can be used to dip-down into a method and provide a readout of
-         the methods signitures.
-      </p>
-
-      <p>The library is currently considered <i>BETA</i>. There are still a few
-         aspects of the system to work out and polish. Howerver the system is
-         usable and has already become the test/spec system for a few projects.</p>
-    </div>
-
-    <div id="sectionDownload">
-      <img class="section-img" src="assets/images/icon/download.gif" align="left"/>
-
-      <h1>Download &amp; Install</h1>
-
-      <h2>Ruby Gems</h2>
-
-      <p>The easiest way to get Quarry is via RubyGems.</p>
-
-      <pre style="color: lightblue;">
-      $ sudo gem install quarry
-      </pre>
-
-      <h2>Tarball</h2>
-
-      <p>To install manually, you will need to have Ruby Setup installed.
-         You can get that from <a href="setup.rubyforge.org">here</a>. With that
-         in hand <a href="https://rubyforge.org/frs/?group_id=">download</a> the
-         latest Quarry tarball package from Rubyforge.</p>
-
-      <p>Unpack and run <code>sudo setup.rb</code> from within the package folder.
-         For example:</p>
-
-      <pre style="color: lightblue;">
-      $ tar -xvzf quarry-0.3.0.tgz
-      $ cd quarry-0.3.0
-      $ sudo setup.rb
-      </pre>
-
-      <p>Once installed, be sure to check out the documentation.</p>
-    </div>
-
-    <div id="sectionDocumentation">
-      <img class="section-img" src="assets/images/icon/license.png" align="left"/>
-
-      <h1 id="documentation"> Documentation </h1>
-
-      <p>The most amazing thing about Quarry specification is that they can be
-         prefectly renderable markup. To demostrate here are links to the
-         HTML rendered specification for Quarry itself.
-      </p>
-
-      <ul>
-      <li><a href="spec/stub.html">Stub Specification</a></li>
-      </ul>
-
-      <h2>RDoc API Documention</h2>
-
-      <p>For more a detailed code-oriented understanding of Quarry, the
-      <a href="rdoc/index.html">API documention</a> is also available.</p>
-
-      <h2>Tips and Tricks</h2>
-
-      <p><b>Quarry's Mocks are not like mocks in other BDD tools.</b> Mocks in 
-      other libraries validate that methods return are invoked, how many times they
-      are invoked, and in what order. This creates overly tight coupling between
-      test and code --this is not validating behavior, but implementation.
-      Quarry's mock objects only validate return values. Nothing more.
-      So in effect a mock is stub with post-method assertions built-in.</p>
-    </div>
-
-    <div id="sectionDevelopment">
-      <img class="section-img" src="assets/images/icon/source.png" align="left"/>
-
-      <h1 id="development"> Development</h1>
-
-      <p>Development is orchistrated via Rubyforge. The site is
-      <a href="http://rubyforge.org/projects/quarry">http://rubyforge.org/projects/quarry</a>.
-
-      <p>You can use gitweb to
-         <a href="http://quarry.rubyforge.org/git?p=quarry.git;a=tree">browse the 'quarry' repository</a>.</p>
-
-      <h3>Anonymous Access</h3>
-
-      <p>To pull the quarry repository anonymously, use:</p>
-
-      <pre style="color: lightblue;">
-      $ git clone git://rubyforge.org/quarry.git
-      </pre>        
-
-      <h3>Developer Access via Gitosis</h3>
-
-      <p>Registered Developers, the remote setting for the repository is:</p>
-
-      <pre style="color: lightblue;">
-      gitosis@rubyforge.org:quarry.git
-      </pre>
-
-      <p>If you use Quarry, contributions to it's improvement are very important and will be
-         sung many wonderous praises &nbsp;<span style="font-family: monospace;">;)</span>
-         If you'd like to contribute, please contact us via the 
-         <a href="http://groups.google.com/group/tigerops-community?hl=en">Tiger Ops mailing list</a>.</p>
-    </div>
-
-  </div>
-</div>
-
-<!-- FOOTER -->
-
-<div id="footer" style="clear: both;">
-  <div>
-      <img src="assets/images/runneth.png" align="left" style="border: 1px solid black; margin-right: 20px;"/>
-
-      <!-- <img src="assets/images/icon/license.png" align="left" style="margin-bottom: 60px;"/> -->
-
-      <b>Ruby Quarry</b> Copyright &copy; 2007,2008 Tiger Ops. <br/><br>
-      Ruby Quarry is distributed under the terms of the GPLv3.<br/>
-
-      <br/>
-
-      THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS
-      OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE
-      IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
-      PARTICULAR PURPOSE.<br/> <br/>
-      <br/>
-  </div>
-</div>
-
-</BODY>
-</HTML>
-
-
-<!--
-    b.p { color: #777799; }
-    b.r { color: #FF0033; }
-
-    td#slogon {
-      font-family: monospace;
-      vertical-align: middle; text-align: left;
-      color: gray; font-size: 12pt; padding-left: 10px;
-      white-space: nowrap; line-height: 12pt;
-    }
-
-  <table style="padding-top: 900px;">
-    <tr>
-    <td id="slogon">
-      <b class="p">W H E N</b> <br/>
-      <b class="p">Y O U R</b> <br/>
-      <b class="r">R U B Y</b> <br/>
-      <b class="p">R U N N E T H</b> <br/>
-      <b class="p">O V E R</b>&nbsp;
-    </td>
-    </tr>
-  </table>
--->

data/doc/log/bstats/stats.html

@@ -1,39 +0,0 @@
-
-        <html>
-        <head>
-          <title>Quarry Code Statistics</title>
-          <style>
-            h2{margin: 5px 0;}
-            table{width: 95%;}
-            th{background: #dcc;}
-            td{padding: 5px;}
-            .basic_stats{margin: 0 auto; width: 800px;}
-          </style>
-          <link rel="stylesheet" type="text/css" href="stats.css"/>
-        </head>
-        <body>
-        <div class="basic_stats">
-          <h1>Quarry -- Basic Code Statistics</h1>
-          <table class="counts" border="1">
-            <tr><th colspan="9"><h2>Counts</h2></th></tr>
-            <tr><th>TYPE</th><th>Total</th><th>Code</th><th>-%-</th><th>Docs</th><th>-%-</th><th>Blank</th><th>-%-</th><th>Files</th></tr>
-            <tr><th>Source</th><td>1585</td><td>847</td><td>53%</td><td>409</td><td>25%</td><td>301</td><td>18%</td><td>18</td></tr>
-            <tr><th>Test</th><td>0</td><td>0</td><td>0%</td><td>0</td><td>0%</td><td>0</td><td>0%</td><td>0</td></tr>
-            <tr><th>Total</th><td>1585</td><td>847</td><td>53%</td><td>409</td><td>25%</td><td>301</td><td>18%</td><td>18</td></tr>
-          </table>
-          <br/>
-          <table class="ratios" border="1">
-            <tr><th colspan="6"><h2>Ratios</h2></th></tr>
-            <tr><th>x:1</th><th>Code</th><th>Docs</th><th>Blank</th><th>Test</th><th>Total</th></tr>
-            <tr><th>Code</th><td>    1.0</td><td>    2.1</td><td>    2.8</td><td>   30.2</td><td>    0.5</td></tr>
-            <tr><th>Docs</th><td>    0.5</td><td>    1.0</td><td>    1.4</td><td>   14.6</td><td>    0.3</td></tr>
-            <tr><th>Blank</th><td>    0.4</td><td>    0.7</td><td>    1.0</td><td>   10.8</td><td>    0.2</td></tr>
-            <tr><th>Test</th><td>    0.0</td><td>    0.1</td><td>    0.1</td><td>    1.0</td><td>    0.0</td></tr>
-            <tr><th>Total</th><td>    1.9</td><td>    3.9</td><td>    5.3</td><td>   56.6</td><td>    1.0</td></tr>
-          </table>
-          <br/>
-          <div class="date">Sat Nov 15 19:57:15 -0500 2008</div>
-        </div>
-        </body>
-        </html>
-      

data/doc/log/notes.xml

@@ -1,32 +0,0 @@
-<notes>
-<set label="TODO">
-<file src="lib/quarry/stub/mock.rb">
-<note line="16" type="TODO">TODO: Ruby has retry, but I need continue!</note>
-<note line="77" type="TODO">TODO: Use Carats for #unmix.</note>
-</file>
-<file src="lib/quarry/stub/stub.rb">
-<note line="75" type="TODO">TODO: Use Carats for #unmix.</note>
-</file>
-<file src="lib/quarry/spec/document.rb">
-<note line="10" type="TODO">TODO: css and javascripts have fixed location
--     need to make more flexible.</note>
-<note line="62" type="TODO">TODO</note>
-</file>
-<file src="lib/quarry/extract.rb">
-<note line="8" type="TODO">TODO:
-- Should extract_block handle more than the first matching block?
-- How can we handle embedded code in standard comments? Eg. #</note>
-</file>
-<file src="lib/quarry/spec/runner.rb">
-<note line="73" type="TODO">TODO &lt;-- plugin in here start (how to set?)
-context.instance_eval(&amp;spec.given) if spec.given</note>
-<note line="97" type="TODO">TODO &lt;-- plugin in here end
-context.instance_eval(&amp;spec.complete) if spec.complete</note>
-<note line="108" type="TODO">TODO: Would spec.before + spec.code be better?</note>
-</file>
-<file src="lib/quarry/assert.rb">
-<note line="58" type="TODO">TODO: Not sure about the raises here.</note>
-<note line="85" type="TODO">TODO: Ultimately better messages would be nice.</note>
-</file>
-</set>
-</notes>

data/doc/log/stats.html

@@ -1,25 +0,0 @@
-<html><head>
-<title>Quarry Code Statistics</title>
-<link rel="stylesheet" type="text/css" href="log.css"/>
-</head><body>
-<div class="basic_statistics">
-<h1>Quarry -- Basic Code Statistics</h1>
-<table class="counts" border="1">
-<tr><th colspan="9"><h2>Code Counts</h2></th></tr>
-<tr><th>TYPE</th><th>Total</th><th>Code</th><th>-%-</th><th>Docs</th><th>-%-</th><th>Blank</th><th>-%-</th><th>Files</th></tr>
-<tr><th>Source</th><td>1259</td><td>620</td><td>49%</td><td>381</td><td>30%</td><td>230</td><td>18%</td><td>13</td></tr>
-<tr><th>Test</th><td>66</td><td>50</td><td>3%</td><td>0</td><td>0%</td><td>16</td><td>1%</td><td>1</td></tr>
-<tr><th>Total</th><td>1325</td><td>670</td><td>50%</td><td>381</td><td>28%</td><td>246</td><td>18%</td><td>14</td></tr>
-</table>
-<table class="ratios" border="1">
-<tr><th colspan="6"><h2>Code Ratios</h2></th></tr>
-<tr><th>RATIO</th><th>Code</th><th>Docs</th><th>Blank</th><th>Test</th><th>Total</th></tr>
-<tr><th>Code</th><td>    1.0</td><td>    1.6</td><td>    2.7</td><td>    9.4</td><td>      -</td></tr>
-<tr><th>Docs</th><td>      -</td><td>    1.0</td><td>    1.7</td><td>    5.8</td><td>      -</td></tr>
-<tr><th>Blank</th><td>      -</td><td>      -</td><td>    1.0</td><td>    3.5</td><td>      -</td></tr>
-<tr><th>Test</th><td>      -</td><td>      -</td><td>      -</td><td>    1.0</td><td>      -</td></tr>
-<tr><th>Total</th><td>    2.0</td><td>    3.3</td><td>    5.5</td><td>   19.1</td><td>    1.0</td></tr>
-</table>
-<div class="date">Mon Oct 20 22:22:33 -0400 2008</div>
-</div>
-</body></html>

data/doc/log/stats.log

@@ -1,14 +0,0 @@
-Quarry Statistics
-Thu Aug 21 13:19:30 -0400 2008
-
-TYPE      Total    Code  -%-    Docs  -%-   Blank  -%-   Files
-Source      873     380  43%     282  32%     183  20%      10
-Test          0       0   0%       0   0%       0   0%       0
-Total       873     380  43%     282  32%     183  20%      10
-
-RATIO     Code    Docs    Blank   Test   Total
-Code       1.0     1.3     2.1    13.6       -
-Docs         -     1.0     1.5    10.1       -
-Blank        -       -     1.0     6.5       -
-Test         -       -       -     1.0       -
-Total      2.3     3.1     4.8    31.2     1.0