Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

I like being able to create domain specific languages - so I think decent macros are a great idea. It's something I miss in Perl5.

In general I think that Perl6 is doing the right thing by building the infrastructure that allows language features to be added (pre/post handlers, macros, etc.) rather than adding everything into the core language.

Macros and operator overloading seem to be things that start religous wars on the language front. Personally I am in the camp that says both things can make code simpler and therefore easier to understand for everybody, smart or otherwise.

I've never seen any studies that show that these features cause comprehensibility problems, just lots of anecdotes and straw man examples. My personal experience has been the opposite.

Yes, these features can be misused. A poorly designed set of macros can make it hard to understand what a program is doing, but you can get the same sort of problems from a poorly designed API.

I don't agree with the whole LFSP/LFM divide. In my experience language adoption by the "masses" is driven by a large number of different factors - many of them having nothing to do with the features of the languages involved.

Trying to justify why certain languages are popular/niche by only looking at the language features can be an exercise in futility.

In reply to Re: Macros, LFSPs and LFMs by adrianh
in thread Macros, LFSPs and LFMs by stefp

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

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others surveying the Monastery: (6)
As of 2022-05-19 07:48 GMT
Find Nodes?
    Voting Booth?
    Do you prefer to work remotely?

    Results (71 votes). Check out past polls.