Programming requires much more than just writing code in a programming language. It is usually done in the context of a stateful environment, by interacting with a system through a graphical user interface. Yet, this wide space of possibilities lacks a common structure for navigation. Work on programming systems fails to form a coherent body of research, making it hard to improve on past work and advance the state of the art. In computer science, much has been said and done to allow comparison of **programming languages**, yet no similar theory exists for *programming systems*; we believe that programming systems deserve a theory too.
We present a framework of *technical dimensions* which capture the underlying characteristics of programming systems and provide a means for conceptualizing and comparing them. We identify technical dimensions by examining past influential programming systems and reviewing their design principles, technical capabilities, and styles of user interaction. Technical dimensions capture characteristics that may be studied, compared and advanced independently. This makes it possible to talk about programming systems in a way that can be shared and constructively debated rather than relying solely on personal impressions. Our framework is derived using a qualitative analysis of past programming systems. We outline two concrete ways of using our framework. First, we show how it can analyze a recently developed novel programming system. Then, we use it to identify an interesting unexplored point in the design space of programming systems.
Much research effort focuses on building programming systems that are easier to use, accessible to non-experts, moldable and/or powerful, but such efforts are disconnected. They are informal, guided by the personal vision of their authors and thus are only evaluable and comparable on the basis of individual experience using them. By providing foundations for more systematic research, we can help programming systems researchers to stand, at last, on the shoulders of giants.
PerceptIn(PerceptIn公司);University of Delaware(特拉华大学);University of California, Irvine(加州大学欧文分校);Laboratoire ETIS(ETIS实验室);CY Cergy Paris Université(CY塞尔吉-巴黎大学);ENSEA(国立高等电子及应用学院);CNRS(法国国家科学研究中心)
C++0x是C++程序设计语言的ISO标准修订版的工作名称,原计划于2009年发布,但推迟到2011年。C++0x中最大的语言扩展是“概念”,即用于约束模板参数的特性集合。2008年9月,C++标准委员会投票将概念扩展纳入C++0x,但随后在2009年7月,委员会投票将概念扩展退出C++0x。本文是我对2003年至2009年“概念”工作中的技术挑战和辩论的描述。为了提供一些背景知识,本文还描述了受约束的参数多态性的设计空间,或者通俗地称为受约束的泛型。虽然这篇文章的目的是为了让一般人都能理解,但它的目标读者是具有函数式编程和程序设计语言理论背景的读者。本文来源于2010年3月在牛津大学Spring School on Generic and Indexed Programming的一次演讲。