You are an architect on your company's new flagship application. The app
encompasses several business and technical domains that are, in your opinion,
well suited to domain-specific languages (DSLs). In years past, you would
have turned to XML as the solution for all your DSL needs. With or without
schemas, you would specify configuration files and scripts in files foul with
angle brackets. Thankfully, for the discerning .NET architect, DSL
implementation options are now plentiful.
For each DSL you create, you need to identify the target user for that DSL.
Is she a non-developer subject matter expert, a particular kind of developer,
or an end user? This choice will drive the kinds of tools you make available
to support the DSL. It will also influence choices such as whether your DSL
is interpreted or when it is compiled.
Before selecting DSL implementation strategie... (more)
You are an architect on your company's new flagship application. The app
encompasses several business and technical domains that are, in your opinion,
well suited to domain-specific languages (DSL). In years past, you would have
turned to XML as the solution for all your DSL needs. With or without
schemas, you would specify configuration files and scripts in files foul with
angle brackets. Thankfully, for the discerning .NET architect, DSL
implementation options are now plentiful.
For each DSL you create, you need to identify the target user for that DSL.
Is she a non-developer ... (more)