Just to note, uri_unescape is functionally:
s/%(\d\d)/chr $1/eg; if you don't even want to load the module. | [reply] [d/l] |
s/%([0-9A-Fa-f]{2})/chr(hex($1))/eg
In fact, that's pretty much exactly what's in URI::Escape, except that the module also handles scalar v. list context and multiple arguments. Using uri_unescape still seems preferable to me, since the resource overhead of using the module is basically nil and the mnemonic benefit of seeing uri_unescape instead of a regex is considerable. | [reply] [d/l] |
You know, you're completely correct, and that mostly proves your point about using a module. I theoretially knew what the proper code should be, but I wasn't paying attention and wrote something that was broken and didn't even think about it, the module would have been much easier.
| [reply] |