That's like carriage vs rocket.

The preprocessor struggles to parse the code.

The only thing you can statically parse in Perl is POD.°

But the lisp macro gets the code (or rather AST) for free. No confusion where it begins or ends and about the elements in between.

When OOP became popular, various lisp dialects just added some macros for implemention. Backwards compatibility included.

Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery

°) well as POD, you can't make it to code. Mind you:

POD inside a here doc is both string code and extractable comment.

In reply to Re^6: Amicable divorce by LanX
in thread Amicable divorce by ribasushi

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.