Update README and bump version number in anticipation of release.
catseye
10 years ago
0 | 0 |
-- encoding: UTF-8
|
1 | 1 |
name: Falderal
|
2 | |
version: 0.5
|
|
2 |
version: 0.6
|
3 | 3 |
cabal-version: >= 1.8
|
4 | 4 |
build-type: Simple
|
5 | 5 |
license: BSD3
|
75 | 75 |
History
|
76 | 76 |
-------
|
77 | 77 |
|
|
78 |
Version 0.6 "Streeterville" (currently under development):
|
|
79 |
|
|
80 |
* Variables may be included in the specification of a shell command
|
|
81 |
implementation; these will be expanded before generating the results
|
|
82 |
generator. These variable include `%(test-text)`, `%(test-file)`,
|
|
83 |
and `%(output-file)`.
|
|
84 |
* `falderal` now lets the user specify how a functionality is implemented
|
|
85 |
on the command line. Giving `-f 'foo:shell command "foo.sh %(test-file)"'`
|
|
86 |
has the same effect as including the pragma `Functionality "foo" is
|
|
87 |
implemented by shell command "foo.sh %(test-file)"` in the Falderal
|
|
88 |
file.
|
|
89 |
* The Markdown formatter now formats Bird-style embedded code with
|
|
90 |
HTML embedded in the Markdown document. This is so that it can
|
|
91 |
be styled independently from, and thus distinguished from, any plain
|
|
92 |
Markdown indented code blocks which may appear in the literate portion
|
|
93 |
of the source code.
|
|
94 |
|
|
95 |
TODO:
|
|
96 |
|
|
97 |
* Rename the variables to conform to what's listed above.
|
|
98 |
* Make `%(output-file)` properly optional.
|
|
99 |
* Update the format specification re those variables.
|
|
100 |
* Command-line option to clear functionalities.
|
|
101 |
* Command-line option to skip tests for given functionalities.
|
|
102 |
|
78 | 103 |
Version 0.5 "The Loop" (current released version):
|
79 | 104 |
|
80 | 105 |
* The command-line format of `falderal` has changed, for the better.
|