HackerPapers

arXiv:1409.2378cs.SE

Design Guidelines for Domain Specific Languages

Gabor Karsai, Holger Krahn, Claas Pinkernell, Bernhard Rumpe, Martin Schindler, Steven Völkel

Early discovery. Linked by one identifiable commenter. This paper is outside the main ranking; a mention is not an endorsement.

Abstract

Designing a new domain specific language is as any other complex task sometimes error-prone and usually time consuming, especially if the language shall be of high-quality and comfortably usable. Existing tool support focuses on the simplification of technical aspects but lacks support for an enforcement of principles for a good language design. In this paper we investigate guidelines that are useful for designing domain specific languages, largely based on our experience in developing languages as well as relying on existing guidelines on general purpose (GPLs) and modeling languages. We defined guidelines to support a DSL developer to achieve better quality of the language design and a better acceptance among its users.

arXiv comments
7 pages, 5 figures. Proceedings of the 9th OOPSLA Workshop on Domain-Specific Modeling (DSM' 09). Helsinki School of Economics. TR no B-108. Orlando, Florida, USA, October 2009
Journal reference
DOI
Subjects
cs.SESoftware Engineering

On Hacker News

Linked by 1 identifiable commenter in 1 comment across 1 thread, from Jul 2018 to Jul 2018. Found in 1 HN submission from Nov 2023 to Nov 2023. Open submission discussions.

Comments linking this paper, per year.

Discussed in comments1 thread

  1. Designing a Good DSL 1 comment

    • (EDIT: I replaced asterisks with <AST> in the pattern below, since HN doesn't have a convenient way to escape asterisks last I checked.) > First, most of its syntax beyond the very basics like "X+" or "[^X]" is impossible to remember. It’d be nice to know what "(?<!X)" does…

      TwisolView on HNParent context

Submitted to Hacker News

Connected through shared HN threads, not inferred similarity or a recommendation.