Category:Icon Implementations: Difference between revisions
Content added Content deleted
No edit summary |
m (Jcon has its own page on RC (listed as Icon implementation)) |
||
| Line 3: | Line 3: | ||
The following are other variants of Icon |
The following are other variants 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/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/tr85_2.pdf Seque] - an Icon variant with streams. Streams are a data object that produces and retains values. |
||
Latest revision as of 19:04, 27 May 2014
These are all of the implementations of Icon on Rosetta Code.
The following are other variants of Icon
- 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