jnthn/grammar-debugger — pull request #6 by meisl (2014-09-02 22:18:15+00:00)
Title: Make it work under Win32/Rakudo* 2014.03.01 (again)

- fixed "bustage" as mentioned in https://github.com/jnthn/grammar-debugger/issues/2#issuecomment-19873420 (at least for me, on the system mentioned in title)
- made it more robust by intercepting only methods of type Regex rather than testing for "magical" names like 'BUILD', 'MATCH', 'orig', etc.
- added 1 sanity test for Debugger (giving it the input that it expects)

Although I'm pretty confident that taking this pull request as is will only make it work better (or, as in my case: *work at all*) - there are quite a few things that I hope to be able to provide soon; as listed below:

- TODO: enable color output on Win Console or simply output w/out color (just `use Term::ANSIColor` ain't enough on Win, and there's no perl6 equiv of Win32::Console::ANSI yet)
- TODO: refactor to eliminate code-dup between Tracer & Debugger, as well as provide same functionality as Grammar::Profiler::Simple (which is more or less stolen anyways :)
- TODO: factor out the actual thing to do on enter/leave regex (breakpoints would be handled with this then), thus a) consolidating Tracer/Debugger/Profiler and b) make tests easier and c) open up
- TODO: make it faster by installing wrappers around regex methods *once* at the time `&add_method` is called rather than creating a new lambda *every time* `&find_method` is called (current perf is *really* near unacceptable in my setup)
- TODO: more tests
- TODO: test on more than just the one system mentioned in title