Re: Finding a safe char with tr///d

Nice++. I could have used this recently in Re: Cleaning Data Between Specified Columns (the original version at the bottom).

If you used $possible_safe = join'', map chr, 0 .. 255; your pretty much guarenteed to find a safe char to use. (You might need to temporarially disable utf-8 if your dealing with unicode stuff I guess.)

Examine what is said, not who speaks.

The 7th Rule of perl club is -- pearl clubs are easily damaged. Use a diamond club instead.

Comment on Re: Finding a safe char with tr///d Download Code

Replies are listed 'Best First'.
Re^2: Finding a safe char with tr///d by Aristotle (Chancellor) on Jan 31, 2003 at 04:21 UTC
Except you're in for some funny looks when what happens to be a "safe character" is an open paren, bracket, etc. `:-)` Makeshifts last the longest.	[reply]
Re: Re^2: Finding a safe char with tr///d by BrowserUk (Patriarch) on Jan 31, 2003 at 04:37 UTC
Ain't that what \Q and \E are for:)... I know, I know... you'd have to monkey with the regex as well. Silly me. On a related note, it good to know I'm not the only one who uses control chars as temporary placeholders in strings. I agree that 0x7f was a bad choice in a utf-8/unicode world. Using a BOM like "\xEF\xBB\xBF" might make some sense though. Examine what is said, not who speaks. The 7th Rule of perl club is -- pearl clubs are easily damaged. Use a diamond club instead.	[reply]