Automatic programming: Difference between revisions

Revision as of 13:41, 26 November 2007

Revision as of 01:11, 13 December 2007

Line 1:

In [[computer science]], the term '''automatic programming'''<ref>Ricardo Aler Mur, "[http://et.evannai.inf.uc3m.es/icml06/aiptutorial.htm Automatic Inductive Programming]", ''ICML 2006 Tutorial''. June 2006.</ref> identifies a type of [[computer programming]] in which some mechanism generates a [[computer program]] rather than have human [[programmer]]s write the code.

There has been little agreement on the precise definition of automatic programming, mostly because its meaning has changed over time. [[David Parnas]], tracing the history of "automatic programming" in published research, noted that in the 1940s it described automation of the manual process of punching [[paper tape]]. Later it referred to translation of [[high-level programming language|high-level]] [[programming language]]s like [[Fortran]] and [[ALGOL]]. In fact, one of the earliest programs identifiable as a [[compiler]] was called [[AutocoderAutocode]]. Parnas concluded that "automatic programming has always been a [[euphemism]] for programming in a higher-level language than was then available to the programmer."<ref>D. L. Parnas. "[http://klabs.org/richcontent/software_content/papers/parnas_acm_85.pdf Software Aspects of Strategic Defense Systems]." ''American Scientist''. November 1985.</ref>

''Generative programming'' is a style of [[computer programming]] that uses automated [[source code]] creation through [[generic programming|generic]] [[class (computer science)|classes]], [[Prototype-based programming|prototypes]], [[template (programming)|template]]s, [[aspect (computer science)|aspect]]s, and [[Code generation (compiler)|code generator]]s to improve [[programmer]] productivity. It is often related to code-reuse topics such as [[software componentry|component-oriented programming]].