final distro tarball after tweaks

lib/POE/Devel/Benchmarker.pm

@@ -463,13 +463,15 @@ NOTE: the Benchmarker expects everything to be in the "local" directory!
 	apoc@apoc-x300:~$ cd poe-benchmarker
 	apoc@apoc-x300:~/poe-benchmarker$ perl -MPOE::Devel::Benchmarker -e 'benchmark()'
 
+	( go sleep or something, this will take a while! )
+
 =back
 
 =head2 ANALYZING RESULTS
 
 This part of the documentation is woefully incomplete. Please look at the L<POE::Devel::Benchmarker::Analyzer> module.
 
-=head2 SUBROUTINES
+=head2 BENCHMARKING
 
 This module exposes only one subroutine, the benchmark() one. You can pass a hashref to it to set various options. Here is
 a list of the valid options:
@@ -480,7 +482,7 @@ a list of the valid options:
 
 This enables the "lite" tests which will not take up too much time.
 
-default: false
+default: true
 
 =item quiet => boolean
 
@@ -490,14 +492,22 @@ default: false
 
 =back
 
-=head2 EXPORT
+=head1 EXPORT
 
 Automatically exports the benchmark() subroutine.
 
 =head1 TODO
 
 =over 4
 
+=item write POE::Devel::Benchmarker::Analyzer
+
+I need to finish this module so it will dump YAML structures along the raw output. That way we can easily parse the data
+and use it for nifty stuff like graphs or websites :)
+
+BEWARE: please don't write any tools to analyze the dumps as of now, and give me some more time to complete this, because
+I probably will be tweaking the raw output a little to make the regexes less crazy!
+
 =item Perl version smoking
 
 We should be able to run the benchmark over different Perl versions. This would require some fiddling with our
@@ -506,10 +516,10 @@ perl binary. It's smart enough to use $^X to be consistent across tests :)
 
 =item Select the EV backend
 
-<Khisanth> and if you are benchmarking, try it with POE using EV with EV using Glib? :P
-<Apocalypse> I'm not sure how to configure the EV "backend" yet
-<Apocalypse> too much docs for me to read hah
-<Khisanth> Apocalypse: use EV::Glib; use Glib; use POE; :)
+	<Khisanth> and if you are benchmarking, try it with POE using EV with EV using Glib? :P
+	<Apocalypse> I'm not sure how to configure the EV "backend" yet
+	<Apocalypse> too much docs for me to read hah
+	<Khisanth> Apocalypse: use EV::Glib; use Glib; use POE; :)
 
 =item Disable POE::XS::Queue::Array tests if not found
 
@@ -518,7 +528,7 @@ if it isn't installed!
 
 =item Be more smarter in smoking timeouts
 
-Currently we depend on the lite_tests option and hardcode some values including the timeout. If your machine is incredibly
+Currently we depend on the litetests option and hardcode some values including the timeout. If your machine is incredibly
 slow, there's a chance that it could timeout unnecessarily. Please look at the outputs and check to see if there are unusual
 failures, and inform me.
 

lib/POE/Devel/Benchmarker/GetInstalledLoops.pm

@@ -171,13 +171,17 @@ sub Got_CLOSED : State {
 __END__
 =head1 NAME
 
+=head1 SYNOPSIS
+
+	Don't use this module directly. Please use POE::Devel::Benchmarker.
+
 POE::Devel::Benchmarker::GetInstalledLoops - Automatically detects the installed POE loops
 
 =head1 ABSTRACT
 
 This package implements the guts of searching for POE loops via fork/exec.
 
-=head2 EXPORT
+=head1 EXPORT
 
 Automatically exports the getPOEloops() sub
 

lib/POE/Devel/Benchmarker/GetPOEdists.pm

@@ -103,7 +103,7 @@ a true value as the first argument.
 
 	perl -MPOE::Devel::Benchmarker::GetPOEdists -e 'getPOEdists( 1 )'
 
-=head2 EXPORT
+=head1 EXPORT
 
 Automatically exports the getPOEdists() sub
 

lib/POE/Devel/Benchmarker/SubProcess.pm

@@ -635,7 +635,7 @@ POE::Devel::Benchmarker::SubProcess - Implements the actual POE benchmarks
 
 This package is responsible for implementing the guts of the benchmarks, and timing them.
 
-=head2 EXPORT
+=head1 EXPORT
 
 Nothing.
 

lib/POE/Devel/Benchmarker/Utils.pm

@@ -95,7 +95,7 @@ POE::Devel::Benchmarker::Utils - Various utility routines for POE::Devel::Benchm
 
 This package contains the utility routines and constants that POE::Devel::Benchmarker needs.
 
-=head2 EXPORT
+=head1 EXPORT
 
 Automatically exports those subs: