Downloaded 86 times
![(Domain Specific Language, not Direct Server Link) [email_address] DSL explained](https://image.slidesharecdn.com/dsl-091108083729-phpapp02/85/DSL-explained-_-1-320.jpg)
![(Domain Specific Language, not Direct Server Link) [email_address] DSL explained](https://image.slidesharecdn.com/dsl-091108083729-phpapp02/75/DSL-explained-_-1-2048.jpg)
Uploaded byDmitry Kandalov
DSL explained _
The document provides an overview of domain-specific languages (DSLs), which are tailored for particular domains while maintaining a human-readable nature. It discusses the types of DSLs, including internal and external DSLs, as well as their applications and examples such as regular expressions and SQL. Additionally, it touches on the use of language workbenches and the process of parsing DSL scripts.
More Related Content
DSL explained _
- 1. (Domain Specific Language,not Direct Server Link) [email_address] DSL explained
- 2.
- 3. and only thenfor computers Code is written for people
- 4. Objects ---> VocabularyGrammar ---> Language Domain Driven Design DSL
- 5. DSL is advancedstuff
- 6. DSL example (byMartin Fowler)
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 14.
- 15. DSL is acomputer language with: human language nature limited expressiveness domain focus
- 16. DSL types internalexternal language workbench
- 17.
- 18.
- 19.
- 20.
- 21.
- 22.
- 23.
- 24.
- 25. regular expressions CSSSQL all XML Unix config files Ruby on Rails mocking frameworks wiki syntax / markdown LINQ
- 26. Using internal DSL(aka Fluent Interface)
- 27. Easy to do...no parsers, etc. Full IDE support Good Bad Limited by host language
- 28.
- 29.
- 30.
- 31.
- 32.
- 33. Method chaining Objectscoping Expression Builder
- 34.
- 35. Unlimited expressiveness Youchoose execution environment Good Bad Requires “more” work No IDE support
- 36. DSL script parseAST Semantic model optional
- 37. You can parseDSL manually (regexp, Tokenizer) using some tool (ANTLR, yacc, ...)
- 38.
- 39. Using LanguageWorkbenches
- 40. Meta Programming SystemMicrosoft Oslo Intentional Domain Workbench Eclipse Modeling Project
- 41.
- 42.
- 43. AST (DSL script)concepts (language) edit describe you
- 44. AST (DSL script)concepts (language) edit edit describe “ user” you
- 45. AST (DSL script)concepts (language) edit describe “ user” you no text, just AST ! edit
- 46. useful stuff (likejava code) AST (DSL script) concepts (language) edit describe transformed “ user” you edit
- 47.
- 48.
- 49. Module Project SolutionLanguage Generator DevKit kind of
- 50. Model Module ProjectSolution Language Generator DevKit kind of
- 51. Node Model ModuleProject Solution Language Generator DevKit kind of includes Concept defined by
- 52.
- 53.
- 54.
- 55.
- 56.
- 57.
- 58.
- 59.
- 60.
- 61.
- 62.
- 63.
- 64.
- 65.
- 66.
- 67.
- 68.
- 69.
Editor's Notes
- #2 Hi For those who haven't heard about it, SOLID is acronym composed from principles names. (There are 5 of them.) SOLID doesn't have any particular meaning. It's just a good way to remember list of principles. These principles are about low-level design and partly interpretation of OOP basics.
- #4 Before doing anything it's good to know “why” you're going to do it. In other words operating without context you're becoming coding monkey or a screwdriver.
- #40 I began programming at school because it was fun (before anyone actually taught me). Turbo Pascal, asm for DOS (for cool things). Then Delphi, C++. Of course we were told at school that OOP not only “Организация Освобождения Палестины”(Palestine Liberation Organization, in Russian sounds like OOP) but also encapsulation, polymorphism, inheritance © Nice words which I've known for quite a long time. What I did at the time was kind of “goal-oriented programming” . You don't really care how the work is done (almost), it's works today – fine! I knew some techniques like using inheritance but never bothered to understand why they exist. After (four?) years I got tired of “fighting the mess” and vision of programming as “low-level activity” so I programmed only for some “code for labs”. Some time later for some reason I though it would be nice to make sense of objects anyway. That way I came across patterns, UML, java, junit, refactoring and OOP (this time for real) . Nice java IDEs were also very attractive, but not more than the following “promises”.