Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • Martin Fowler has a nice article [] where he uses the terms Internal and External DSLs to describe the difference between DSLs implemented within a language and those implemented in a separate language that is then parsed.

    As somebody who played a great deal with Lisp I have a fondness for the whole code-as-data paradigm that leads to internal DSLs.

    (Aside - feeling generally annoyed off with this utterly f**king pointless Ruby/Perl pissing match. We're turning into the Lisp community. Look how well they did

    • Aside - feeling generally annoyed off with this utterly f**king pointless Ruby/Perl pissing match.

      Who made it Perl versus Ruby?

      It just so happens that a portion of the Ruby community (probably mostly Rails fans) seems to get very excited every time one of them creates an API and jumps up and down yelling "I MADED A DEE ESS ELL!!! WHOOPAH! YUOU CANNOT DO THIS IN UR LANGAGES HEEHEH FOOLZORZ!" That could happen in any language where a silly idea propagated rapidly.

      Meanwhile, I as a polyglot programmer look at that and say "Looks like an API I could have written in a any of half-dozen languages in a couple of hours. What makes it a DSL?" and can't get a straight answer. (Seriously, the defining feature of a DSL is that it's valid code you have to eval()?) If there's something to this DSL thing, programmers in general ought to be able to talk about it in ways that make sense!

      The most honest answer I could expect to get it "I don't know, but everyone else seems to be writing valid Ruby in ways that exploit features of the parser, so I just did what they did. I don't really know what that term means either."