funit 0.11.0 → 0.11.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. data/History.txt +5 -0
  2. data/README.txt +7 -6
  3. data/lib/funit.rb +1 -1
  4. metadata +2 -2
data/History.txt CHANGED
@@ -1,3 +1,8 @@
1
+ === 0.11.1 / 2009-11-01
2
+
3
+ * 1 bug fix
4
+ * Documentation
5
+
1
6
  === 0.11.0 / 2009-11-01
2
7
 
3
8
  * 1 minor enhancement
data/README.txt CHANGED
@@ -13,13 +13,13 @@ set of testing-specific keywords and functions. FUnit transforms
13
13
  these fragments into valid Fortran code, compiles, links, and
14
14
  runs them against the code under test.
15
15
 
16
- FUnit is {opinionated software}[http://www.oreillynet.com/pub/a/network/2005/08/30/ruby-rails-david-heinemeier-hansson.html], which values convention over
17
- configuration. Specifically, FUnit,
16
+ FUnit is
17
+ {opinionated software}[http://www.oreillynet.com/pub/a/network/2005/08/30/ruby-rails-david-heinemeier-hansson.html],
18
+ which values convention over configuration. Specifically, FUnit requires,
18
19
 
19
- * requires a Fortran 95 compiler,
20
- * only supports testing routines contained in modules,
21
- * requires tests to be stored along side the code under test, and
22
- * requires test files to be named appropriately.
20
+ * a Fortran 95 compiler,
21
+ * tests to be stored along side the code under test, and
22
+ * test files to be named appropriately.
23
23
 
24
24
  == FEATURES/PROBLEMS:
25
25
 
@@ -90,6 +90,7 @@ these directories can be found in your Rubygems library directory, e.g., <tt>/us
90
90
  * Set FC environment variable to point to a Fortran compiler:
91
91
  * <tt>export FC=/path/of/Fortran/compiler</tt> (sh)
92
92
  * <tt>setenv FC /path/of/Fortran/compiler</tt> (csh)
93
+ * Other influential environment variables: FCFLAGS and LDFLAGS
93
94
 
94
95
  == LICENSE:
95
96
 
data/lib/funit.rb CHANGED
@@ -14,7 +14,7 @@ require 'fileutils'
14
14
 
15
15
  module Funit
16
16
 
17
- VERSION = '0.11.0'
17
+ VERSION = '0.11.1'
18
18
 
19
19
  ##
20
20
  # run all tests
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: funit
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.11.0
4
+ version: 0.11.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Karen Bibb
@@ -36,7 +36,7 @@ dependencies:
36
36
  - !ruby/object:Gem::Version
37
37
  version: 2.3.3
38
38
  version:
39
- description: FUnit is a unit testing framework for Fortran. Unit tests are written as Fortran fragments that use a small set of testing-specific keywords and functions. FUnit transforms these fragments into valid Fortran code, compiles, links, and runs them against the code under test. FUnit is {opinionated software}[http://www.oreillynet.com/pub/a/network/2005/08/30/ruby-rails-david-heinemeier-hansson.html], which values convention over configuration. Specifically, FUnit, * requires a Fortran 95 compiler, * only supports testing routines contained in modules, * requires tests to be stored along side the code under test, and * requires test files to be named appropriately.
39
+ description: FUnit is a unit testing framework for Fortran. Unit tests are written as Fortran fragments that use a small set of testing-specific keywords and functions. FUnit transforms these fragments into valid Fortran code, compiles, links, and runs them against the code under test. FUnit is {opinionated software}[http://www.oreillynet.com/pub/a/network/2005/08/30/ruby-rails-david-heinemeier-hansson.html], which values convention over configuration. Specifically, FUnit requires, * a Fortran 95 compiler, * tests to be stored along side the code under test, and * test files to be named appropriately.
40
40
  email: nasarb-developers@rubyforge.org
41
41
  executables:
42
42
  - funit