Skip Menu |
Report information
Id: 130419
Status: open
Priority: 0/
Queue: perl6

Owner: Nobody
Requestors: comdog <brian.d.foy [at] gmail.com>
Cc:
AdminCc:

Severity: (no value)
Tag: Todo
Platform: (no value)
Patch Status: (no value)
VM: (no value)



From: brian d foy <brian.d.foy [...] gmail.com>
To: rakudobug [...] perl.org
Date: Tue, 27 Dec 2016 14:31:49 -0800
Subject: |, ^, and & character class set operators aren't parseable
Download (untitled) / with headers
text/plain 858b
The |, ^, and & character class (and Unicode property) set operators aren't parseable: Show quoted text
> / <[abc] | [def]> /
===SORRY!=== Error while compiling: Unable to parse expression in metachar:sym<assert>; couldn't find final '>' ------> / <[abc]⏏ | [def]> / Show quoted text
> / <[abc] ^ [def]> /
===SORRY!=== Error while compiling: Unable to parse expression in metachar:sym<assert>; couldn't find final '>' ------> / <[abc]⏏ ^ [def]> / Show quoted text
> / <[abc] & [def]> /
===SORRY!=== Error while compiling: Unable to parse expression in metachar:sym<assert>; couldn't find final '>' ------> / <[abc]⏏ & [def]> / Show quoted text
> / <[abc] + [def]> /
/ <[abc] + [def]> / Show quoted text
> / <[abc] - [def]> /
/ <[abc] - [def]> / These are documented in https://docs.perl6.org/language/regexes but are not marked as "not implemented" or something similar.
RT-Send-CC: perl6-compiler [...] perl.org
Download (untitled) / with headers
text/plain 275b
On Tue, 27 Dec 2016 14:32:45 -0800, comdog wrote: Show quoted text
> These are documented in https://docs.perl6.org/language/regexes but > are > not marked as "not implemented" or something similar.
I doubt they'll be implemented particularly soon; I suggest they are removed from the docs.
RT-Send-CC: perl6-compiler [...] perl.org
Download (untitled) / with headers
text/plain 472b
On Fri, 30 Dec 2016 13:36:03 -0800, jnthn@jnthn.net wrote: Show quoted text
> On Tue, 27 Dec 2016 14:32:45 -0800, comdog wrote:
> > These are documented in https://docs.perl6.org/language/regexes but > > are > > not marked as "not implemented" or something similar.
> > I doubt they'll be implemented particularly soon; I suggest they are > removed from the docs.
Opened a docs ticket to cover it. https://github.com/perl6/doc/issues/1093 Rejecting this ticket. -- Will "Coke" Coleda
Download (untitled) / with headers
text/plain 276b
I notice that in many other places in the docs there are "NYI" annotations. Perhaps that would be appropriate here. I figure that this ticket would need to come back to satisfy the UTS #18 (http://www.unicode.org/reports/tr18/tr18-19.html) support. Perhaps mark it as stalled?
Download (untitled) / with headers
text/plain 276b
I notice that in many other places in the docs there are "NYI" annotations. Perhaps that would be appropriate here. I figure that this ticket would need to come back to satisfy the UTS #18 (http://www.unicode.org/reports/tr18/tr18-19.html) support. Perhaps mark it as stalled?
From: brian d foy <brian.d.foy [...] gmail.com>
Date: Sat, 31 Dec 2016 01:55:40 -0500
To: perl6-bugs-followup [...] perl.org
Subject: Re: [perl #130419] |, ^, and & character class set operators aren't parseable
Download (untitled) / with headers
text/plain 264b
If these are intended to be future features (and for Unicode compliance I think they are), maybe mark it as stalled instead. I tend to think of rejected tickets as not valid or wrong, which this one isn't. It's still something that needs to happen in the future.
I've raised this question too ( https://irclog.perlgeek.de/perl6/2016-12-31#i_13827103 ), but according to Coke:
“no. there's no intent to implement it.”

Perhaps someone can doublecheck, but looks like there's no reason to keep this open.

On 2017-01-02 13:27:48, comdog wrote:
Show quoted text
> If these are intended to be future features (and for Unicode
> compliance I think they are), maybe mark it as stalled instead. I tend
> to think of rejected tickets as not valid or wrong, which this one
> isn't. It's still something that needs to happen in the future.
>


Subject: Re: [perl #130419] |, ^, and & character class set operators aren't parseable
Date: Mon, 2 Jan 2017 16:50:21 -0500
To: perl6-bugs-followup [...] perl.org
From: brian d foy <brian.d.foy [...] gmail.com>
Download (untitled) / with headers
text/plain 122b
If it's going to be rejected, a note about why Perl 6 will not have full, basic Unicode support (Level 1) would be nice.
On 2017-01-02 13:51:27, comdog wrote:
Show quoted text
> If it's going to be rejected, a note about why Perl 6 will not have
> full, basic Unicode support (Level 1) would be nice.
>


I'm not sure I understand the issue here…
It does support properties, and you can already use + and - (and | was supposed to be an equivalent to + I think, so just use + instead).

So if you want something like <:Ll + :N>, then it already works. Now, the only question is how would you do intersections, in which case you can use something like this:

say ‘pyõrl6’ ~~ m/[<:Ll> & <:Block(‘Basic Latin’)>]+/ # OUTPUT«「py」»


I don't mind & being added, as much as I don't mind it being rejected. But I don't really see the point about basic unicode support (or the lack of thereof). Perhaps you can clarify?
RT-Send-CC: perl6-compiler [...] perl.org
Download (untitled) / with headers
text/plain 1.6k
On Mon, 02 Jan 2017 14:15:45 -0800, alex.jakimenko@gmail.com wrote: Show quoted text
> On 2017-01-02 13:51:27, comdog wrote:
> > If it's going to be rejected, a note about why Perl 6 will not have > > full, basic Unicode support (Level 1) would be nice. > >
> > > I'm not sure I understand the issue here… > It does support properties, and you can already use + and - (and | was > supposed > to be an equivalent to + I think, so just use + instead). > > So if you want something like <:Ll + :N>, then it already works. Now, > the only > question is how would you do intersections, in which case you can use > something > like this: > > say ‘pyõrl6’ ~~ m/[<:Ll> & <:Block(‘Basic Latin’)>]+/ # OUTPUT«「py」» > > > I don't mind & being added, as much as I don't mind it being rejected. > But I > don't really see the point about basic unicode support (or the lack of > thereof). Perhaps you can clarify?
To be clear, my "doubt they'll be implemented soon" wasn't an indication they shouldn't be, just that it's better that the docs cover things that actually exist. If somebody popped up with a patch to implement them tomorrow, that'd be just great. But, as mentioned by Alex, there is already a way to do it, and at the moment most folks are more focused on making the many features we already have robust and fast rather than adding more features. Thus my uncertainty whether it'll top anybody's todo list especially soon. Of course, now I've written this somebody will probably be like "hah, challenge accepted!" :-) I'll re-title this ticket to be an NYI for the features; it's right that we have a ticket to track that it wants doing at some point. /jnthn
Also:

“I notice that in many other places in the docs there are "NYI" annotations.”

Please file doc tickets for these. Most of the time we don't want to doc NYI stuff.

On 2016-12-30 23:24:46, comdog wrote:
Show quoted text
> I notice that in many other places in the docs there are "NYI"
> annotations. Perhaps that would be appropriate here. I figure that
> this ticket would need to come back to satisfy the UTS #18
> (http://www.unicode.org/reports/tr18/tr18-19.html) support. Perhaps
> mark it as stalled?




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