in reply to Re^2: {Perl6} Macros and native compilation
in thread {Perl6} Macros and native compilation

Well, I don't want to discourage anyone from working on native code export if they have good reason to believe it's worthwhile. (This is not to be confused with the JIT, which is native code as an in-memory optimization.) But as far as I can tell, it isn't worthwhile. Some good use cases might change my mind, of course.

BTW, for those of you who want to create packaged binaries: I suggest that the best route will be to package the parrot executable along with your pbc.

    -- Chip Salzenberg, Free-Floating Agent of Chaos

  • Comment on Re^3: {Perl6} Macros and native compilation

Replies are listed 'Best First'.
Re^4: {Perl6} Macros and native compilation
by Limbic~Region (Chancellor) on Apr 11, 2005 at 14:45 UTC
    I will paraphrase and summarize our recent IRC conversation for the benefit of others.

    Limbic~Region: Parrot currently has a command line option for native executables which I believe already works on a couple of platforms. Are you saying that this functionality isn't integral or necessary for the project?
    chip: Not exactly. It is unlikely a native executable will work without linking against a substantial part of Parrot. It is not something I see as being necessary but I certainly don't want to discourage anyone else from working on something they feel is important.

    Please correct me if my paraphrasing is misrepresenting your position in any way. I see your point and concede that I have apparently been under the wrong impression for over a year now.

    Cheers - L~R

      That's about right. Some effort has already been made in the direction of native-binary creation -- make hello in the current parrot source tree actually builds a "hello world" program from Parrot assembler -- and whatever contributions others continue to make will certainly be accepted. (Modulo quality, of course.)

          -- Chip Salzenberg, Free-Floating Agent of Chaos