Closed meisl closed 10 years ago
Re color output on Windows: right now I think it's fine enough to simply filter the output through perl5's Win32::Console::ANSI
; like so:
perl6 MyGrammar.pm | perl -e "use Win32::Console::ANSI; print while (<>)"
Alternatively, use Console2, or AnsiCon, which know how to interpret the ANSI color codes. :-)
Thanks for the patches!
Thanks & yw :)
Console2: http://www.hanselman.com/blog/Console2ABetterWindowsCommandPrompt.aspx AnsiCon: https://github.com/adoxa/ansicon
Crossed out the stuff that's in pr #7.
BUILD
,MATCH
,orig
, etc. (also fixes issue #4)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(added some hints to README)use Term::ANSIColor
ain't enough on Win, and there's no perl6 equiv of Win32::Console::ANSI yet)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 :)factor out the actual thing to do on enter/leave regexbreakpoints to be handled with that then), thus a) consolidatingTracer/Debugger/Profiler and b) make tests easier and c) open up&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)at least enough to feel safe for refactoring)