develooper Front page | perl.perl5.porters | Postings from July 2013

Re: [perl #116296] [PATCH] remove PL_patchlevel from and optimizeS_minus_v

Thread Previous
From:
Karl Williamson
Date:
July 7, 2013 05:00
Subject:
Re: [perl #116296] [PATCH] remove PL_patchlevel from and optimizeS_minus_v
Message ID:
51D8F5C7.50008@khwilliamson.com
On 07/06/2013 10:10 AM, bulk88 via RT wrote:
>> >I really don't like this part. Its just an excessive level of
>> >micro-optimisation for code that's only called once at most, and will
>> >have
>> >a negligible effect on the overall binary size.
> ................
>> >The downside is that the src code becomes more bloated and confusing.
> And this is why people give up, switch languages, then tell all their
> friends Perl [5 or Perl world] is dead. If the git repo is locked, code
> will never become more confusing. The assumption that progress is for
> communists and hippies is the death of Perl 5.

I agree with Dave, and I believe it is counterproductive to write code 
based on how current particular hardware works, when that code will long 
outlive the hardware and likely the whole underlying mechanism.

But suppose we are wrong; suppose it has to be implemented the way you 
did.  It's not at all obvious that it has to be that way.  Therefore 
there should be comments in the code as to your reasoning.  If not, the 
next guy might come along and not realize that this implementation has 
to be this particular way, and change it out.  If indeed it is required 
to be this way, that might introduce subtle failures that the 
accompanying tests don't catch.  It's unfair to those who follow to not 
comment such subtleties.

Thread Previous


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About