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

JS is nowadays not only the most widespread language...

... because of its minimality one should think of it as a VM with incredible efficient JIT performance.

Now think of benchmarks where a "python2js" conversion runs 10 times faster than a "perl2js" because you can't use ++ but you need a method inc(), which has to handle a special case which is only known to a little minority of people ...

Wouldn't you love to have a pragma telling the compiler: No Sir, I don't need that magic here! ?

Cheers Rolf

UPDATE: added quotes.

Replies are listed 'Best First'.
Re^5: getting rid of special features
by tobyink (Canon) on Feb 19, 2013 at 09:52 UTC

    "Wouldn't you love to have a pragma telling the compiler: No Sir, I don't need that magic here! ?

    ... or just run perl2js --opt assume_increment_is_numeric=1

    package Cow { use Moo; has name => (is => 'lazy', default => sub { 'Mooington' }) } say Cow->new->name
[reply]
[d/l]
      For the records I didn't mean any specific "perl2js" or "python2js" implementation.

      > ... or just run perl2js --opt assume_increment_is_numeric=1

      ATM his is the only mode that perlito knows!

      But if you need to be sure that the Perl¹ side does the same thing, you will end up in overloading ++, hence considerably slowing down the Perl side.

      Cheers Rolf

      ¹) is there any name for the standard interpreter/compiler? "CPerl" maybe? ;)

[reply]
[d/l]
Re^5: getting rid of special features
by Anonymous Monk on Feb 19, 2013 at 09:26 UTC
    What are you talking about, got link?
[reply]

In Section Meditations