Re: qr//xx in 5.26?

On 01/05/2017 11:20 PM, Karl Williamson wrote:
> We never have really discussed what happens when we deprecate
> something in order to use the construct for something else.

I don't see why it needs to be any different than a regular deprecation
cycle.

>
> After 2 deprecation cycles can we just re-use it?  Or do we need 1 or
> 2 additional cycles where its attempted use generates a syntax error?

What makes sense to me is two versions of deprecation warnings, and the
next version allows re-purposing.

>
> In particular, qr//xx has generated an error since 5.25.1.  There have
> been no reports of problems as a result.
>
> Is it ok to give /xx its new meaning in 5.26? or should it generate an
> error for 5.26, and we defer changing it until 5.27?

I think it's fortunate this did not raise any issues, but I'm not sure
why this means it doesn't need two release cycles of deprecation. I
admit this particular one is different in the sense that this is
something that until now was just not used. You couldn't do anything
with /xx before, so we're not deprecating an existing feature, just
tightening up when we find it. That might be different enough to not
fall under the policy. What do you think?

>
> And there needs to be some policy in general for this situation.  For
> example, the decision might be different for the unescaped left brace
> deprecation, which has caused lots of problems in 5.25.

True.

• qr//xx in 5.26? by Karl Williamson
• Re: qr//xx in 5.26? by Sawyer X
• Re: qr//xx in 5.26? by Karl Williamson
• Re: qr//xx in 5.26? by Sawyer X