Category:Icon Implementations: Difference between revisions
Content added Content deleted
m (Created page with '{{implementation cat|Icon}}') |
(dialects) |
||
| Line 1: | Line 1: | ||
{{implementation cat|Icon}} |
{{implementation cat|Icon}} |
||
* [[Category:Unicon|Unicon the Unified Extended Dialect of Icon]] |
|||
* [http://www.cs.arizona.edu/icon/jcon/ Jcon a Java based implementation of Icon] - no longer maintained. |
|||
* [http://www.cs.arizona.edu/icon/ftp/doc/ipd276.pdf ProIcon] - a version of Icon for the Macintosh] |
|||
* [http://www.cs.arizona.edu/icon/ftp/doc/tr85_2.pdf Seque] - an Icon variant with streams. Streams are a data object that produces and retains values. |
|||
* [http://www.cs.arizona.edu/icon/ftp/doc/tr84_9.pdf Rebus] - a SNOBOL4 / Icon hybrid |
|||
* MTIcon - a multi-threading implementation of Icon, superseded by Unicon |
|||
* IDOL - a pre-processor extension to Icon to facilitate object oriented code, superseded by Unicon |
|||
Revision as of 03:27, 29 July 2010
These are all of the implementations of Icon on Rosetta Code.
- Jcon a Java based implementation of Icon - no longer maintained.
- ProIcon - a version of Icon for the Macintosh]
- Seque - an Icon variant with streams. Streams are a data object that produces and retains values.
- Rebus - a SNOBOL4 / Icon hybrid
- MTIcon - a multi-threading implementation of Icon, superseded by Unicon
- IDOL - a pre-processor extension to Icon to facilitate object oriented code, superseded by Unicon