RELEASE 0.3
- Fixed a bug that globally changed the state of all modules
when a user chose to use the
'module SomeThing extend OptiFlag::Flagset(:flag_symbol => "/")'
syntax. Required some singleton class trickeration and module cloning.
- Changed all references from OptiFlag::FlagestDefinitions to
OptiFlag::Flagset which is shorter and therefore easier to use
(not everyone has dynamic-abbrev in emacs enabled to make typing easy)
- Started changing the design of printing help so that users can
register help-formatting bundles to do their own rendering of usage
and error messages
- Changed the functionality of the 'usage_flag' option to be of
either zero or one arity. With standard zero arity, the help will
print out the standard help/usage message. With an arity of one,
the help/usage flag will assume that the argument is another flag
for which we will print extended usage (example: '-h dir' will print
the help message just for the '-dir' flag)
- Fixed another nasty global-state bug (the perils of using '@' syntax
with modules)... This one wasn't needed -- it would only affect those
people who chose to parse an array of strings a 2nd and 3rd time, and
I was considering mandating that the parse method could only be called
once... but since my tests relied on multiple parses, I decided to fix
it just to make the test suites continually easy to write.
- Added a new top-level declarative form: 'optional_switch_flag' which
is an optional flag with zero arity. (I needed this one for myself)
- A few more tests were added:
- tc_basic_optional_flag.rb
- tc_bug_two.rb
- Wrote some XSLT and a ruby-script to autogenerate the site at
http://optiflag.rubyforge.org
- Added a warning generation system for things that are not errors
- extra parameters left over (implemented)
- potential consumption of an optional flag as value
to a flag with >0 arity. (example: '-dir -verbose' where
'-dir' takes on argument and '-verbose' is optional. In this
case the '-verbose' would be consumed as the value unless
warning mode was on)
|
