Any other way?
This page is a great idea, but that kind of table is getting increasingly difficult to edit the more there'll be languages. Could there be any other way, such as a list something like this;
- other languages in brainfuck
- brainfuck in other languages
--Keymaker 11:17, 26 June 2007 (UTC)
- Well, I just learned how to make wiki tables. That cleaned it up a lot. I like the table format for now... --Nthern 20:51, 6 July 2007 (UTC)
- Yeah, it's a lot better now. :) --Keymaker 00:27, 7 July 2007 (UTC)
- If there exists an interpreter for language foo in language bar and language baz is Isomorphically similar to bar, then an interpreter for foo can be constructed in baz. If there exists an automatic Translator (compiler) from bar to baz, then it could be used to convert any bar program into a baz program - including a foo interpreter written in bar. A compiler can also be used as a "pre-processor" to enable a baz interpreter to also interpret bar; but I don't think that really applies to this page. The two compilers you are talking about could be used to construct Underload interpreters for any language currently interpreted by either Unlambda or brainfuck. Thus, according to the current matrix, it should be possible to construct Underload interpreters for BCT, brainfuck, Underload and Unlambda. --Nthern 02:54, 19 July 2007 (UTC)
Any links to Geocities are dead now. There are five in this article in total. Do they need to be deleted or flagged, or something like that?
- Reocities doesn't seem to have most of them; it may be worth seeing if Archive.org does. (The links should probably be kept as-is until we can find the page that was originally at the other end of them, or maybe marked as dead; the link itself should be kept in order to help finding the page it linked to, though.) --ais523 17:15, 5 March 2010 (UTC)
- I'm in favor of the idea. I assume compilation is identical to translation in this case? --Keymaker (talk) 08:23, 7 October 2014 (UTC)