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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • To start I am not a fan of the modeling gang like Martin Fowler and his buddies of the agile manifesto, I believe they ruined the topic (software modeling) for generations to come, they took something smart and turn it into something dumb and silly, and not smart at all!

    But I have to say, every now and them being the veterans that they are, something smart comes out of them.

    I believe that the IT literature, writing or whatever suffer from ill defined definitions.

    For example, surf the net for definition of thing like BI, Data Mining and Transaction Management System. Whatever definition you will find, it be far from the actual product.

    DSL, is kinda, one of these term, that people tend to over complicate, which doesn't help outsiders (Business people), or insiders (IT people) who are new to the concept.

    I do like Martin's DSL categories, they are simple, clear, straightfoward and useful.

    I will paraphrase what you said he said to clarify why I think they are useful.

    You have two kind of Perl DSL. Internal, and External.

    Internal DSL, is Perl Code a library, with an interface that clear, simple and intuitive, to the extent that none Perl coders, can correctly guess what the code, without prior Perl experience and with very little (and preferably without) training.

    External DSL, is a new language, specially crafted to solve a specific type of programs. Like regular expression.

    And to elaborate furthur, and explain why DSL good not just of Business people, is not just about syntax, DSL is about providing delcative solution vs. procedural ones.

    Using an Internal or External DSL, should shield you from reverting to tradional program languages constructs like Loops and Conditionl branches. You should be able to only use the DSL code to solve the Domain Issue by coding what you want done and without having to use loops or conditional branches and by doing so reverting to a procedural style.

    Moose does exactly this, I declare clases using Moose provided syntax, I don't use previous, older or traditional Perl OOP idiom. And this makes Moose code shorter, clearer and more intuitive, I don't read algorithims when I read Moose code (the code used to create classes and types), which is specifically what in my opinion make Moose worth using.

    One thing I dont know, is, if Moose is Internal or External DSL, and according to most of the Moose tutorial I read, I should not care.

    Moose is probably a hybrid DSL, as it introduce new Keywords (or so they say) and other than that its Perl code.

    I ultimatly find the DSL categories introduces by Martin useful, they allow peole to answer simple and common asked questions. Like is this syntax Perl Code or an External DSL. The differentiation can help developer at different better read, learn and teach the code. Better communicate using smart, clear well defined term that may have the effect or reducing the complexity of a complex concept

    I hope i was clear, and not to long, and that my message got through, and was perceived as smart.