Ayende @ Rahien

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

ayende@ayende.com

+972 52-548-6969

, @ Q c

Posts: 6,124 | Comments: 45,475

filter by tags archive

Building Domain Specific Languages in BooChapter 9 TOC

time to read 2 min | 201 words

Thoughts?

  • 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

Comments

Nathan

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

Nathan,

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.

Nathan

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

Comment preview

Comments have been closed on this topic.

FUTURE POSTS

  1. The design of RavenDB 4.0: Making Lucene reliable - 6 hours from now
  2. RavenDB 3.5 whirl wind tour: I’ll find who is taking my I/O bandwidth and they SHALL pay - about one day from now
  3. The design of RavenDB 4.0: Physically segregating collections - 2 days from now
  4. RavenDB 3.5 Whirlwind tour: I need to be free to explore my data - 3 days from now
  5. RavenDB 3.5 whirl wind tour: I'll have the 3+1 goodies to go, please - 6 days from now

And 13 more posts are pending...

There are posts all the way to May 30, 2016

RECENT SERIES

  1. RavenDB 3.5 whirl wind tour (14):
    02 May 2016 - You want all the data, you can’t handle all the data
  2. The design of RavenDB 4.0 (13):
    28 Apr 2016 - The implications of the blittable format
  3. Tasks for the new comer (2):
    15 Apr 2016 - Quartz.NET with RavenDB
  4. Code through the looking glass (5):
    18 Mar 2016 - And a linear search to rule them
  5. Find the bug (8):
    29 Feb 2016 - When you can't rely on your own identity
View all series

RECENT COMMENTS

Syndication

Main feed Feed Stats
Comments feed   Comments Feed Stats