rant 0.4.6 → 0.4.8

data/INSTALL

@@ -0,0 +1,44 @@
+
+== Installing Rant
+
+Of course you need Ruby to run rant. You can get the latest Ruby
+package from the {Ruby hompage}[http://www.ruby-lang.org/en/].
+
+There are two ways to install Rant on your system:
+
+=== Installing Rant as a RubyGem
+
+RubyGems has to be installed on your system. Check this by trying
+the _gem_ command:
+    % gem
+If this prints a help message, RubyGems should work. Otherwise
+install Rant as described in the next section.
+Now the following command:
+    % gem install --remote rant
+will download and install Rant. Depending on the RubyGems
+configuration, you will probably need superuser privileges.
+Then try to run:
+    % rant --version
+which should print name and version of the _rant_ command. If this
+is done, you have successfully installed Rant. Congratulations!
+
+=== Conventional installation
+
+First download the latest version of Rant from
+http://rubyforge.org/frs/?group_id=615. Choose the .zip or .tar.gz
+file, whatever you like, with the highest version number. Then unpack
+the archive, cd to the new directory and run the install.rb script.
+This could look like:
+    % tar -xzf rant-<version>.tar.gz
+    % cd rant-<version>
+    % ruby install.rb
+Depending on your Ruby installation, you'll probably need superuser
+privileges for the last command.
+Finally try to run
+    % rant --version
+to verify Rant was installed correctly.
+
+If you aren't already reading this documentation in html format, you
+can generate it with:
+    % rant doc
+The output will be in doc/html.

data/NEWS

@@ -1,6 +1,36 @@
 
 = Rant NEWS
 
+== Rant 0.4.8
+
+Incompatible changes:
+* The filenames <tt>Rantfile.rb</tt> and <tt>rantfile.rb</tt> which
+  were deprecated since the last release aren't recognized anymore.
+  Use +Rantfile+, +rantfile+ or <tt>root.rant</tt> instead.
+
+Deprecated:
+* The two undocumented Array methods <tt>ary.arglist</tt> and
+  <tt>ary.shell_pathes</tt> are deprecated. Use <tt>sys.sp(ary)</tt>
+  in Rantfiles instead.
+* <tt>rant-import -v</tt> option. Use <tt>-V</tt> or
+  <tt>--version</tt> instead.
+
+Fixes and minor improvements:
+* Fix output of <tt>rant -T</tt> for descriptions with more than two lines.
+* Filelists: Same handling of files starting with a dot with all
+  supported ruby versions (1.8.0 - 1.9).
+* The <tt>sys.ruby</tt> method uses an absolute path to start the Ruby
+  interpreter. Thus <tt>sys.ruby</tt> also works if ruby is not on the
+  PATH.
+* Fix for latest ruby 1.9, which renamed +fcall+ to +funcall+.
+
+New features:
+* <tt>rant-import</tt> supports <tt>--zip</tt> (<tt>-z</tt>) option
+  for zip-compression now.
+* Tasks with command change recognition. Read
+  doc/command.rdoc[link:files/doc/command_rdoc.html]
+* Improved rule support.
+
 == Rant 0.4.6
 
 Incompatible changes:

data/README

@@ -18,6 +18,7 @@ Rant currently features:
   additional software.
 * Optional recognition of file changes based on MD5 checksums instead
   of file modification times.
+* Tasks with command change recognition.
 * Primitive support for compiling C# sources portably with csc, cscc
   and mcs.
 * Dependency checking for C/C++ source files.
@@ -41,7 +42,7 @@ Running rant in the directory of this file:
 will ensure that the "data" file in the "backup" directory is up to
 date.
 
-This document was written for version 0.4.6 of Rant. Most things
+This document was written for version 0.4.8 of Rant. Most things
 described here will work for older/newer versions of Rant, but look at
 the README file in the Rant distribution you've installed for exact
 documentation of your Rant version.
@@ -62,7 +63,7 @@ mailto:langstefan@gmx.at.
 == Roadmap
 
 Installing Rant::
-    read the section _Installation_ in this document
+    read INSTALL[link:files/INSTALL.html]
 License::
     read the section _Copying_ in this document
 Invoking *rant*::
@@ -83,6 +84,8 @@ Compiling C/C++::
     read doc/c.rdoc[link:files/doc/c_rdoc.html]
 Buildfiles in subdirectories::
     read doc/subdirs.rdoc[link:files/doc/subdirs_rdoc.html]
+Tasks with command change recognition::
+    read doc/command.rdoc[link:files/doc/command_rdoc.html]
 Using the Configure plugin::
     read doc/configure.rdoc[link:files/doc/configure_rdoc.html]
 Compiling C#::
@@ -91,50 +94,6 @@ Upgrading::
     read the NEWS[link:files/NEWS.html] for new features, not
     backwards compatible changes and other issues.
 
-== Installation
-
-Of course you need Ruby to run rant. You can get the latest Ruby
-package from the {Ruby hompage}[http://www.ruby-lang.org/en/].
-
-There are two ways to install Rant on your system:
-
-=== Installing Rant as a RubyGem
-
-RubyGems has to be installed on your system. Check this by trying
-the _gem_ command:
-    % gem
-If this prints a help message, RubyGems should work. Otherwise
-install Rant as described in the next section.
-Now the following command:
-    % gem install --remote rant
-will download and install Rant. Depending on the RubyGems
-configuration, you will probably need superuser privileges.
-Then try to run:
-    % rant --version
-which should print name and version of the _rant_ command. If this
-is done, you have successfully installed Rant. Congratulations!
-
-=== Conventional installation
-
-First download the latest version of Rant from
-http://rubyforge.org/frs/?group_id=615. Choose the .zip or .tar.gz
-file, whatever you like, with the highest version number. Then unpack
-the archive, cd to the new directory and run the install.rb script.
-This could look like:
-    % tar -xzf rant-<version>.tar.gz
-    % cd rant-<version>
-    % ruby install.rb
-Depending on your Ruby installation, you'll probably need superuser
-privileges for the last command.
-Finally try to run
-    % rant --version
-to verify Rant was installed correctly.
-
-If you aren't already reading this documentation in html format, you
-can generate it with:
-    % rant doc
-The output will be in doc/html.
-
 == Copying
 
 Copyright (C) 2005  Stefan Lang
@@ -215,6 +174,7 @@ Rant was tested on:
                         1.8.1
                         1.8.2
 			1.8.3
+			1.8.4
 			1.9
     MacOS X		1.8.2
     Windows XP		1.8.2 (OneClick Installer)

data/Rantfile

@@ -9,10 +9,9 @@ task :default => :test
 dist_files = sys["{bin,lib,test,doc,misc}/**/*"]
 dist_files.shun("html", "coverage")
 dist_files += sys["*"].no_dir.exclude("InstalledFiles", "Session.vim")
-dist_files.exclude("bench-*")
+dist_files.exclude("mk", "bench-*")
 hp_files = sys["doc/homepage/*"]
-extra_rdoc_files = sys["**/README", "NEWS", "doc/**/*.rdoc"]
-extra_rdoc_files.no_dir("pkg").no_dir("test")
+rdoc_files = sys["README", "NEWS", "INSTALL", "doc/*.rdoc"]
 
 # remove when compiler stuff is getting useful...
 dist_files.exclude "lib/rant/compiler*", "lib/rant/import/c/program.rb"
@@ -20,7 +19,7 @@ dist_files.exclude "lib/rant/compiler*", "lib/rant/import/c/program.rb"
 rdoc_opts = %w(-S -c UTF-8 --title Rant --main README)
 
 gen RubyPackage, "rant#{var :pkg_ext}" do |t|
-    t.version = `#{Env::RUBY} run_rant --version`.split[1]
+    t.version = `#{sys.sp Env::RUBY_EXE} run_rant --version`.split[1]
     t.summary = "Rant is a Ruby based build tool."
     t.files = dist_files
     t.bindir = "bin"
@@ -29,7 +28,8 @@ gen RubyPackage, "rant#{var :pkg_ext}" do |t|
     t.email = "langstefan@gmx.at"
     t.rubyforge_project = "make"
     t.homepage = "http://make.rubyforge.org"
-    t.gem_extra_rdoc_files = extra_rdoc_files
+    t.has_rdoc = false
+    t.gem_extra_rdoc_files = rdoc_files
     t.gem_rdoc_options = rdoc_opts
     desc "Create packages for distribution."
     t.package_task
@@ -39,7 +39,7 @@ desc "Generate documentation."
 gen RubyDoc do |g|
     g.verbose = true
     g.dir = "doc/html"
-    g.files.concat extra_rdoc_files
+    g.files = rdoc_files
     g.opts = rdoc_opts + %w(-T doc/jamis.rb)
 end
 
@@ -139,7 +139,12 @@ end
 task :t180 do |t|
     # my installed testrb version doesn't work with ruby-1.8.0
     sys.cd "test"
-    sys "ruby180 ts_all.rb"
+    if var[:TEST]
+        sys "ruby180", "-rtest/unit", "-I", sys.expand_path("@lib"),
+            "-I", sys.expand_path("."), var[:TEST].sub(/^test\//, '')
+    else
+        sys "ruby180 ts_all.rb"
+    end
 end
 
 desc "Remove autogenerated files."
@@ -189,4 +194,30 @@ task "svn-clean" do
     }
 end
 
+task "check-168" do
+    rbfiles = sys["bin/rant*", "lib/**/*.rb"]
+    ok = []
+    bad = []
+    rbfiles.each { |fn|
+        sys "ruby168 -c #{fn}" do |ps|
+            (ps.exitstatus == 0 ? ok : bad) << fn
+        end
+    }
+    puts "Bad files:"
+    bad.each { |b| puts "  #{b}" }
+    puts "#{ok.size} of #{rbfiles.size} are OK"
+end
+
+task "fetch-svn-dump" do
+    require 'net/http'
+    require 'uri'
+    url = URI.parse("http://svn.berlios.de/svndumps/rant-repos.gz")
+    req = Net::HTTP::Get.new(url.path)
+    puts "Starting download from: #{url}"
+    res = Net::HTTP.start(url.host, url.port) { |http|
+        http.request(req)
+    }
+    sys.write_to_file "../rant-repos.gz", res.body
+end
+
 # vim:ft=ruby

data/doc/c.rdoc

@@ -60,5 +60,7 @@ Rantfile basics::
     doc/rantfile.rdoc[link:files/doc/rantfile_rdoc.html]
 Advanced Rantfiles::
     doc/advanced.rdoc[link:files/doc/advanced_rdoc.html]
+Tasks with command change recognition::
+    doc/command.rdoc[link:files/doc/command_rdoc.html]
 Rant Overview::
     README[link:files/README.html]

data/doc/command.rdoc

@@ -0,0 +1,210 @@
+
+== Command change recognition
+
+A +Command+ task is similar to a +file+ task: It is intended to create
+on file which may depend on other files. But instead of creating the
+file by executing a block of Ruby code, the +Command+ task creates the
+target file by executing a shell command.
+
+A +file+ task rebuilds the target file if at least one of the
+following two conditions is met:
+1. The target file doesn't exist.
+2. One of the prerequisites changed since the last build.
+
+A +Command+ task rebuilds the target file if at least one of the
+following three conditions is met:
+1. The target file doesn't exist.
+2. One of the prerequisites changed since the last build.
+3. The command to create the target file changed since the last build.
+
+=== General usage
+
+Consider the following Rantfile for rant 0.4.6:
+
+    var :CFLAGS => "-g -O2"    # can be overriden from commandline
+    
+    file "foo" => ["foo.o", "util.o"] do |t|
+        sys "cc -o #{t.name} #{var :CFLAGS} #{t.prerequisites.join(' ')}"
+    end
+
+    gen Rule, ".o" => ".c" do |t|
+        sys "cc -c -o #{t.name} #{var :CFLAGS} #{t.source}"
+    end
+
+The problem with this buildfile is, that it won't recognize
+a change of CFLAGS, i.e. foo.o, util.o and foo should get
+rebuilt whenever CFLAGS changes.
+
+Since Rant 0.4.8, it is possible to do the following:
+
+    import "command"
+
+    var :CFLAGS => "-g -O2"    # can be overriden from commandline
+    
+    gen Command, "foo" => ["foo.o", "util.o"] do |t|
+        # notice: we're not calling the sys method, we
+        # are returning a string from the block
+        "cc -o #{t.name} #{var :CFLAGS} #{t.prerequisites.join(' ')}"
+    end
+
+    # if the block to Rule takes two arguments,
+    # it is expected to return a task
+    gen Rule, ".o" => ".c" do |target, sources|
+        gen Command, target => sources do |t|
+            "cc -c -o #{t.name} #{var :CFLAGS} #{t.source}"
+        end
+    end
+
+Now, whenever the command to build foo or a *.o file changes,
+it will be rebuilt.
+
+There is also a more concise syntax:
+
+    import "command"
+
+    var :CFLAGS => "-g -O2"
+    
+    # first argument (string) is the task/file name, second
+    # argument (string, array or filelist) is a list of
+    # prerequisites (notice: no `target => prereqs' syntax!)
+    # third argument is a command string, which will be
+    # executed by a subshell.
+    gen Command, "foo", ["foo.o", "util.o"],
+        'cc -o $(>) $[CFLAGS] $(<)'
+
+    gen Rule, ".o" => ".c" do |target, sources|
+        gen Command, target, sources,
+            'cc -c -o $(<) $[CFLAGS] $(-)'
+    end
+
+For the last syntax:
+
+=== Interpolation of variables into command strings:
+
+==== Which variables are interpolated?
+
+1. Instance variables (mostly for internal usage), e.g.:
+       @cc = "cc"
+
+2. "var" variables (can be set from commandline, easy
+   synchronization with environment variables), e.g.:
+       var :cc => "cc"
+
+3. Special, task specific variables
+   "name" (symbol equivalent ">")::
+      task name
+   "prerequisites" (symbol equivalent "<")::
+      all prerequisites seperated by spaces
+   "source" (symbol equivalent "-")::
+      first prerequisite
+   more task specific variables might get added later
+
+==== Syntax of variable interpolation
+
+Variable names must consist only of "word characters",
+i.e. matching \w in Ruby regexes.
+
+1. Plain interpolation.
+   Example command:
+        "echo $[ARGS]"
+   The contents of variable ARGS (either <tt>@ARGS</tt> or
+   <tt>var[:ARGS]</tt>) are converted to a string and interpolated.
+   If the variable contains an array, <tt>ARGS.join(' ')</tt> is
+   interpolated.
+
+2. Escaped interpolation.
+   Example command:
+        "echo ${ARGS}"
+   Like plain interpolation, but spaces will be escaped
+   (system dependent).
+   Consider this Rantfile:
+      
+       import "command"
+       @args = ["a b", "c d", "ef"]
+       @sh_puts = "ruby -e \"puts ARGV\""
+       gen Command, "foo", '$[sh_puts] ${args} > $(>)'
+
+   Running rant will give on Windows:
+        ruby -e "puts ARGV" "a b" "c d" ef > foo
+   and on other systems:
+        ruby -e "puts ARGV" a\ b c\ d ef > foo
+
+3. Path interpolation.
+   Example command:
+        "echo $(ARGS)"
+   Like escaped interpolation, but additionally, forward slashes
+   (as used for filenames in Rantfiles) will be replaced with
+   backslashes on Windows.
+
+==== More on semantics of variable interpolation
+
+Interpolation is recursive, except for special target variables.
+
+There is a small semantic difference between the verbose
+special target variables (+name+ +prerequisites+ +source+) and
+the symbolic ones (<tt><</tt> <tt>></tt> <tt>-</tt>):
+The symbolic ones are interpolated *after* checking if the command
+has changed since the last build, the verbose forms are interpolated
+*before*.
+
+Consider this (artifical, using the Unix tool "cat") example:
+Rantfile (symbolic special target vars):
+
+    import "command"
+    @src = ["src1", "src2"]
+    @src = var[:SRC].split if var[:SRC]
+    gen Command, "foo", @src, 'cat $(<) > $(>)'
+
+    % echo a > src1
+    % echo b > src2
+    % echo b > src3
+    % rant
+    cat src1 src2 > foo
+
+"foo" didn't exist, so it was built anyway. Now let us
+change the prerequisite list:
+
+    % rant "SRC=src1 src3"
+
+won't cause a rebuild of foo. Dependencies of foo changed from
+<tt>["src1", "src2"]</tt> to <tt>["src1", "src3"]</tt> but since src2
+and src3 have the same content and <tt>$(<)</tt> isn't expanded for
+command change recognition, rant considers foo up to date.
+
+Now change Rantfile to (verbose special target vars):
+
+    import "command"
+    @src = ["src1", "src2"]
+    @src = var[:SRC].split if var[:SRC]
+    gen Command, "foo", @src, 'cat $(prerequisites) > $(name)'
+
+Starting from scratch:
+    % echo a > src1
+    % echo b > src2
+    % echo b > src3
+    % rant
+    cat src1 src2 > foo
+    % rant "SRC=src1 src3"
+    cat src1 src3 > foo
+
+This time, Rant expanded <tt>$(prerequisites)</tt> for command change
+recognition, and since the prerequsite list changed, it caused a
+rebuild.
+
+== See also
+
+If you want more details, look in the <tt>test/import/command</tt>
+directory of the Rant distribution.
+
+Using MD5 checksums instead of file modification times::
+    doc/md5.rdoc[link:files/doc/md5_rdoc.html]
+Advanced Rantfiles::
+    doc/advanced.rdoc[link:files/doc/advanced_rdoc.html]
+Support for C/C++::
+    doc/c.rdoc[link:files/doc/c_rdoc.html]
+Packaging::
+    doc/package.rdoc[link:files/doc/package_rdoc.html]
+Ruby project howto::
+    doc/rubyproject.rdoc[link:files/doc/rubyproject_rdoc.html]
+Rant Overview::
+    README[link:files/README.html]

data/doc/examples/c_dependencies/Rantfile

@@ -3,7 +3,7 @@ import %w(c/dependencies clean autoclean)
 
 desc "Compile hello world program."
 file "hello" => %w(src/main.o src/util.o) do |t|
-    sys "cc -Wall -o #{t.name} #{t.prerequisites.arglist}"
+    sys "cc -Wall -o #{t.name} #{sys.sp t.prerequisites}"
 end
 
 gen Rule, :o => :c do |t|

data/doc/examples/directedrule/Rantfile

@@ -13,7 +13,7 @@ ro = gen DirectedRule, "obj" => sys["src_*"], :o => :c do |t|
 end
 
 file "obj/libfoo.a" => ro.candidates do |t|
-    sys "ar cr #{t.name} #{t.prerequisites.arglist}"
+    sys "ar cr #{t.name} #{sys.sp t.prerequisites}"
     sys "ranlib #{t.name}"
 end
 

data/doc/homepage/index.html

@@ -80,7 +80,7 @@
             <h2>Links</h2>
             <p>
             <a href="files/NEWS.html">ChangeLog</a><br/>
-            <a href="api.html">API docs</a><br/>
+            <!--a href="api.html">API docs</a><br/-->
             <a href="http://rubyforge.org/projects/make/">Project page</a><br/>
             <a title="Subscribe to mailing list"
                 href="http://rubyforge.org/mailman/listinfo/make-cafe">Mailing list</a><br/>
@@ -88,6 +88,8 @@
                 href="http://rubyforge.org/pipermail/make-cafe/">List archives</a><br/>
             <a
                 href="http://rubyforge.org/tracker/?func=add&amp;group_id=615&amp;atid=2428">Report a bug</a><br/>
+            <a title="Subversion repository for Rant development"
+                href="http://developer.berlios.de/svn/?group_id=5046">Repository</a><br/>
             </p>
         </div>
 
@@ -101,12 +103,21 @@
             before installing a newer version of Rant. It describes
             non-backwards compatible changes and new features.
             </p>
+            <h2>Rant vs. Rake</h2>
+            <p>
+            <a href="files/doc/rant_vs_rake_rdoc.html">Read comparison</a>
+            </p>
         </div>
 
         <p>
         <a href="http://validator.w3.org/check?uri=referer"><img
             src="http://www.w3.org/Icons/valid-xhtml10"
             alt="Valid XHTML 1.0!" height="31" width="88" /></a>
+        <a href="http://developer.berlios.de" title="BerliOS
+            Developer"> <img
+            src="http://developer.berlios.de/bslogo.php?group_id=5046"
+            width="124px" height="32px" border="0" alt="BerliOS
+            Developer Logo"></a>
         </p>
 
         <!-- BlueRobot was here. -->

data/doc/rant-import.rdoc

@@ -8,11 +8,14 @@ run rant-import).
 
 Just run the command with the <tt>--help</tt> option to get a brief
 help message:
+
     % rant-import --help
 
 Probably the easiest way to create your monolithic rant script is with
 the <tt>--auto</tt> option:
+
     % rant-import --auto ant
+
 This will write a monolithic rant script to the file +ant+ in the
 current directory. To determine which plugins and imports your project
 is using, it performs step 2 of the rant command as described in
@@ -20,7 +23,9 @@ doc/rant.rdoc[link:files/doc/rant_rdoc.html], which means that it
 loads the Rantfile in the current directory.
 
 That one command should be enough, try it out:
+
     % ruby ant
+
 This script has the same behaviour as the rant command. Distribute it
 with your project and nobody else but you needs an Rant installation.
 

data/doc/rant_vs_rake.rdoc

@@ -0,0 +1,107 @@
+
+== Rant vs. Rake
+
+Since many people (especially Ruby programmers) that know Rake ask for
+a Rake/Rant comparison, I'll spend a few paragraphs on this topic.
+
+This comparison is for Rant 0.4.8 and Rake 0.6.2. If not stated
+otherwise, this document assumes a standard Ruby 1.8/1.9 installation
+without additional libraries (except for Rant and Rake).
+
+=== Feature comparison
+
+Generally speaking, Rant has all major features of Rake and more.
+Especially the following major Rant features aren't available for
+Rake:
+
+* Optional use of MD5 checksums instead of timestamps.
+  To enable it, one import statement at the top of the Rantfile is
+  enough:
+
+    import "md5"
+
+* Easy and portable tgz/zip file creation on Linux/MacOS X/Windows
+  (and probably most other platforms where ruby runs). No additional
+  libraries necessary!
+
+* Create a script, tailored to the needs of a project, which
+  can be used instead of an Rant installation => Distribute this
+  script with your project and users and other developers don't need
+  an Rant installation.
+
+  Try the <tt>rant-import</tt> command:
+
+    % rant-import --auto make.rb
+
+  rant-import reads the Rantfile in the current directory, determines
+  what code of the Rant distribution (and custom imports) is needed
+  and writes a script that supports all required Rant features and
+  depends only on a standard Ruby (1.8.0 or newer) installation to the
+  file <tt>make.rb</tt>. Users and other developers don't need an Rant
+  installation anymore. Instead of typing:
+
+    % rant foo
+
+  they can type:
+
+    % ruby make.rb foo
+
+* It is possible to split up the build specification into
+  multiple files in different directories.  (=> no such thing as
+  "recursive make" necessary). 
+
+* Dependency checking for C/C++ source files (integrated makedepend
+  replacement).
+
+* The <tt>--force-run</tt> (<tt>-a</tt>) option forces the rebuild of
+  a target and all its dependencies. E.g.:
+
+    % rant -a foo
+
+  Let's say +foo+ depends on <tt>foo.o</tt> and <tt>util.o</tt>. Then
+  the above command will cause a rebuild of <tt>foo.o</tt>,
+  <tt>util.o</tt> and +foo+, no matter if Rant considers these files
+  up to date or not.
+
+* Tasks with command change recognition. Example code:
+  
+    import "command"
+
+    var :CFLAGS => "-g -O2" # can be overridden from commandline
+
+    gen Command, "foo", ["foo.o", "util.o"],
+        "cc $[CFLAGS] -o $(name) $(prerequisites)"
+  
+  The last two lines tell Rant, that the file +foo+ depends on the
+  files <tt>foo.o</tt> and <tt>util.o</tt> and that +foo+ can be built
+  by running the command in the last line ("cc ...") in a subshell.
+  If at least one of the following three conditions is met, +foo+ will
+  be rebuilt:
+  1. +foo+ doesn't exist.
+  2. <tt>foo.o</tt> or <tt>util.o</tt> changed since the last build of
+     +foo+.
+  3. The command (most probably +CFLAGS+) changed since the last build
+     of +foo+.
+
+Some other goodies: The +make+ method, the SubFile and AutoClean
+tasks, special variables and more. Most of this is documented in
+doc/advanced.rdoc[link:files/doc/advanced_rdoc.html]
+
+=== Internals
+
+* Rake defines many methods (task, file, desc, FileUtils methods, etc.)
+  in the Object class (i.e. accessible from *each* line of Ruby code)
+  which can get problematic at least if you want to use Rake as a
+  library.
+
+  Rant solves this problem by evaluating Rantfiles in a special
+  context (with +instance_eval+).
+
+* Rake uses global variables and class/class instance variables to
+  store state (tasks, etc.). The effect of this is, that you can have
+  only one Rake application per Ruby interpreter (process) at a time.
+
+  Rant stores application state in a class instance. It is possible to
+  instantiate as many "Rant applications" at the same time as needed.
+  On the other hand, there is currently no public and documented
+  interface to do so (but it will come at least with Rant 1.0.0).