Re: Module Design Ideas - HTML Entity Reference

Replies are listed 'Best First'.
Re^2: Module Design Ideas - HTML Entity Reference by John M. Dlugosz (Monsignor) on May 10, 2011 at 23:53 UTC
I had not seen that. I don't care for it though: Why is `$u->u5c0f;`, after creating `$u`, which generates a different method for every character the first time it is used, any better or easier than just writing `"\x{5c0f}"`? You would only use the literal method name call if you had the character code already as a compile-time literal, so what is the possible point? It also has `$u->name`, which seems to be identical to using \N{}. So why did you mention this module? Are you just mentioning things that show up on a keyword search without seeing what they actually are (which is what it gives the impression of; sorry if that's not the case), or is there something you want to discuss about this approach or the lessons it can teach? If that's the case, please elaborate.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^2: Module Design Ideas - HTML Entity Reference
by John M. Dlugosz (Monsignor) on May 10, 2011 at 23:53 UTC

$u->u5c0f;

$u

"\x{5c0f}"

It also has $u->name, which seems to be identical to using \N{}.

So why did you mention this module? Are you just mentioning things that show up on a keyword search without seeing what they actually are (which is what it gives the impression of; sorry if that's not the case), or is there something you want to discuss about this approach or the lessons it can teach? If that's the case, please elaborate.

[reply]
[d/l]
[select]