a DSL

However, most of us have already used a DSL for execution, like you suggest, though we probably never thought of it that way.

JES: You can think of a DSL as a means to communicate an idea or a concept in its own specific terms.

A major advantage of a DSL is that it requires significantly less time to understand and to communicate details of a domain.

For information about establishing an Internet connection with a broadband modem, see Set up a DSL or cable connection.

I really like having a DSL to develop integration flows in. The disadvantage of ServiceMix is pretty much tied to its advantages.

Being able to evaluate a DSL script in multiple contexts begins to blur the line between code and data.

A DSL enables you to abstract the software solution and hide the implementation details.

However, when it comes to detailed design, you need to transform the model into a DSL model.

Decomposing a DSL solution into smaller building blocks (separate tiers) presents some interesting architectural options.

It talked about the limitations of UML and the related requirement for a DSL for detailed modeling of different AUTOSAR templates.

That config file is actually a DSL designed by the framework author and developers use it to configure a running system.

Using an entity-relationship model is one form of defining a DSL.

Is mobl still a DSL, considering the fact that it has GPL features?

The concepts and abstractions of a DSL are related to a particular domain.

Defining a DSL is valuable because DSLs help to focus on a specific area by setting a very specific scope.

NET Entity Framework uses a DSL called conceptual schema definition language ( CSDL) to define conceptual models.

A "DSL" light on your modem usually shows that the line is synchronized.

A DSL is a focused, processable language for describing a specific concern when building a system in a specific domain.

By encoding the operations in a DSL, I can take extra actions (like beneficial side effects) in addition to populating data structures.

A DSL, or domain-specific language, is a scripted language designed to solve a specific programming problem.

The ability to create a DSL like Builder illustrates why expressiveness and power in languages are so critical.

This element of a DSL implementation is on of the most critical design elements.

A DSL imposes a well-defined set of types of elements and relations.

ChocTop has a DSL-ish configuration system and adds a few task to your rake file.

Several design considerations need addressing when planning a DSL.

A DSL can also use the vocabulary from the business domain and provide the translation for the IT domain.

In a DSL world, there's not a whole lot of waiting going on.

Documentation is not a DSL, and it is most certainly not understandable in many cases.

The best way to start a DSL is to doodle around and sketch something that looks right.

I recently used it while developing a DSL to represent SQL. I started with the following syntax.

Even putting aside the reality that we live in a DSL, cable modem, T1, even T3 world, this argument is silly (and that's being kind).

For instance, HTML is a DSL for defining structured web pages.

Obviously, a DSL is not required in every case.

Nowadays, it is best practice to generate code from a DSL, which is simpler to use than a general purpose language like UML.

The ability to preview a DSL before printing has been added to the DSL designer.

The above code also shows the first few steps towards defining a DSL.

With Guice 2. 0 we even support a DSL to intuitively map servlets and filters to URL paths in web applications.

For things such as business rules, you can define a DSL that directly express these rules and use a rules engine to evaluate them.

Once installed you'll be able to generate easily PDF with a DSL-ish approach (example excerpted from a Prawn sample)

A DSL is a language, that is, a collection of sentences in a textual or visual notation with a formally defined syntax and semantics

Offers a DSL for UI definition, actions, and testing

Act 3: Business Language, on how to use a DSL to make specifications readable and verifyable for the client (42: 53)

In fact, one key to using a DSL is the ability to evaluate in various contexts. Take this code for example

The language we built above is a DSL, a domain-specific language. Here is how I like to define DSLs