Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Justifications for code generation 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • When you consider that a "compiler" is just a "code generator" for machine language, all the same rules apply.

    When we first got compilers, people complained that they couldn't debug, because the debuggers showed only the translated version. And there were times when the compilers generated sub-optimal code, and there was no way to tune or fix the output without breaking the paradigm.

    But now, high-level languages are commonplace. High-level debuggers are commonplace. The resulting machine code is optimized and trusted.

    For a good meta-code generator, you'll need to get to the point where you have good debugging hooks, trusted code, and optimal code. Prior to that, it'll be a maintenance nightmare. {grin}

    --
    • Randal L. Schwartz
    • Stonehenge

    • When you consider that a "compiler" is just a "code generator" for machine language, all the same rules apply.

      When we first got compilers, people complained that they couldn't debug, because the debuggers showed only the translated version. And there were times when the compilers generated sub-optimal code, and there was no way to tune or fix the output without breaking the paradigm.

      I don't think it's the same thing here. In an abstract sense, it is all about the maturity of the tools. But in a pra

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.