develooper Front page | perl.perl5.porters | Postings from December 2015

Re: Obsolete text in utf8.pm

Thread Previous | Thread Next
From:
Father Chrysostomos
Date:
December 28, 2015 01:01
Subject:
Re: Obsolete text in utf8.pm
Message ID:
20151228010134.22345.qmail@lists-nntp.develooper.com
John Imrie wrote:
> You have another problem with utf8 in identifiers in that $é is not the
> same as $é. Unless something between my email client and your email
> client has normalised this message.

Such as the terminal program I copied this from.  (Grrrr!  It breaks
copying and pasting grep commands from one window to another.)

> This could make a difference if you
> try to import a sub from a package and the text in the package and
> importing script have different ideas of how the identifiers should be
> normalised. I would like to propose that identifiers added into the
> stash by Perl its self are done so in Normalization Form C this does not
> stop a programmer from directly manipulating the stash with such as
> ${"é::é"} but in this case they are supposed to know what they are doing.

But that is exactly how symbols are exported (assuming you mean *
rather than *).  Normalization for hash access (which is how we would
have to do this), even if it is limited to stashes, would be an effic-
iency nightmare.

P.S.: This e-mail is in utf-8 encoding, but lynx does not know how to
add an encoding header, so the text may appear scrambled.


Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About