Re: Whitespace in \c[...], \x[...], etc.

2009-04-28 Thread Patrick R. Michaud
On Tue, Apr 28, 2009 at 03:08:05PM -0400, Mark J. Reed wrote: > On Tue, Apr 28, 2009 at 2:27 PM, Patrick R. Michaud > wrote: > > * The Unicode character name database [2] has parens in the > >  name property field for many characters > > > >    000A;;Cc;0;B;N;LINE FEED (LF) > > That's no

Re: Whitespace in \c[...], \x[...], etc.

2009-04-28 Thread Mark J. Reed
On Tue, Apr 28, 2009 at 2:27 PM, Patrick R. Michaud wrote: >> According to the 5.0.0 standard, section 4.8: >> >> "Unicode character names contain only uppercase Latin letters A >> through Z, digits, space, and hyphen-minus." >> >> So it seems the notes in parentheses are not considered part of th

Re: Whitespace in \c[...], \x[...], etc.

2009-04-28 Thread Patrick R. Michaud
On Tue, Apr 28, 2009 at 07:22:18AM -0700, Larry Wall wrote: > On Mon, Apr 27, 2009 at 11:04:03AM +0200, Helmut Wollmersdorfer wrote: > > Std.pm allows e.g. > > > > "\x[ 41 , 42 , 43 ]" > > > > For convenience - especially with long charnames - it should be possible > > to write > > > >

Re: Whitespace in \c[...], \x[...], etc.

2009-04-28 Thread Patrick R. Michaud
On Tue, Apr 28, 2009 at 01:28:40PM -0400, Mark J. Reed wrote: > On Tue, Apr 28, 2009 at 10:22 AM, Larry Wall wrote: > > Does anyone know offhand whether the Unicode Consortium has an explicit > > policy against use of punctuation in a charname?  So far they only > > seem to use hyphen and parens,

Re: Whitespace in \c[...], \x[...], etc.

2009-04-28 Thread Mark J. Reed
On Tue, Apr 28, 2009 at 10:22 AM, Larry Wall wrote: > Does anyone know offhand whether the Unicode Consortium has an explicit > policy against use of punctuation in a charname?  So far they only > seem to use hyphen and parens, but I wonder to what extent we can > depend on that... > According to

Re: Whitespace in \c[...], \x[...], etc.

2009-04-28 Thread Larry Wall
On Mon, Apr 27, 2009 at 11:04:03AM +0200, Helmut Wollmersdorfer wrote: > It's not explicitly specified, if insignificant whitespace is allowed in > \c[...], \x[...], etc. > > Std.pm allows e.g. > > "\x[ 41 , 42 , 43 ]" > > For convenience - especially with long charnames - it should be

r26542 - in docs/Perl6/Spec: . S32-setting-library

2009-04-28 Thread pugs-commits
Author: szabgab Date: 2009-04-28 18:26:17 +0200 (Tue, 28 Apr 2009) New Revision: 26542 Modified: docs/Perl6/Spec/S11-modules.pod docs/Perl6/Spec/S21-calling-foreign-code.pod docs/Perl6/Spec/S32-setting-library/IO.pod docs/Perl6/Spec/S32-setting-library/Str.pod Log: add some X<>-es to t

r26534 - docs/Perl6/Spec

2009-04-28 Thread pugs-commits
Author: jnthn Date: 2009-04-28 17:30:11 +0200 (Tue, 28 Apr 2009) New Revision: 26534 Modified: docs/Perl6/Spec/S04-control.pod Log: [spec] s/atan/atan2/ Modified: docs/Perl6/Spec/S04-control.pod === --- docs/Perl6/Spec/S04-control

Re: .to_charnames() and .from_charnames()

2009-04-28 Thread Larry Wall
On Mon, Apr 27, 2009 at 12:02:56PM +0200, Helmut Wollmersdorfer wrote: > [1] It would be possible to compose character names for the life-time of > the process, but these names would need to be checked for uniqueness > (performance problem). With our grapheme approach we will certainly compose

Re: Interpolation of "\c[$charname]"?

2009-04-28 Thread Larry Wall
On Mon, Apr 27, 2009 at 10:44:54AM +0200, Helmut Wollmersdorfer wrote: > It's not explicitly specified, if a something like > > my $charname = 'SPACE'; > my $string = "\c[$charname]"; > > should interpolate or not. > > I assume 'not'. Right? I also assume 'not', unless someone can present a