in reply to getting rid of costly special features

Does anyone really use features like ...

This is exactly the kind of introspective navel gazing that I think does Perl harm.

If the magical string increment was removed from perl, no one would notice any performance difference at all in their production code.

(Except those of use that do use it, and would have to re-implement it ourselves in Perl.)

And as for it being a barrier to porting to JavaScript VMs. Its not that complicated an algorithm.

But mostly, there are just so many more important issues that could occupy our time.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
  • Comment on Re: getting rid of costly special features

Replies are listed 'Best First'.
Re^2: getting rid of costly special features
by LanX (Saint) on Feb 18, 2013 at 10:12 UTC
    > And as for it being a barrier to porting to JavaScript VMs. Its not that complicated an algorithm.

    Not complicated but very slow.

    It considerably slows down any numeric increment, which are >99% of the use cases.

    > magical string increment was removed from perl,

    I didn't say that, I just want a switch to turn it off.

    Cheers Rolf

[reply]
      Not complicated but very slow. It considerably slows down any numeric increment

      Care to back that assertion up with some evidence?

      With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
        > Care to back that assertion up with some evidence?

        Strings are immutable in JS, now how would you implement a postincrement?

        Instead of i++ of a primitive value i, you need to use objects for all scalars with methods like i.postInc() and i.preInc() and i.getValue()

        Cheers Rolf

[reply]
[d/l]
[select]

In Section Meditations