Skip Menu |
Report information
Id: 1375
Status: resolved
Priority: 0/
Queue: perl5

Owner: Nobody
Requestors:
Cc:
AdminCc:

Operating System: (no value)
PatchStatus: (no value)
Severity: low
Type: docs
Perl Version: (no value)
Fixed In: (no value)



Download (untitled) / with headers
text/plain 135b
I hope that's not intended to apply to $x = 'beef'; "\U$x" But if not, you've got some rather kludgy semantics. Mike Guy
Download (untitled) / with headers
text/plain 1008b
M.J.T. Guy writes: Show quoted text
> Jarkko Hietaniemi <jhi@iki.fi> wrote
> > Do I remember correctly or was it so that we should make > > > > "\Ubeef" > > > > (and I think possibly also "\U+beef"?) to work as "\x{beef}"? In > > other words, convert /\\U\+?([0-9a-f]{4})/i into the corresponding > > Unicode (UTF-8) character. (For completeness, maybe also \U{hexhere} > > should work?)
> > I hope that's not intended to apply to > > $x = 'beef'; "\U$x"
Not this. Only for "literal hex" immediately following the \U because an "\U$x" is of course still meant to equal uc($x). Rationale: that's how Unicode characters are usually marked. Well, in Java they seem to use \ubeef. Show quoted text
> But if not, you've got some rather kludgy semantics.
If I could think of better search expressions I could try finding Larry's message on the subject... Show quoted text
> Mike Guy
-- $jhi++; # http://www.iki.fi/jhi/ # There is this special biologist word we use for 'stable'. # It is 'dead'. -- Jack Cohen
Download (untitled) / with headers
text/plain 474b
Do I remember correctly or was it so that we should make "\Ubeef" (and I think possibly also "\U+beef"?) to work as "\x{beef}"? In other words, convert /\\U\+?([0-9a-f]{4})/i into the corresponding Unicode (UTF-8) character. (For completeness, maybe also \U{hexhere} should work?) Now that's just a weird way to get BEEF. -- $jhi++; # http://www.iki.fi/jhi/ # There is this special biologist word we use for 'stable'. # It is 'dead'. -- Jack Cohen
Download (untitled) / with headers
text/plain 236b
Yes, I do recall decreeing something like that, but when I decree something and it doesn't happen, I usually attribute it to lack of round tuition rather than passive aggressive behavior. Whether or not that's the case... :-) Larry
Download (untitled) / with headers
text/plain 455b
I am glad it is not just me that thought that. When playing with this stuff that is the order I tried them in ;-) The last (working) one after greping the docs. Show quoted text
>In >other words, convert /\\U\+?([0-9a-f]{4})/i into the corresponding >Unicode (UTF-8) character. (For completeness, maybe also \U{hexhere} >should work?) > >Now that's just a weird way to get BEEF.
-- Nick Ing-Simmons <nik@tiuk.ti.com> Via, but not speaking for: Texas Instruments Ltd.
Download (untitled) / with headers
text/plain 855b
Larry Wall writes: Show quoted text
> jhi@iki.fi writes: > : Do I remember correctly or was it so that we should make > : > : "\Ubeef" > : > : (and I think possibly also "\U+beef"?) to work as "\x{beef}"? In > : other words, convert /\\U\+?([0-9a-f]{4})/i into the corresponding > : Unicode (UTF-8) character. (For completeness, maybe also \U{hexhere} > : should work?) > > Yes, I do recall decreeing something like that, but when I decree > something and it doesn't happen, I usually attribute it to lack of > round tuition rather than passive aggressive behavior. Whether or
Many things can be said of p5p but *passive* aggressive behaviour isn't one them... Show quoted text
> not that's the case... :-) > > Larry
-- $jhi++; # http://www.iki.fi/jhi/ # There is this special biologist word we use for 'stable'. # It is 'dead'. -- Jack Cohen


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

For issues related to this RT instance (aka "perlbug"), please contact perlbug-admin at perl.org