Jump to content

Talk:Concatenative programming language

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by John Nowak (talk | contribs) at 09:24, 22 February 2009. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

This doesn't appear to be a term with significant usage outside of wikipedia, and also is very poorly defined here. Should this be deleted?

  • Manfred von Thun keeps referring as "concatenative" to those languages that he includes in a class with Joy. There is also a discussion group dealing with Joy and related topics. To browse previous messages, or to join the group, see yahoo group: concatenative These messages can be read without joining the group. There have been 1116 contributions in the first two years, 1-MAY-2000 to 1-MAY-2002. Perhaps there is a better (i.e., more standard way of referring to this class of languages? If you do know of one, it would probably make sense to change the name. — danakil 01:12, Aug 26, 2004 (UTC)
  • Charles Moore didn't invent the name, but sure invented the concept. However, the only name he ever gave it was Forth. Although a long term Forth user (over 30 years), I have no problem with finally having a name for a class of programming languages that was previously unnamed. Mdfischer 23:06, 27 April 2007 (UTC)[reply]

Contradicting information

The article says "or stack-based", but the category lists languages that aren's stack-based. I see some contradiction in this. --Stesch 13:10, 21 October 2007 (UTC)[reply]

Replacement

The article here has many issues. The issues were discussed on the concatenative mailing list. The full discussion is available here:

   http://www.nabble.com/the-concatenative-wikipedia-article-td21227513.html

The result of this discussion is a new article that better addresses the topic. It can be viewed here:

   http://en.wikipedia.org/wiki/User:John_Nowak/Sandbox/Concatenative

Assuming there are no issues, I'll go ahead and switch the article to the new version.