Ayende @ Rahien

My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by phone or email:


+972 52-548-6969

, @ Q c

Posts: 6,026 | Comments: 44,842

filter by tags archive

Building Domain Specific Languages in BooChapter 9 TOC

time to read 2 min | 201 words


  • Starting from a stable origin
  • Planning our DSL's versioning story
    • Implications of modifying the DSL Engine
    • Implications of modifying the DSL API and Model
    • Implications of modifying the DSL Syntax
    • Implications of modifying the DSL Environment
  • Regression Test Suite
  • Versioning cut off point - where to apply versioning concerns
  • Versioning strategies:
    • Abandon Ship Strategy
    • Glacial Change Strategy
    • Additive Change Strategy
    • Tower of Babel Strategy
    • Runtime Adapter Strategy
    • Compilation Adapter Strategy
    • Auto Modification Strategy
    • Self Modification Strategy
  • Versioning best practices:
    # actual content
    • Closed world
    • Regression test suite

More posts in "Building Domain Specific Languages in Boo" series:

  1. (29 Jul 2008) Chapter 9 TOC
  2. (17 Feb 2008) Available for early access



That's a lot of versioning strategies to discuss.

I am curious to your bullet point on Implications of modifying the DSL Environment. What do you mean by environment in this context? When I think of environment I usually think of concerns that should be abstracted from the DSL such as data stores where changing them should not affect the DSL.

Ayende Rahien


Yes, but a lot of them are really simple. Abandon ship == no versioning, for example.

Environment in this case refer to the naming convention, the order in which the are executed, how do you select what to execute, etc.


Ah ok, that makes sense. Looking forward to the next chapter of the book!

Comment preview

Comments have been closed on this topic.


No future posts left, oh my!


  1. Technical observations from my wife (3):
    13 Nov 2015 - Production issues
  2. Production postmortem (13):
    13 Nov 2015 - The case of the “it is slow on that machine (only)”
  3. Speaking (5):
    09 Nov 2015 - Community talk in Kiev, Ukraine–What does it take to be a good developer
  4. Find the bug (5):
    11 Sep 2015 - The concurrent memory buster
  5. Buffer allocation strategies (3):
    09 Sep 2015 - Bad usage patterns
View all series


Main feed Feed Stats
Comments feed   Comments Feed Stats