Remove boolean traps in Option

Create issue
Issue #152 resolved
Jesper Öqvist created an issue

Add subclass to handle options that take values in order to remove boolean traps in Option constructors.

Comments (1)

  1. Jesper Öqvist reporter

    Improved option parsing and handling

    • Improved Option API by removing boolean traps in constructors
    • Do not let accepted values collection be null!
    • Represent indentation using number of spaces rather than String object
    • Removed CommandLineArguments class - replaced by ArgumentParser
    • ArgumentParser has list of filenames rather than operands
    • ArgumentParser works with prefix map to speed up option matching
    • Renamed JastAddConfiguration to Configuration
    • Added subclass ValueOption of Option
      • Option now only handles options without values
      • ValueOption handles options with values
    • Added anonymous classes for each option that handle option matching
    • Added package org.jastadd.option for option handling classes
    • Simplified option matching - all work is now done in ArgumentParser
    • Print warning when non-accepted option value is encountered
    • Improved cache option checking

    fixes issue #152 (bitbucket)

    → <<cset 0f7357b945a2>>

  2. Log in to comment