Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

Jump to content

Talk:IMP (programming language)

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 8 months ago by UmbyUmbreon in topic IDA, not NSA

Untitled

[edit]

The article doesn't explain what imp stands for. Is there a meaning for it?

The language was created by E. T. Irons and I remember it being claimed that IMP stood for Iron's Magnificent Plaything. Unfortunately, I can't find a source for that claim. MediaMangler (talk) 06:15, 18 May 2012 (UTC)Reply

I remember hearing that Irons got interested in extensible syntax languages from Tony Brooker and the Atlas Autocode Compiler Compiler which was also to some extent an extensible syntax system. Sorry I do not have a reference for that at the moment but I'll return here if I find it. It is probably just a coincidence that Edinburgh's extension of Atlas Autocode came to also be called Imp.  Preceding unsigned comment added by 24.243.109.9 (talk) 02:27, 24 January 2017 (UTC)Reply

IDA, not NSA

[edit]
National Security Agency
+
Institute for Defense Analyses

(in two places)

Ned Irons developed IMP at the Institute for Defense Analyses, Communications Research Division, not the National Security Agency. [1]

Flagging this as a COI out of an abundance of caution. I worked with Ned at IDA and later at Yale, where I wrote IMP72 using his syntax-directed compiler algorithm and my own method of describing the generated code. Bilofsky (talk) 21:39, 8 November 2025 (UTC)Reply

Go ahead: I have reviewed these proposed changes and suggest that you go ahead and make the proposed changes to the page. Having found the journal in question, this looks right to me. - Umby 🌕🐶 (talk) 03:21, 10 November 2025 (UTC)Reply
  1. Irons, Edgar T., Experience with an Extensible Language, Communications of the ACM, Vol. 13, Issue 1, pp. 31–40 (Jan. 1970)