in reply to Re^4: Unicode character handling with Net::Telnet::Cisco
in thread Unicode character handling with Net::Telnet::Cisco

Then the string didn't contain what you said it did. decode_utf8 does character decoding, not JavaScript-ish string literal parsing.

>perl -MEncode -E"$_=decode_utf8('\u0000\r\n'); say; s/\0//g; say" \u0000\r\n \u0000\r\n

Replies are listed 'Best First'.
Re^6: Unicode character handling with Net::Telnet::Cisco
by josh803316 (Beadle) on Jul 23, 2010 at 18:37 UTC
    Yes, you are correct, that's probably why I was confused and having a hard time with it as well. I didn't have visibility into what the string was....from the bug report/customer site it seems the null value was later being converted into that string. Thank you for your help though!!! I appreciate you taking your time to help me out and guide me!