Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: master
Commits on Mar 27, 2015
Commits on Mar 16, 2015
  1. Increment to v0.36.

    authored
  2. Timestamp v0.35.

    authored
Commits on Mar 15, 2015
  1. Let the installer install Rest::Weaken.

    authored
    So that hopefully it will avoid doing so on 5.6, since it is not supported there.
  2. Require Storable 2.05.

    authored
  3. Install Test::Weaken on Travis.

    authored
  4. Try installing GraphViz.

    authored
  5. Fix failing GraphViz tests.

    authored
    By using debug output instead of canonical output. Resolves #7.
  6. Update copyright and URL links.

    authored
Commits on Mar 14, 2015
  1. Try coverage with all Perls.

    authored
  2. Get the URLs right.

    authored
  3. Badges. Stinkin badges.

    authored
  4. Just use prove.

    authored
  5. Re-enable sudo.

    authored
    To hopefully fix the permission denied error from Travis-CI in t/leak.t.
  6. Increment to v0.35.

    authored
  7. Increment to v0.34 and timestamp.

    authored
    Turns out I cannot upload 0.33 again, even though it failed. :-(.
  8. Need a version in FSA::State.

    authored
    So go back to v0.33 and release again.
  9. Try using Perl Travis helper.

    authored
    Will get coverage, too.
  10. Increment to v0.34.

    authored
  11. Timestamp v0.33.

    authored
  12. Remove Pod tests.

    authored
  13. Fix segfault on Perl 5.6.

    authored
    By requiring the pure Perl Data::Dumper for versions < 5.8. Thanks to
    @khwilliamson for the suggestion.
Commits on Mar 12, 2015
  1. Skip segfaulting test on 5.6.

    authored
Commits on Mar 10, 2015
  1. Add .travis.yml.

    authored
  2. Explain how we test for leaks.

    authored
    It takes advantage of the internals, using a string to mimic a memory address.
    But since it's those internals that cause the leak in the first place, I think
    this is a reaonable way to do the test. However, it could be confusing without
    signifant study, so leave a note for my future self to explain how this works
    and why.
  3. Fix rule circular reference memory leak.

    authored
    If you specify a state with a rule that point to a state that also has a rule
    that eventually point back to the first state, well, you'll get a memory
    leak. The fix is to weaken references to states in rules.
    
    Many thanks to @glasswalk3r for finally chasing down the proper fix, which in
    turn allowed me to do some poking to reproduce the leak as a test failure so
    that it can stay fixed.
    
    Closes #6.
Commits on Oct 17, 2013
  1. Add test to detect memory leaks in the future.

    authored
    I confirmed that it does indeed fail if I comment out either of the calls
    to `weaken()` in the module.
Commits on Oct 16, 2013
  1. Increment to v0.33.

    authored
  2. Timestamp v0.32.

    authored
  3. Fix memory leak due to circular references.

    authored
    Made the mistake of referencing the referenced, which meant that no FSA::Rules
    object was ever destroyed until program exit. Nasty memory leak!
    
    So use `Scalar::Util::weaken()` to weaken the circular references. This allows
    the objects to be destroyed when they exit scope. Resolves #3.
Commits on May 2, 2012
  1. Increment to v0.32.

    authored
  2. Timestamp v0.31.

    authored
Something went wrong with that request. Please try again.