Andy Lester
Andy Lester
That compile-time vs. run-time explains everything. I wonder if doing the `qr//` in an `eval` block would be "compile-time" enough. (Not that we want to use `eval` here after we...
I think we might already have a ticket on this suggestion. It's a common one.
I've made a new ticket #247 for cscope.out
https://speakerdeck.com/patch/unicode-best-practices
The make run: ``` "/u/tux/bin/perl" t/runtests.pl 0 0 "blib/lib" "blib/arch" t/*.t Running tests on blib/script/ack, ACK_TEST_STANDALONE=0 t/ack-c.t .................... ok t/ack-color.t ................ ok t/ack-column.t ............... ok t/ack-create-ackrc.t ......... ok t/ack-dump.t ....................
The first taint checks should go away with the current `dev` branch because I've removed the `-T` from all the tests.
Many of the rest of the failures seem to be related to the handling of temp files. ``` # $got->[2]{path} = '/S0W1/tmp/EgkADC9vph/foo/bar/.ackrc' # $expected->[2]{path} = '/tmp/EgkADC9vph/foo/bar/.ackrc' ``` Do you know...
> Should ack have the same? Would you use it? What would the use case be?
Sample failure: ``` t/ack-man.t .................. # Failed test 'Nothing in STDERR' # at t/ack-man.t line 60. # [ # 'stty: standard input: Inappropriate ioctl for device' # ] # Failed...
Working on this in the `pathing` branch.