Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid
 
PerlMonks  

Re^4: getting rid of special features

by LanX (Canon)
on Feb 17, 2013 at 19:58 UTC ( #1019202=note: print w/ replies, xml ) Need Help??


in reply to Re^3: getting rid of special features
in thread getting rid of costly special features

My point is the huffman-coding principle.

Incrementing numeric indices happens maybe 1_000 or even 1_000_000 times more often than incrementing strings. So for integers this operator has to be short.

But the effort to learn and maintain string_increment with a core operator like ++ is far less economic.

For that reason I agree that strinc() (or whatever notation suits the most) would pollute the namespace like in PHP, so it should be outsourced to a pragma or module.

The inverse approach would be the 'no feature qwinc' I proposed, forcing ++ to croak on strings and allowing full backwards compatibility.

Furthermore allowing optimizations within Perl and less headaches and far more performance when translating to other VMs.

Cheers Rolf


Comment on Re^4: getting rid of special features
Download Code
Replies are listed 'Best First'.
Re^5: getting rid of special features
by Anonymous Monk on Feb 17, 2013 at 23:37 UTC

    Furthermore allowing optimizations within Perl and less headaches and far more performance when translating to other VMs.

    Sure, we all like pipe dreams :)

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1019202]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others taking refuge in the Monastery: (13)
As of 2015-07-30 12:17 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    The top three priorities of my open tasks are (in descending order of likelihood to be worked on) ...









    Results (271 votes), past polls