Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?

Re: Re: Re: Re: perl2exe - no more secrets

by Anonymous Monk
on Feb 26, 2003 at 12:51 UTC ( #238754=note: print w/replies, xml ) Need Help??

in reply to Re: Re: Re: perl2exe - no more secrets
in thread perl2exe - no more secrets

Yeah, I read that one a while back and I completely disagree with it. It sounds kind of like this to me:

the Perl vm is pretty good for a vm and it might take a little effort to write a better compiler, so perl's perfect again, so yeah, move along. what do you mean that doesn't make any sense? well, you obviously don't know what you're talking about. See this function? it's fast in perl. If I poorly write a c-equivalent, it's slow. So why don't I write it well? because perl is good. Perl rox0rs.

The end.

It's very possibly to write a native compiler for Perl that would produce faster, more efficient code. Nobody seems to want to do it though, probably because they don't want to deal with the negative response from the community. So instead they focus on the next-gen scripting languages.

  • Comment on Re: Re: Re: Re: perl2exe - no more secrets

Replies are listed 'Best First'.
Re: perl2exe - no more secrets
by Abigail-II (Bishop) on Feb 26, 2003 at 12:56 UTC
    Big words, no evidence. If it's so very possible to write a native compiler that produces faster, more efficient code, what's keeping you from writing it?

    When you have finished your compiler, come back and show us to be wrong. Otherwise, just shut up.


      what's keeping you from writing it?

      Perl's a nice language, much more practical than it appears at first, but it's not the only language out there. There is substantial room for improvement (even over what I've seen of Perl 6). Writing a compiler involves a substantially amount of work and I'm careful what I invest my time in. If I were to start such a project I doubt it would end up as a perl native compiler. It may have many similiarities, but it wouldn't be Perl.

      When you have finished your compiler, come back and show us to be wrong. Otherwise, just shut up.

      Fair enough. I'll pick one of the two :)

      As for the original post, the parody was meant as a joke and not as disrespectful to anyone. I haven't yet tried to write a perl native compiler, but I see no theoretical reason why one couldn't produce faster, more efficient code.

      Oops, didn't shut up, guess I have to write the compiler now ;).

        perl is already written in C, and its has been optimized for years. I see no theoretical reasons why a native compiler produces a faster split function than perl already has. Or faster hashes. Or faster whatever.

        Compiling to "native code" isn't going to run your Perl code faster. Unless you are going to sacrifice the flexibility Perl gives you. But then, it's no longer a Perl compiler.


Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://238754]
[haukex]: Corion: Yes exactly, in the author tests I don't worry about portability as much, I also don't list the author tests' dependencies in Makefile.PL
[haukex]: I figure someone who wants to contribute will know how to install the missing modules ;-) Not the nicest way to go but I don't think many people are using my modules yet
[ambrus]: Corion: some of these stupid syntax highlighters assume that too. just look at the table in http://perldoc. functions/pack. html for example.
[haukex]: ..."yet" ;-) I haven't had to deal with Dist::Zilla yet but I've heard about how it's a big setup
[ambrus]: I really don't like automagic stuff. I'm happy when computers do exactly what I tell them, even if that means they sometimes do the wrong thing.

How do I use this? | Other CB clients
Other Users?
Others surveying the Monastery: (14)
As of 2017-02-27 12:41 GMT
Find Nodes?
    Voting Booth?
    Before electricity was invented, what was the Electric Eel called?

    Results (385 votes). Check out past polls.