Front page | perl.perl5.porters |
Postings from January 2017
On 29 January 2017 at 22:06, Father Chrysostomos <sprout@cpan.org> wrote:
> Abigail wrote:
>> On Sun, Jan 29, 2017 at 08:14:39PM -0000, Father Chrysostomos wrote:
>> > It started warning in 5.14 or so, at which point I opposed the warn-
>> > ing. Ever since then I have simply suppressed it in my code, since I
>> > think it is wrong. Now it is a deprecation warning, and my code is
>> > very noisy.
>> >
>> > What do we gain by deprecating this behaviour that has been around
>> > since perl 4?
>> >
>> > This commit message for bfdc8cd3d5a is wrong to state that it was dep-
>> > recated in 5.14. It was not deprecated until bfdc8cd3d5a.
>>
>>
>>
>> It's listed as a deprecation in perl5140delta.pod.
>
> Non-ASCII characters are listed as deprecated in perl5140delta.pod,
> and specifically \c{ (so that we might introduce a \c{...} construct
> some time in the future), but other uses are (were) not. I see no
> benefit to deprecating \c` (which I use) and \c:.
Ok, so you use it. How hard is it to switch to \x{20}, or \040.
I mean sure, maybe you like it, but surely Perl has a enough ways to
inject a space into your code, or your regexes, that you can find an
alternative that you like almost as much.
And IMO, \c` is sufficiently unlikely you can fix your code to use
something else without too much trauma.
Yves
--
perl -Mre=debug -e "/just|another|perl|hacker/"
Thread Previous