Permalink
Commits on Mar 27, 2015
Commits on Mar 16, 2015
  1. Increment to v0.36.

    committed Mar 16, 2015
  2. Timestamp v0.35.

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

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

    committed Mar 15, 2015
  3. Try installing GraphViz.

    committed Mar 15, 2015
  4. Try to build and test without sudo.

    committed Mar 15, 2015
  5. Fix failing GraphViz tests.

    By using debug output instead of canonical output. Resolves #7.
    committed Mar 15, 2015
  6. Update copyright and URL links.

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

    committed Mar 14, 2015
  2. Get the URLs right.

    committed Mar 14, 2015
  3. Badges. Stinkin badges.

    committed Mar 14, 2015
  4. Just use prove.

    committed Mar 14, 2015
  5. Re-enable sudo.

    To hopefully fix the permission denied error from Travis-CI in t/leak.t.
    committed Mar 14, 2015
  6. Increment to v0.35.

    committed Mar 14, 2015
  7. Increment to v0.34 and timestamp.

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

    So go back to v0.33 and release again.
    committed Mar 14, 2015
  9. Try using Perl Travis helper.

    Will get coverage, too.
    committed Mar 14, 2015
  10. Increment to v0.34.

    committed Mar 14, 2015
  11. Timestamp v0.33.

    committed Mar 14, 2015
  12. Remove Pod tests.

    committed Mar 14, 2015
  13. Fix segfault on Perl 5.6.

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

    committed Mar 12, 2015
Commits on Mar 10, 2015
  1. Add .travis.yml.

    committed Mar 10, 2015
  2. Explain how we test for leaks.

    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.
    committed Mar 10, 2015
  3. Fix rule circular reference memory leak.

    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.
    committed Mar 10, 2015
Commits on Oct 17, 2013
  1. Add test to detect memory leaks in the future.

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

    committed Oct 16, 2013
  2. Timestamp v0.32.

    committed Oct 16, 2013
  3. Fix memory leak due to circular references.

    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.
    committed Oct 16, 2013
Commits on May 2, 2012
  1. Increment to v0.32.

    committed May 2, 2012
  2. Timestamp v0.31.

    committed May 2, 2012