Remove negative options (noXxx)

Issue #155 resolved
Jesper Öqvist created an issue

The noXxx options should be made deprecated, then removed from JastAdd. We can use value options instead i.e. xxx={true|false}.

Comments (2)

  1. Jesper Öqvist reporter

    Added TODOs for negative (noXxx) options

    • added TODOs for deprecating negative options
    • undeprecated some positive options - these will replace the corresponding negative options

    see issue #155 (bitbucket)

    → <<cset 0e27395a849c>>

  2. Jesper Öqvist reporter

    Refactored JastAdd options and configuration

    Deprecated options:

    • doc (unused)
    • java1.4 (not tested)
    • noLazyMaps (equivalent to lazyMaps=false)
    • noVisitCheck (equivalent to visitCheck=flase)
    • noCacheCycle (equivalent to cacheCycle=false)
    • noRefineLegacy (equivalent to refineLegacy=false)
    • noComponentCheck (componentCheck was already off by default)
    • noInhEqCheck (equivalent to inhEqCheck=false)
    • noStatic (the name was misleading, renamed to staticState)
    • deterministic (collection attributes are now always deterministic)

    New or updated options:

    • staticState (replaces noStatic)
    • incremental: added 'all' option

    Code generation changes

    • Don't generate ASTNode$State.IdentityHashSet

    Template variable chnages:

    • removed Deterministic (no longer relevant)
    • removed CircularEnabled (was always enabled)
    • removed NoStatic
    • added StaticState (replaces NoStatic)

    Improved JastAddTask. Should now be closer to the command-line interface.

    fixes issue #155 (bitbucket)

    → <<cset f1466f19c423>>

  3. Log in to comment