arXivDaily arXiv每日学术速递 周一至周五更新
arXiv 0707.4166cs.SE
收藏

软件构件和元语言的简约原则

Parsimony Principles for Software Components and Metalanguages

Todd L. Veldhuizen

摘要:

软件是一种通信系统。通信的通常主题是程序的行为,由程序编码。领域特定的库是代码本,领域特定的语言是编码方案,等等。为了将隐喻转化为方法,我们采用了信息论的工具--有效沟通的研究--来探索语言和库让我们沟通程序的效率。在以前的工作中,我们开发了一个信息理论分析的问题域中的软件重用。这篇新论文使用信息论来分析组件、生成器和元语言设计中的权衡。我们寻求两个问题的答案:(1)我们如何判断一个组件是过度或欠广义?利用最小描述长度原则,我们建议最好的组件产生用例的最简洁的表示。(2)如果我们把程序设计语言看作是元语言的集合,每种元语言都提供一种互补的抽象风格,那么这些元语言如何帮助或阻碍我们有效地描述软件呢?我们描述了一个复杂的三角形之间的相互作用的抽象机制的力量,重用的数量,它使,其使用的认知困难。

英文摘要:

Software is a communication system. The usual topic of communication is program behavior, as encoded by programs. Domain-specific libraries are codebooks, domain-specific languages are coding schemes, and so forth. To turn metaphor into method, we adapt toolsfrom information theory--the study of efficient communication--to probe the efficiency with which languages and libraries let us communicate programs. In previous work we developed an information-theoretic analysis of software reuse in problem domains. This new paper uses information theory to analyze tradeoffs in the design of components, generators, and metalanguages. We seek answers to two questions: (1) How can we judge whether a component is over- or under-generalized? Drawing on minimum description length principles, we propose that the best component yields the most succinct representation of the use cases. (2) If we view a programming language as an assemblage of metalanguages, each providing a complementary style of abstraction, how can these metalanguages aid or hinder us in efficiently describing software? We describe a complex triangle of interactions between the power of an abstraction mechanism, the amount of reuse it enables, and the cognitive difficulty of its use.

机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。

↑