rroonga 0.9.5-x86-mingw32 → 1.0.1-x86-mingw32

data/pkg/rroonga-0.9.5/text/expression.rdoc

@@ -1,285 +0,0 @@
-# -*- coding: utf-8 -*-
-
-= grn式 (grn_expr)
-
-
-== 名前
-
-grn式 - 検索条件やデータベースへの操作を表現する文字列の形式。(読み方:"ぐるんしき")
-
-
-== 書式
-
-grn式はquery形式とscript形式のいずれかによって表現することができます。
-
-query形式
-
-[条件式]
-  以下の条件式が使用できます。
-
-  [文字列]
-    全文検索条件(デフォルト検索対象カラムの値が指定された文字列を含んでいる)
-
-  ["文字列"]
-    フレーズ検索条件(デフォルト検索対象カラムの値が指定されたフレーズを含んでいる)
-
-  [カラム名:値]
-    一致条件(カラム値 == 値)
-
-  [カラム名:!値]
-    不一致条件(カラム値 != 値)
-
-  [カラム名:<値]
-    比較条件(カラム値 < 値)
-
-  [カラム名:>値]
-    比較条件(カラム値 > 値)
-
-  [カラム名:<=値]
-    比較条件(カラム値 <= 値)
-
-  [カラム名:>=値]
-    比較条件(カラム値 >= 値)
-
-  [カラム名:@文字列]
-    全文検索条件(カラム値が指定された文字列を含んでいる)
-
-[補助演算子 [1]]
-  全文検索条件の挙動を制御する以下の演算子が指定できます。
-
-  [~文字列]
-    文字列を含んでいた場合は、そのレコードのスコアを下げます。
-
-  [<文字列]
-    文字列を含んでいた場合に加算されるスコアの値を小さくします。
-
-  [>文字列]
-    文字列を含んでいた場合に加算されるスコアの値を大きくします。
-
-  [文字列*]
-    文字列に前方一致する条件を示します。
-
-  [*S[数値]"文字列"]
-    文字列と関連する文書を検索します。文字列から抽出する特徴語の数を数値に指定します。
-
-  [*N[数値]"文字列"]
-    文字列に含まれる複数の語が、近傍に含まれる文書を検索します。近傍の範囲の上限とな
-    る語数を数値に指定します。N-gramの場合は、文字数を指定します。
-
-[結合演算子]
-  複数の条件式を結合するために以下の演算子が使用できる。演算子を伴わずに複数の条件式 が空白('
-  ')区切りで指定された場合は、デフォルトの結合演算子が指定されたものとみな される。
-
-  [a OR b]
-    論理和(aとbといずれかの条件がマッチする)
-
-  [a + b]
-    論理積(aとbの両方がマッチする)
-
-  [a - b]
-    aにマッチし、bにはマッチしない
-
-  [( )]
-    複数の条件をまとめる
-
-[プラグマ [2]]
-  query形式文字列の先頭に、処理方法を指定するプラグマを埋め込むことができます。
-
-  プラグマは必ずクエリ文字列の冒頭に存在しなければなりません。(先頭に空白を入れては いけません)
-
-  一つのクエリに複数のプラグマを指定することができます。
-
-  複数のプラグマを指定する場合は、間に空白を入れてはいけません。
-
-  [*E数値1[,数値2]]
-    検索結果の数が数値1よりも小さい場合、完全一致→非わかち書き→部分一致の順に自動
-    的に検索処理方法を切り替えます。完全一致でヒットした文書と比べて非わかち書き一致、
-    部分一致でヒットした文書には数値2分だけ小さいスコアを付与します。数値2を省略した
-    場合は既定値(=2)と解釈されます。数値1に負の数を指定した場合は以下のように処理し ます。
-
-    -1
-
-    完全一致検索のみを行う
-
-    -2
-
-    非わかち書き検索のみを行う
-
-    -3
-
-    完全一致検索と非わかち書き検索のみを行う
-
-    -4
-
-    部分一致検索のみを行う
-
-    -5
-
-    完全一致検索と部分一致検索のみを行う
-
-    -6
-
-    非わかち書き検索と部分一致検索のみを行う
-
-    -7
-
-    完全一致検索,非わかち書き検索,部分一致検索の全てを行う
-
-    例:
-
-    *E10,3
-
-    検索結果数が10件以下だった場合に検索処理方法を順次切り替え、スコアを3ずつ小さ くします。
-
-  [*D演算子]
-    結合演算子の既定値(演算子を省略した場合にどの演算を行うか)を指定します。指定できる演 算子は、OR, +, - のいずれかです。
-
-    例1:
-
-    *D+ abc def
-
-    abcとdefを両方含む文書を検索します。
-
-    例2:
-
-    *DOR abc def
-
-    abcとdefのいずれかを含む文書を検索します。
-
-  [*W[数値[:重み][,数値[:重み]]...]
-    数値で指定されたセクション番号のみを対象に検索します。セクションごとに検索スコア
-    の倍数を指定することができます。重みは、省略された場合1となります。負の重みも指 定することができます。
-
-script形式 [3]
-
-ECMAScript風の構文で検索条件やレコードへの操作を記述します。
-
-式中のIDENTIFIER(識別子)は、以下のいずれかを指します。
-
-[引数名]
-  grn式が受け取る引数の名前
-
-[カラム名]
-  操作対象としているレコードのカラム名
-
-[型名・関数名・テーブル名]
-  データベースに定義された型・テーブル・関数の名前
-
-
-== 説明
-
-grn式は、検索条件やデータベースへの操作を表現するために使用される文字列の形式です。
-
-selectやloadなどのいくつかの組込コマンドや、API関数grn_table_select()などで使用されます。grn式はquery
-形式とscript形式という2種類の方式で記述することができます。query形式は、多くのweb検索エンジンなどで検索フォームにユーザが指定
-可能なクエリ文字列の書式に合わせた形式です。script形式は、ECMAScriptの構文から式(expression)以下の構文要素を抜粋
-した形式になっており、文(statement)や制御構造などは表現できません。
-
-query形式のgrn式もscript形式のgrn式も、共通の中間形式に翻訳された上で処理されますので、処理速度や効率には差違はありません。
-記述できる処理の範囲はscript形式の方がquery形式より広くなっています。たとえば更新系の操作はscript形式のみで記述できます。
-
-DB-APIレイヤでは、異なる形式で記述された複数のgrn式を結合することも可能です。
-
-
-== 例
-
-query形式でcolumn1の値が'hoge'に等しいという条件
-
-column1:hoge
-
-script形式でcolumn1の値が'hoge'に等しいという条件
-
-column1 == "hoge"
-
-
-== 構文
-
-query形式のgrn式で有効な式の構文を拡張BNF記法で示します。
-
-  query             ::= query_element
-            | ( query query_element )
-            | ( query "+" query_element )
-            | ( query "-" query_element )
-            | ( query "OR" query_element )
-  query_element     ::= STRING
-                    | ( "(" query ")" )
-                    | ( IDENTIFIER relative_operator query_element )
-  relative_operator ::= ( ":" | ":!" | ":<" | ":>" | ":<=" | ":>=" | ":@" )
-
-script形式のgrn式で有効な式の構文を拡張BNF記法で示します。
-
-  expression                   ::= assignment_expression
-  expression                   ::= ( expression "," assignment_expression )
-  assignment_expression        ::= conditional_expression
-                            | ( lefthand_side_expression assign_operator assignment_expression )
-  assign_operator              ::= ( "=" | "*=" | "/=" | "%=" | "+=" | "-=" | "<<=" | ">>=" | ">>>=" | "&=" | "^=" | "|=" )
-  conditional_expression       ::= logical_or_expression
-                             | ( logical_or_expression "?" assignment_expression ":" assignment_expression )
-  logical_or_expression        ::= logical_and_expression
-                            | ( logical_or_expression "||" logical_and_expression )
-  logical_and_expression       ::= bitwise_or_expression
-                             | ( logical_and_expression logical_and_operator bitwise_or_expression )
-  logical_and_operator         ::= ( "&&" | "&!" )
-  bitwise_or_expression        ::= bitwise_xor_expression
-                            | ( bitwise_or_expression "|" bitwise_xor_expression )
-  bitwise_xor_expression       ::= bitwise_and_expression
-                             | ( bitwise_xor_expression "^" bitwise_and_expression )
-  bitwise_and_expression       ::= equality_expression
-                             | bitwise_and_expression "&" equality_expression )
-  equality_expression          ::= relational_expression
-                          | ( equality_expression equality_operator relational_expression )
-  equality_operator            ::= ( "==" | "!=" )
-  relational_expression        ::= shift_expression
-                            | ( relational_expression relational_operator shift_expression )
-  relational_operator          ::= ( "<" | ">" | "<=" | ">=" | "in" | "@" )
-  shift_expression             ::= additive_expression
-                       | ( shift_expression shift_operator additive_expression )
-  shift_operator               ::= ( "<<" | ">>" | ">>>" )
-  additive_expression          ::= multiplicative_expression
-                          | ( additive_expression additive_operator multiplicative_expression )
-  additive_operator            ::= ( "+" | "-" )
-  multiplicative_expression    ::= unary_expression
-                                | ( multiplicative_expression multiplicative_operator unary_expression )
-  multiplicative_operator      ::= ( "*" | "/" | "%" )
-  unary_expression             ::= postfix_expression
-                       | ( unary_operator unary_expression )
-  unary_operator               ::= ( "delete" : "++" : "--" : "+" : "-" : "!" : "~" )
-  postfix_expression           ::= lefthand_side_expression
-                         | ( lefthand_side_expression postfix_operator )
-  postfix_operator             ::= ( "++" | "--" )
-  lefthand_side_expression     ::= (call_expression | member_expression)
-  call_expression              ::= member_expression arguments
-  member_expression            ::= primary_expression
-  member_expression            ::= member_expression member_expression_part
-  primary_expression           ::= object_literal
-                         | ( "(" expression ")" )
-                         | IDENTIFIER
-                         | array_literal
-                         | DECIMAL
-                         | HEX_INTEGER
-                         | STRING
-                         | "true"
-                         | "false
-                         | "null"
-  array_literal                ::= ( "[" elision "]" )
-                    | ( "[" `element_list elision` "]" )
-                    | ( "[" element_list "]" )
-  elision                      ::= "," | ( elision "," )
-  element_list                 ::= assignment_expression
-                   | ( elision assignment_expression )
-                   | ( element_list elision assignment_expression )
-  object_literal               ::= ( "{" property_name_and_value_list "}" )
-  property_name_and_value_list ::= ( property_name_and_value_list "," property_name_and_value )
-  property_name_and_value      ::= ( property_name ":" assignment_expression )
-  property_name                ::= IDENTIFIER | STRING | DECIMAL
-  member_expression_part       ::= "[" expression "]" | ( "." IDENTIFIER )
-  arguments                    ::= ( "(" argument_list ")" )
-  argument_list                ::= assignment_expression | ( argument_list "," assignment_expression )
-
--[ 脚注 ]-
-
-[1] 補助演算子はv1.0でサポートされます。
-
-[2] プラグマはv1.0でサポートされます。
-
-[3] script形式のgrn式はv1.0でサポートされます。

data/test-unit/Rakefile

@@ -1,40 +0,0 @@
-# -*- ruby -*-
-
-require 'rubygems'
-gem 'rdoc'
-require 'hoe'
-require './lib/test/unit/version.rb'
-
-ENV["NODOT"] = "yes"
-
-version = Test::Unit::VERSION
-ENV["VERSION"] = version
-Hoe.spec('test-unit') do |p|
-  Hoe::Test::SUPPORTED_TEST_FRAMEWORKS[:testunit2] = "test/run-test.rb"
-  p.version = version
-  p.developer('Kouhei Sutou', 'kou@cozmixng.org')
-  p.developer('Ryan Davis', 'ryand-ruby@zenspider.com')
-
-  # Ex-Parrot:
-  # p.developer('Nathaniel Talbott', 'nathaniel@talbott.ws')
-end
-
-task :check_manifest => :clean_test_result
-task :check_manifest => :clean_coverage
-
-task :clean_test_result do
-  test_results = Dir.glob("**/.test-result")
-  sh("rm", "-rf", *test_results) unless test_results.empty?
-end
-
-task :clean_coverage do
-  sh("rm", "-rf", "coverage")
-end
-
-task :tag do
-  message = "Released Test::Unit #{version}!"
-  base = "svn+ssh://#{ENV['USER']}@rubyforge.org/var/svn/test-unit/"
-  sh 'svn', 'copy', '-m', message, "#{base}trunk", "#{base}tags/#{version}"
-end
-
-# vim: syntax=Ruby

data/test-unit/TODO

@@ -1,5 +0,0 @@
-* mock.
-* data-driven test.
-* port ruby trunk's assert_equal's intelligent inspection
-  when inspected expected and actual are same content
-  string.

data/test-unit/bin/testrb

@@ -1,5 +0,0 @@
-#!/usr/bin/env ruby
-require 'test/unit'
-(r = Test::Unit::AutoRunner.new(true)).process_args(ARGV) or
-  abort r.options.banner + " tests..."
-exit r.run

data/test-unit/html/classic.html

@@ -1,15 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<title>Test::Unit (Classic)</title>
-</head>
-<body bgcolor="red">
-<p style="text-align: center">
-  <img height="161" width="308" src="test-unit-classic.png">
-  <br>
-  <br>
-  <br>
-  Read the <a href="classic/test-unit/">rdoc</a>
-</p>
-</body>
-</html>

data/test-unit/html/index.html

@@ -1,25 +0,0 @@
-<?xml version="1.0" encoding="utf-8" ?>
-<!DOCTYPE html
-  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-  <head>
-    <meta http-equiv="Content-type" content="text/html; charset=utf-8" />
-    <title>Test::Unit - a Unit Testing Framework for Ruby</title>
-  </head>
-  <body>
-    <h1>Test::Unit - a Unit Testing Framework for Ruby</h1>
-    <p>[<a href="index.html.ja">Japanese</a>]</p>
-    <ul>
-      <li><a href="http://rubyforge.org/projects/test-unit/">Project Page</a></li>
-      <li>
-        <a href="test-unit/">RDoc</a>
-        <!--(<a href="ja/test-unit/">ja</a>)-->
-      </li>
-      <li>
-        <a href="classic.html">Classic</a>
-        <!--(<a href="ja/classic.html">ja</a>)-->
-      </li>
-    </ul>
-  </body>
-</html>

data/test-unit/html/index.html.ja

@@ -1,27 +0,0 @@
-<?xml version="1.0" encoding="utf-8" ?>
-<!DOCTYPE html
-  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" lang="ja" xml:lang="ja">
-  <head>
-    <meta http-equiv="Content-type" content="text/html; charset=utf-8" />
-    <title>Test::Unit - Ruby用単体テストフレームワーク</title>
-  </head>
-  <body>
-    <h1>Test::Unit - Ruby用単体テストフレームワーク</h1>
-    <p>[<a href="./">English</a>]</p>
-    <ul>
-      <li>
-        <a href="http://rubyforge.org/projects/test-unit/">プロジェクトページ</a>
-      </li>
-      <li>
-        <!--<a href="ja/test-unit/">RDoc</a>-->
-        RDoc(<a href="test-unit/">en</a>)
-      </li>
-      <li>
-        <!--<a href="classic.html.html">Classic</a>-->
-        Classic(<a href="classic.html">en</a>)
-      </li>
-    </ul>
-  </body>
-</html>

data/test-unit/lib/test/unit.rb

@@ -1,323 +0,0 @@
-require 'test/unit/testcase'
-require 'test/unit/autorunner'
-
-module Test # :nodoc:
-  #
-  # = Test::Unit - Ruby Unit Testing Framework
-  # 
-  # == Introduction
-  # 
-  # Unit testing is making waves all over the place, largely due to the
-  # fact that it is a core practice of XP. While XP is great, unit testing
-  # has been around for a long time and has always been a good idea. One
-  # of the keys to good unit testing, though, is not just writing tests,
-  # but having tests. What's the difference? Well, if you just _write_ a
-  # test and throw it away, you have no guarantee that something won't
-  # change later which breaks your code. If, on the other hand, you _have_
-  # tests (obviously you have to write them first), and run them as often
-  # as possible, you slowly build up a wall of things that cannot break
-  # without you immediately knowing about it. This is when unit testing
-  # hits its peak usefulness.
-  # 
-  # Enter Test::Unit, a framework for unit testing in Ruby, helping you to
-  # design, debug and evaluate your code by making it easy to write and
-  # have tests for it.
-  # 
-  # 
-  # == Notes
-  # 
-  # Test::Unit has grown out of and superceded Lapidary.
-  # 
-  # 
-  # == Feedback
-  # 
-  # I like (and do my best to practice) XP, so I value early releases,
-  # user feedback, and clean, simple, expressive code. There is always
-  # room for improvement in everything I do, and Test::Unit is no
-  # exception. Please, let me know what you think of Test::Unit as it
-  # stands, and what you'd like to see expanded/changed/improved/etc. If
-  # you find a bug, let me know ASAP; one good way to let me know what the
-  # bug is is to submit a new test that catches it :-) Also, I'd love to
-  # hear about any successes you have with Test::Unit, and any
-  # documentation you might add will be greatly appreciated. My contact
-  # info is below.
-  # 
-  # 
-  # == Contact Information
-  # 
-  # A lot of discussion happens about Ruby in general on the ruby-talk
-  # mailing list (http://www.ruby-lang.org/en/ml.html), and you can ask
-  # any questions you might have there. I monitor the list, as do many
-  # other helpful Rubyists, and you're sure to get a quick answer. Of
-  # course, you're also welcome to email me (Nathaniel Talbott) directly
-  # at mailto:testunit@talbott.ws, and I'll do my best to help you out.
-  # 
-  # 
-  # == Credits
-  # 
-  # I'd like to thank...
-  # 
-  # Matz, for a great language!
-  # 
-  # Masaki Suketa, for his work on RubyUnit, which filled a vital need in
-  # the Ruby world for a very long time. I'm also grateful for his help in
-  # polishing Test::Unit and getting the RubyUnit compatibility layer
-  # right. His graciousness in allowing Test::Unit to supercede RubyUnit
-  # continues to be a challenge to me to be more willing to defer my own
-  # rights.
-  # 
-  # Ken McKinlay, for his interest and work on unit testing, and for his
-  # willingness to dialog about it. He was also a great help in pointing
-  # out some of the holes in the RubyUnit compatibility layer.
-  # 
-  # Dave Thomas, for the original idea that led to the extremely simple
-  # "require 'test/unit'", plus his code to improve it even more by
-  # allowing the selection of tests from the command-line. Also, without
-  # RDoc, the documentation for Test::Unit would stink a lot more than it
-  # does now.
-  # 
-  # Everyone who's helped out with bug reports, feature ideas,
-  # encouragement to continue, etc. It's a real privilege to be a part of
-  # the Ruby community.
-  # 
-  # The guys at RoleModel Software, for putting up with me repeating, "But
-  # this would be so much easier in Ruby!" whenever we're coding in Java.
-  # 
-  # My Creator, for giving me life, and giving it more abundantly.
-  # 
-  # 
-  # == License
-  # 
-  # Test::Unit is copyright (c) 2000-2003 Nathaniel Talbott. It is free
-  # software, and is distributed under the Ruby license. See the COPYING
-  # file in the standard Ruby distribution for details.
-  # 
-  # 
-  # == Warranty
-  # 
-  # This software is provided "as is" and without any express or
-  # implied warranties, including, without limitation, the implied
-  # warranties of merchantibility and fitness for a particular
-  # purpose.
-  # 
-  # 
-  # == Author
-  # 
-  # Nathaniel Talbott.
-  # Copyright (c) 2000-2003, Nathaniel Talbott
-  #
-  # ----
-  #
-  # = Usage
-  #
-  # The general idea behind unit testing is that you write a _test_
-  # _method_ that makes certain _assertions_ about your code, working
-  # against a _test_ _fixture_. A bunch of these _test_ _methods_ are
-  # bundled up into a _test_ _suite_ and can be run any time the
-  # developer wants. The results of a run are gathered in a _test_
-  # _result_ and displayed to the user through some UI. So, lets break
-  # this down and see how Test::Unit provides each of these necessary
-  # pieces.
-  #
-  #
-  # == Assertions
-  #
-  # These are the heart of the framework. Think of an assertion as a
-  # statement of expected outcome, i.e. "I assert that x should be equal
-  # to y". If, when the assertion is executed, it turns out to be
-  # correct, nothing happens, and life is good. If, on the other hand,
-  # your assertion turns out to be false, an error is propagated with
-  # pertinent information so that you can go back and make your
-  # assertion succeed, and, once again, life is good. For an explanation
-  # of the current assertions, see Test::Unit::Assertions.
-  #
-  #
-  # == Test Method & Test Fixture
-  #
-  # Obviously, these assertions have to be called within a context that
-  # knows about them and can do something meaningful with their
-  # pass/fail value. Also, it's handy to collect a bunch of related
-  # tests, each test represented by a method, into a common test class
-  # that knows how to run them. The tests will be in a separate class
-  # from the code they're testing for a couple of reasons. First of all,
-  # it allows your code to stay uncluttered with test code, making it
-  # easier to maintain. Second, it allows the tests to be stripped out
-  # for deployment, since they're really there for you, the developer,
-  # and your users don't need them. Third, and most importantly, it
-  # allows you to set up a common test fixture for your tests to run
-  # against.
-  #
-  # What's a test fixture? Well, tests do not live in a vacuum; rather,
-  # they're run against the code they are testing. Often, a collection
-  # of tests will run against a common set of data, also called a
-  # fixture. If they're all bundled into the same test class, they can
-  # all share the setting up and tearing down of that data, eliminating
-  # unnecessary duplication and making it much easier to add related
-  # tests.
-  #
-  # Test::Unit::TestCase wraps up a collection of test methods together
-  # and allows you to easily set up and tear down the same test fixture
-  # for each test. This is done by overriding #setup and/or #teardown,
-  # which will be called before and after each test method that is
-  # run. The TestCase also knows how to collect the results of your
-  # assertions into a Test::Unit::TestResult, which can then be reported
-  # back to you... but I'm getting ahead of myself. To write a test,
-  # follow these steps:
-  #
-  # * Make sure Test::Unit is in your library path.
-  # * require 'test/unit' in your test script.
-  # * Create a class that subclasses Test::Unit::TestCase.
-  # * Add a method that begins with "test" to your class.
-  # * Make assertions in your test method.
-  # * Optionally define #setup and/or #teardown to set up and/or tear
-  #   down your common test fixture.
-  # * You can now run your test as you would any other Ruby
-  #   script... try it and see!
-  #
-  # A really simple test might look like this (#setup and #teardown are
-  # commented out to indicate that they are completely optional):
-  #
-  #     require 'test/unit'
-  #     
-  #     class MyTest < Test::Unit::TestCase
-  #       # def setup
-  #       # end
-  #     
-  #       # def teardown
-  #       # end
-  #     
-  #       def test_fail
-  #         assert(false, 'Assertion was false.')
-  #       end
-  #     end
-  #
-  #
-  # == Test Runners
-  #
-  # So, now you have this great test class, but you still
-  # need a way to run it and view any failures that occur
-  # during the run. There are some test runner; console test
-  # runner, GTK+ test runner and so on. The console test
-  # runner is automatically invoked for you if you require
-  # 'test/unit' and simply run the file. To use another
-  # runner simply set default test runner ID to
-  # Test::Unit::AutoRunner:
-  #
-  #    require 'test/unit'
-  #    Test::Unit::AutoRunner.default_runner = "gtk2"
-  #
-  # == Test Suite
-  #
-  # As more and more unit tests accumulate for a given project, it
-  # becomes a real drag running them one at a time, and it also
-  # introduces the potential to overlook a failing test because you
-  # forget to run it. Suddenly it becomes very handy that the
-  # TestRunners can take any object that returns a Test::Unit::TestSuite
-  # in response to a suite method. The TestSuite can, in turn, contain
-  # other TestSuites or individual tests (typically created by a
-  # TestCase). In other words, you can easily wrap up a group of
-  # TestCases and TestSuites.
-  #
-  # Test::Unit does a little bit more for you, by wrapping
-  # these up automatically when you require
-  # 'test/unit'. What does this mean? It means you could
-  # write the above test case like this instead:
-  #
-  #  require 'test/unit'
-  #  require 'test_myfirsttests'
-  #  require 'test_moretestsbyme'
-  #  require 'test_anothersetoftests'
-  #
-  # Test::Unit is smart enough to find all the test cases existing in
-  # the ObjectSpace and wrap them up into a suite for you. It then runs
-  # the dynamic suite using the console TestRunner.
-  #
-  #
-  # == Configuration file
-  #
-  # Test::Unit reads 'test-unit.yml' in the current working
-  # directory as Test::Unit's configuration file. It can
-  # contain the following configurations:
-  #
-  # * color scheme definitions
-  # * test runner to be used
-  # * test runner options
-  # * test collector to be used
-  #
-  # Except color scheme definitions, all of them are
-  # specified by command line option.
-  #
-  # Here are sample color scheme definitions:
-  #
-  #   color_schemes:
-  #     inverted:
-  #       success:
-  #         name: red
-  #         bold: true
-  #       failure:
-  #         name: green
-  #         bold: true
-  #     other_scheme:
-  #       ...
-  #
-  # Here are the syntax of color scheme definitions:
-  #
-  #  color_schemes:
-  #    SCHEME_NAME:
-  #      EVENT_NAME:
-  #        name: COLOR_NAME
-  #        intensity: BOOLEAN
-  #        bold: BOOLEAN
-  #        italic: BOOLEAN
-  #        underline: BOOLEAN
-  #      ...
-  #    ...
-  #
-  # SCHEME_NAME:: the name of the color scheme
-  # EVENT_NAME:: one of [success, failure, pending,
-  #              omission, notification, error]
-  # COLOR_NAME:: one of [black, red, green, yellow, blue,
-  #              magenta, cyan, white]
-  # BOOLEAN:: true or false
-  #
-  # You can use the above 'inverted' color scheme with the
-  # following configuration:
-  #
-  #   runner: console
-  #   console_options:
-  #     color_scheme: inverted
-  #   color_schemes:
-  #     inverted:
-  #       success:
-  #         name: red
-  #         bold: true
-  #       failure:
-  #         name: green
-  #         bold: true
-  #
-  # == Questions?
-  #
-  # I'd really like to get feedback from all levels of Ruby
-  # practitioners about typos, grammatical errors, unclear statements,
-  # missing points, etc., in this document (or any other).
-  #
-
-  module Unit
-    # Set true when Test::Unit has run.  If set to true Test::Unit
-    # will not automatically run at exit.
-    def self.run=(flag)
-      @run = flag
-    end
-
-    # Already tests have run?
-    def self.run?
-      @run ||= false
-    end
-  end
-end
-
-at_exit do
-  unless $! || Test::Unit.run?
-    exit Test::Unit::AutoRunner.run
-  end
-end