develooper Front page | perl.perl5.porters | Postings from May 2016

Re: [perl #128241] Deprecate /$empty_string/

Thread Previous | Thread Next
May 27, 2016 08:43
Re: [perl #128241] Deprecate /$empty_string/
Message ID:
Aristotle Pagaltzis writes:

> Personally:
> • I agree /$empty/ should be deprecated.
> • I oppose changing its behaviour without a deprecation cycle.

“Warning: We've found a bug in your code. Please fix it now, otherwise a
future version of Perl will automatically fix it for you.”

>   At that point, the special case is so well circumscribed that I see
>   no real gain in excising [use of literal //] entirely, however
>   ancient-Unix-warty it may be.

Would it have advantages for users of the identically spelt //
defined-or operator? Specifically, are there circumstances where
somebody who makes a mistake while trying to use defined-or could get an
error message but at the moment gets mysterious repeat-match behaviour?
Or does get an error message, but a suboptimal one?


Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About