Building DSLs: Marriage of High Essence and Groovy Metaprogramming
15 likes1,064 views
The document discusses domain specific languages (DSLs) and how to build them. It covers key topics like the differences between external and internal DSLs, characteristics of DSLs like being context-driven and having fluent interfaces, and techniques for creating DSLs in Groovy like using categories and ExpandoMetaClass. Examples of DSLs in different languages and frameworks are provided. References for further reading on DSLs are listed at the end.
Building DSLs: Marriage of High Essence and Groovy Metaprogramming
- 1. Building DSLs High Essence Groovy MetaProgramming Venkat Subramaniam venkats@AgileDeveloper.com
- 2. Communication How do we humans communicate? 2
- 3. First Moon Landing Transcript... Two things go through my mind: 1. Wow 2. I’ve the faintest idea what they’re talking about! 3
- 4. Communication As human we communicate using Jargons 4
- 5. Aren’t Jargons Bad? They’re very bad for people who don’t understand the domain or don’t share the context You’d be totally lost But, they’re very good for people who share the context in the domain The communication is highly effective Terse, high signal—to—noise ratio This is what professionals use in their respective fields 5
- 6. How do you use your App/ Computer? Typically you use keyword input files, configuration files, etc. If you’re stuck at an airport, which of these two agents gives you the most confidence you’ll be on your way—one that uses the keyboard, or the one that mouses around? The former, uses direct queries 6
- 7. Productivity is Key A GUI makes an average user productive, but often may slowdown an expert user or a user very fluent with your application and its domain. You don't want to make the novice productive at the expense of making an expert counterproductive. 7
- 8. Naked Objects Richard Pawson and Robert Matthews introduced the concept of Naked Objects They auto-build a thin object-oriented user interface (OOUI) from a domain model The OOUI exposes the behavior of domain objects for direct interaction by the users. 8
- 9. How does an expert express Matrix Multiplication? 9
- 10. Goal of a DSL The goal of DSLs is to provide a highly effective interface for your users to interact with your application. The interface may be graphical or textual. 10
- 11. But?! what’s a DSL? 11
- 12. Domain Specific Language A language targeted at a particular type of problem Syntax focuses on intended domain/problem Unlike a general purpose language, you can’t use it for all kinds of stuff (or don’t want to) Limited in scope and capability Hence, they’re small and simple—that’s good 12
- 13. Domain and Context What’s Domain? It is an area of sphere or knowledge, influence, or activity What’s Context? A logical framework within which we evolve models What’s Bounded Context? Context Defines a logical boundary of relevance within the context Domain 13
- 14. What is it really? It’s a ubiquitous language—only narrow within a domain Domain folks understand it well Highly expressive and easy to use 14
- 15. Where does it fit? You’re most likely to use multiple languages to build your application—Neal Ford’s vision for Polyglot Programmer. Martin Fowler argues that rather than using one big general purpose language, applications will use several small and limited DSLs—Languages Oriented Programming. Ola Bini argues at http://ola-bini.blogspot.com/ 2008/01/language-explorations.html that "three language layers will emerge in large applications" 15
- 16. Where does it fit? Ola’s Pyramid Expressive Domain Specific DSL Layer Groovy/ Dynamic Layer JRuby (Most Functionality) Java/Scala/ JVM Small Stable Layer 16
- 17. What’s Need to Build ‘em? Objects + Meta Programming (Aspects) + lots of Patience + 17
- 18. Types of DSLs External DSLs Internal DSLs 18
- 19. External DSL You define a new language You then parse the commands to take actions You have the liberty to chose the syntax you like You’re in full control—that’s good... and bad Can be lot of fun ;) One of my first jobs was to maintain lex and Yacc... 19
- 20. External DSL Examples CSS is an example of an external DSL! 20
- 21. External DSL Examples Good old Makefile is an example of external DSL 21
- 22. External DSL Examples Ant is an example of external DSL 22
- 23. Internal DSL Also known as Embedded DSLs Built on top of a host language Constructs of your host language are construed to form a DSL You don’t need to write an separate parser—that’s less work Commands tactfully map over to constructs like methods, etc. You can enjoy the host language’s flexibility, but you get bitten by its limitations and idiosyncrasies 23
- 24. Internal DSL Examples Rake is an example of internal DSL! It is pure Ruby 24
- 25. Internal DSL Examples Gant is an example of internal DSL! It is pure Groovy, wrapper around Ant 25
- 26. Internal DSL Examples easyb is an example of internal DSL It is a Behavior Driven Design Tool and uses Groovy for expressing stories and behavior in a DSL form 26
- 27. External or Internal It depends on your application Certain (dynamic) languages are better suited for internal DSLs Smalltalk, Lisp, Ruby, Groovy, ... Other languages are better suited for external DSL and offer good parsing libraries or capabilities C++, Java, C#, ... 27
- 28. External or Internal External Internal +You decide syntax - You decide within limits of host language -You write parser for + Language takes care it of parsing + A tad easier to - You gotta find your design way around host + Once you write a - Hard to validate at parser, validation is a the moment, good breeze research potential 28
- 29. Are all Languages Suited for Not really Internal DSLs? Low Ceremony + Metaprogramming is essential Scala, for example, has low ceremony, but lacks metaprogramming capabilities. So, not so easy to write internal DSLs with it Groovy, Ruby, ... shine due to high essence, low ceremony, and metaprogramming 29
- 30. Characteristics of a DSL What are some of the qualities of a DSL? Context Driven Extremely context sensitive Fluent Interfaces Provides for a humane, easy to understand interface 30
- 31. Context Driven DSL is extremely context sensitive or context driven A lot of things are knows from the context Without context, we may be confused or misled With context, there is less clutter, terse, but readable 31
- 32. Context Driven ... I heard my friend Neal Ford yell out Quad Venti Latte with 2 Extra Shots What’s he talking about? He’s using the Starbucks DSL Nowhere did he mention the word coffee, but he sure got a good one at a high price ;) That’s context driven 32
- 33. Context Driven ... I heard my friend Scott Davis mutter place a $ in a GString What’s he talking about? You don’t want to know He sure was talking about embedding variables into the Groovy’s mutable string class That’s also context driven :) 33
- 34. Fluent Interface I was going to call this hygienic interface I like the name Eric Evans and Martin Fowler promote–Fluent Interface/Humane Interface It’s designed to be readable and to flow naturally Not easy to design–you put in more effort to create it, so it is easier for users to use 34
- 35. Code With No Context What do you do with mailer object after call to send? Is the order important? Do I have to create an object each time? ... Can I just get my work done, can this be simpler? 35
- 36. Code With Context 36
- 37. Let’s Look at them both We’ll see later how to build these... 37
- 38. How do you write a Loop? Find total of numbers from 1 to 10 Why does the Java loop look like this? 38
- 39. Fluent Loops (Groovy) 39
- 40. How to get Fluency? You can achieve fluency in Java as well You can use method chaining with a little compromise 40
- 41. A Little Compromise Command Query Separation was promoted by Bertrand Meyer Command methods—mutators or modifiers—affect object state and don’t return anything Query methods—don’t affect object state and return useful information You compromise a little to be fluent (kind of like words bent to rhyme in a poem) Command methods return self or a promoter for a good flow 41
- 42. Fluent Interface in EasyMock 42
- 43. Fluent Interface in JSONObject Library 43
- 44. Fluent Interface in Guice 44
- 45. Fluency in Rails/Active Records 45
- 46. Fluency in Grails/GORM 46
- 47. Let’s Order Pizza Voice on line (VOL): Thanks for calling Joe’s You: Ya, A Large Thin Crust VOL: Toppings? You: Olives, Onions, Bell Pepper VOL: Address You: 101 Main St.,... VOL: Card? You: Visa 1234-1234-1234-1234 VOL: 20 minutes–Thank you 47
- 48. Java Pizza Order Not fluent Very noisy—how many times do you have to say joes_pizza? Can we make it fluent? 48
- 49. with Some languages have a with keyword within the scope, methods are invoked on an implicit object Here is an example from JavaScript 49
- 50. with in Groovy? Groovy has with keyword which is synonym for identity method 50
- 51. How about Fluent Java? Less clutter There is a context in each call Each set method (except setCard()) returns this (PizzaShop) Can we make this a bit more readable? 51
- 52. A bit more Fluent... Method names make sense in the flow, but may not make sense alone What’s a catch? 52
- 53. Ordered vs. Unordered Some DSLs may require a certain order in the flow You can force ordering by tactfully defining return types that will allow method chaining in only certain order Not easy Others may not require ordering It depends on the particular problem Ideally, not requiring an order is great, but may not always be possible 53
- 54. How to Enforce Sequence? 54
- 55. Closures Make It Easier 55
- 56. OK, but... You may not be able to deviate from standard API conventions What if it is existing API or there are other reasons to follow conventions? You can use a Façade or expression builder It sits on top of existing traditional API and provides context and fluency For example, Groovy has a number of these builders built-in 56
- 57. Groovy Builder: XML Fluency to build XML 57
- 58. Groovy Builder: Swing Fluency to build Swing GUI 58
- 59. Creating DSLs You may use tools like Antlr for working with DSLs JetBrains is working on Meta Programming System(MPS) Languages like Ruby and Groovy may it easier to create (internal) DSLs What makes Groovy attractive? Classes are always open Closures and Builders Categories and ExpandoMetaClass To some extent operator overloading 59 Parenthesis are almost optional (a bit lacking)
- 60. Creating a DSL in Groovy file:order See next page file:process.groovy output 60
- 61. Creating a DSL in Groovy contents of file:defs.groovy methodMissing 61
- 62. transmogrification How to deal with fluency, context, and ordering You can tactfully return different interfaces so only correct sequence of calls will fit in Return an appropriate interface from your methods and let method chaining take over 62
- 63. Using Categories Type conversions ------------------------ 2 => int .days => int .ago => Calendar .at => Date 63
- 64. Using ExpandoMetaClass 64
- 65. Using EMC 65
- 66. Categories vs. ExpandoMetaClass Categories allows you to tactically enhance a class ExpandoMetaClass is far reaching, global in nature You may not want to affect a class globally Categories provide controlled flexibility 66
- 67. Run Your DSL within a Context Running your DSL out in the open is not good: Unpredictable, unsettling Run it within the context of an object 67
- 68. Running in a context scores See next page Output 68
- 69. Running in a Context 69
- 70. Running in a Context 70
- 71. References http://martinfowler.com/bliki/DomainSpecificLanguage.html http://docs.codehaus.org/display/GROOVY/Writing+Domain-Specific+Languages http://docs.codehaus.org/display/GROOVY/Gant http://groovy.codehaus.org/ExpandoMetaClass http://www.onboard.jetbrains.com/is1/articles/04/10/lop/ http://www.jetbrains.com/mps Martin Fowler’s book work in progress: http://martinfowler.com/dslwip A Chapter on creating DSL in Groovy: “Programming Groovy: Dynamic Productivity for Java Developers” by Venkat Subramaniam (Pragmatic Bookshelf). You can download examples and slides from http://www.agiledeveloper.com - download 71
- 72. References A number of references from the following URL http://martinfowler.com/bliki/DomainSpecificLanguage.html http://docs.codehaus.org/display/GROOVY/Writing+Domain-Specific +Languages http://docs.codehaus.org/display/GROOVY/Gant http://groovy.codehaus.org/ExpandoMetaClass http://www.onboard.jetbrains.com/is1/articles/04/10/lop/ http://www.jetbrains.com/mps You can download examples and slides from http://www.agiledeveloper.com - download 72
- 73. Thank You! Please fill in your session evaluations You can download examples and slides from http://www.agiledeveloper.com - download 73