From @bbkr

This code​:
"" ~~ /m ** 1..-1 /

Gives following message​:
"Only integers or '*' allowed as range quantifier endpoint"

I think that error message should say "positive integers" or "unsigned
integers" because -1 IS also an integer.

I don't know what STD says about it, because eval on IRC seems to be currently
down

From @bbkr

[18​:35] <TimToady> std​: say "" ~~ /m ** 1..-1 /
[18​:35] <p6eval> std 32088​:
OUTPUT«�[31m===�[0mSORRY!�[31m===�[0m�Malformed range at /tmp/NlvQf0HNFI
line 1​:â�¤------> �[32msay "" ~~ /m ** 1..�[33mâ���[31m-1 /�[0mâ�¤
expecting quantifierâ�¤Parse failedâ�¤FAILED 00​:01 119mâ�¤Â»

The RT System itself - Status changed from 'new' to 'open'

From @coke

On Mon Aug 23 09​:32​:08 2010, pawel.pabian@​implix.com wrote​:

This code​:
"" ~~ /m ** 1..-1 /

Gives following message​:
"Only integers or '*' allowed as range quantifier endpoint"

I think that error message should say "positive integers" or "unsigned
integers" because -1 IS also an integer.

I don't know what STD says about it, because eval on IRC seems to be
currently
down

01​:40 <[Coke]> r​: "" ~~ /m ** 1..-1 /
01​:40 <camelia> rakudo bfd850​: OUTPUT«===SORRY!===â�¤Negative numbers are not
  allowed as range quantifier endpointâ�¤at
  /tmp/QI9W2dDDrG​:1â�¤------> "" ~~ /m ** 1..-1â�� /â�¤Â»
01​:41 <[Coke]> std​: "" ~~ /m ** 1..-1 /
01​:41 <camelia> std b33d8e0​: OUTPUT«===SORRY!===â�¤Malformed range at
  /tmp/bftAQl82Sb line 1​:â�¤------> "" ~~ /m ** 1..â��-1 /â�¤
  expecting quantifierâ�¤Parse failedâ�¤FAILED 00​:01 43mâ�¤Â»

I'd say this meets the criteria of the original bug report. Closable with tests, I think.

--
Will "Coke" Coleda

From @peschwa

Am Fr 10. Mai 2013, 22​:42​:09, coke schrieb​:

On Mon Aug 23 09​:32​:08 2010, pawel.pabian@​implix.com wrote​:

This code​:
"" ~~ /m ** 1..-1 /

Gives following message​:
"Only integers or '*' allowed as range quantifier endpoint"

I think that error message should say "positive integers" or
"unsigned
integers" because -1 IS also an integer.

I don't know what STD says about it, because eval on IRC seems to be
currently
down

01​:40 <[Coke]> r​: "" ~~ /m ** 1..-1 /
01​:40 <camelia> rakudo bfd850​: OUTPUT«===SORRY!===â�¤Negative numbers
are not
allowed as range quantifier endpoint�at
/tmp/QI9W2dDDrG​:1â�¤------> "" ~~ /m ** 1..-1â�� /â�¤Â»
01​:41 <[Coke]> std​: "" ~~ /m ** 1..-1 /
01​:41 <camelia> std b33d8e0​: OUTPUT«===SORRY!===â�¤Malformed range at
/tmp/bftAQl82Sb line 1​:â�¤------> "" ~~ /m ** 1..â��-1 /â�¤
expecting quantifierâ�¤Parse failedâ�¤FAILED 00​:01 43mâ�¤Â»

I'd say this meets the criteria of the original bug report. Closable
with tests, I think.

A typed exception has been added (X​::Syntax​::Regex​::MalformedRange) and is tested for in roast with commit ca327a9c.

From @usev6

Since the test in S32-exceptions/misc.t passes on all backends, I'm closing this ticket.

@usev6 - Status changed from 'open' to 'resolved'