Re^4: Transform ASCII into UniCode (escape_metas)

[LanX]

> Why not test it directly, then?

I wanted to have a generic method for escaping selected metas while keeping others as is.

> what did I do wrong?

Took me a moment to understand (well guess) what's happening

Take case #2:

a\\b is internally the 3 char string a\b , so this escape b is untouched.

but you do a string interpolation for

eval "\$string =~ tr/$s/$r/r"

so whats happening is

  DB<57> say "a\\b" =~ tr/a\b/xyz/r # expected 'xyz'
x\b

  DB<58>

Actually I'm not sure what tr's interpretation of \b is here

Question is if your expectation was right, because the literal code gives my result (?)

C:\tmp\t_wperl>perl -E"say 'a\\b' =~ tr/a\b/xyz/r # expected 'xyz'"
x\b

C:\tmp\t_wperl>

update

I.o.W.

Your expectation is to have a 1-to-1 mapping of characters.

My expectation was to emulate tr like implemented and to catch injections.

It's a question of definition.

[LanX]

> Actually I'm not sure what tr's interpretation of \b is here

\b is the control character for backspace

  DB<62> p "a\bc"
c
  DB<63>

see also perlrebackslash

[choroba]

I see. I would expect the strings coming in to contain the characters to operate on, not strings that Perl can turn into the characters to operate on by evaluating them.

The \b is tricky, as I can use it to get three different results from my three subroutines:

# Add this to the list of cases:

    [ "a\b\\b" => '\\/',  'xy',  "a\bxb"]

# Results:

not ok 22 - simulate
#   Failed test 'simulate'
#   at ./2.pl line 64.
#          got: 'xb'
#     expected: 'xb'
ok 23 - cheat
Replacement list is longer than search list at (eval 45) line 1.
not ok 24 - use
#   Failed test 'use'
#   at ./2.pl line 66.
#          got: '\b'
#     expected: 'xb'

Switching to Test2::V0 explains the test 22:

not ok 22 - simulate
# Failed test 'simulate'
# at ./2.pl line 64.
# +-------+----+-------+
# | GOT   | OP | CHECK |
# +-------+----+-------+
# | a\bxb | eq | xb    |
# +-------+----+-------+

[LanX]

Sorry I'm too tired now, I'll check tomorrow.

Multiple levels of escaping are often kind of brainf*ck.

> would expect the strings coming in to contain the characters to operate on, not strings that Perl can turn into the characters to operate on by evaluating them.

this escape_metas can also be used with a character class [METAS] for with multiple metas.

> The \b is tricky, as I can use it to get three different results from my three subroutines:

exactly, as I said, it depends what the intended behavior is.

FWIW

my intention was to implement a sub tri = "transliterate interpolated" which allowed to write tri($input,$left,$right) and implemented $input =~ tr/LEFT/RIGHT/ while sticking close to tr's behaviour but without breaking.

I'll try again tomorrow. after GPW. :)