[33016] in Perl-Users-Digest
Perl-Users Digest, Issue: 4292 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Thu Oct 2 03:09:15 2014
Date: Thu, 2 Oct 2014 00:09:02 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Thu, 2 Oct 2014 Volume: 11 Number: 4292
Today's topics:
Re: clever equal still experimental after so much time <lionslair@consolidated.net>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Wed, 01 Oct 2014 21:42:42 -0500
From: Martin Eastburn <lionslair@consolidated.net>
Subject: Re: clever equal still experimental after so much time
Message-Id: <2Z2Xv.148824$_r4.12173@fx25.iad>
On 10/1/2014 7:17 AM, Rainer Weikusat wrote:
> Justin C <justin.1401@purestblue.com> writes:
>> On 2014-09-29, George Mpouras <gravitalsun@hotmail.foo> wrote:
>>> use strict;
>>> use warnings;
>>> my %hash = qw/k1 1 k2 0 k3 1/;
>>>
>>> print %hash ~~ sub{$hash{$_[0]}} ? 'all true' : 'nope'
>>
>> Smartmatch is experimental.
>>
>> "If something in the Perl core is marked as experimental, we may
>> change its behaviour, deprecate or remove it without notice. While
>> we'll always do our best to smooth the transition path for users of
>> experimental features, you should contact the perl5-porters
>> mailinglist if you find an experimental feature useful and want to
>> help shape its future."
>
> That's an invitation for users of experimental features to consider
> participiating in their future development.
>
>> In other words, don't use it because it might do something
>> different next week. If you can cope with that, go ahead but
>> you'd be a fool to put it in production code just yet.
>
> And that's a non-sequitur: Some future (or already released but
> 'relatively future') Perl version may "change the behaviour of the
> feature or remove it". Consequently, such a Perl version possibly can't
> be used for known-be-working production code, at least not without
> either changing the former or the latter.
>
It is a kin to using an op-code in a processor that is not working right
in a program and get your results. Then another gets the same program
and the results differ.
I had an 8080 that way and after working with it with my dad (distant) I
decided to write around it.
I later got a new CPU in a new mainframe and my programs worked because
I did.
If a list of experimentals were published then the core workers might
get feedback as to want and need. And all would know.
Martin
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
Back issues are available via anonymous ftp from
ftp://cil-www.oce.orst.edu/pub/perl/old-digests.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V11 Issue 4292
***************************************
