Anonymous user
Category talk:Unicon: Difference between revisions
m
→Template/ How to write up Icon and Unicon markup: more
m (header level fixup) |
|||
| (13 intermediate revisions by the same user not shown) | |||
Line 30:
=== Constrained Tasks ===
I'm not sure how many of these there may be here. But using the [https://tapestry.tucson.az.us/twiki/bin/view/Main/LongestStringsPuzzle| Unicon Twiki - Find the longest string problem without using comparisons, math, or lists] as an example, perhaps we should introduce a few. I'd like to see how some of the more traditional languages do this :) --[[User:Dgamey|Dgamey]] 21:17, 8 April 2010 (UTC)
=== Level of detail where Icon and Unicon are different ===
A number of task writers had taken to explaining some of the fundamental differences underlying Icon and Unicon in individual tasks. It's better to put the text into the Introduction and refer to it from the task. See:
[[Icon+Unicon/Intro|To provide detailed introduction to Unicon and Icon that can be referenced in tasks.]]
=== ObjectIcon, Jcon and Other variants ===
I recently discovered Object Icon and will set up some stub pages for it.
* There will be a link back here for this discussion
* I strongly encourage other contributors to keep all the Icon variants together under one heading set as has been done with Icon and Unicon.
= HELP Wanted =
Line 106 ⟶ 117:
== Thanks ==
* Clint for valuable insight into everything▼
* [[User:SteveWampler]] for valuable insight into co-expressions
* [[User:MattOates|Matt Oates]] for work on the syntax coloring templates
▲* Clint for valuable insight into everything
* Art E, Andrew C
* [[User:Peter|Peter Lane]] for numerous contributions and helping us cross into the top 20!
* Anyone else I forgot?
Line 150 ⟶ 161:
* [[:Category:Programming_paradigm/Event-driven]] applies to the monitoring interface MT-Icon and Unicon, and probably co-expressions. Although some of the comments on the page such as about poor performance I'm not sure are apply.
* [[:Category:Programming_paradigm/Object-oriented]] Unicon
* [[:Category:Programming_paradigm/Concurrent]] may be a stretch for co-expressions; however, Unicon v12 adds support for mutexes▼
==== Clearly not applicable ====
Line 156 ⟶ 168:
==== Not clear / Mixed ====
▲* [[:Category:Programming_paradigm/Concurrent]] may be a stretch for co-expressions
* [[:Category:Programming paradigm/Declarative]] if only for OO in Unicon. SNOBOL4 patterns were given as an example of declarative but I think it's a stretch.
* [[:Category:Programming_paradigm/Dynamic]] as a paradigm seems to mean scripting but there are also references to dynamic record construction
Line 190 ⟶ 201:
: Conversion to this format is ongoing and proceeding alphabetically --[[User:Dgamey|Dgamey]] 14:16, 30 January 2011 (UTC)
=== Note on templates for other variants ===
I've stubbed in categories for [[Jcon]] and [[ObjectIcon]]; however, there are no code examples for either at this time. If you plan on adding them please add the code as per the templates in the sections below using a single Icon/Jcon/ObjectIcon/Unicon header like one of these (assuming all examples are present):
<pre><nowiki>
</nokiki></pre>
=== Template/ How to write up Icon and Unicon markup ===
Line 210 ⟶ 228:
end</lang>
{{libheader|Icon Programming Library}}
[http://www.cs.arizona.edu/icon/library/src/procs/XXXX.icn XXXX provides YYYY]
{{libheader|Unicon Code Library}}
Output:<pre>sample output</pre></nowiki></pre>
The second case is where Icon and Unicon examples are ''significantly'' different. In this case the difference will be visually obvious in task indices.
Line 230 ⟶ 250:
end</lang>
{{libheader|Icon Programming Library}}
[http://www.cs.arizona.edu/icon/library/src/procs/XXXX.icn XXXX provides YYYY]
{{libheader|Unicon Code Library}}
Output:<pre>sample output</pre></nowiki></pre>
In the third case, only one solution is presented. At this time it is unlikely there will be an Icon only case. Unicon only solutions should be presented as shown below. If it is the case that the solution isn't possible in Icon then an omit template should be coded as well. Using this structure will keep the look and feel of the task index, be properly reflected in tasks implemented/not implemented on the language category page, and allow someone to provide an Icon solution at a later date with minimal modification by converting to the second format.
Line 243 ⟶ 265:
# Unicon code
...
end</lang
{{libheader|Icon Programming Library}}
[http://www.cs.arizona.edu/icon/library/src/procs/XXXX.icn XXXX provides YYYY]
{{libheader|Unicon Code Library}}
</nowiki></pre>
=== Template / Other Useful Markup ===
Line 284 ⟶ 311:
--[[User:Dgamey|Dgamey]] 15:53, 31 December 2010 (UTC)
==== Translation of ====
<pre><nowiki>{{trans|language}}</nowiki></pre>
--[[User:Dgamey|Dgamey]] 11:10, 23 June 2011 (UTC)
=== Template for new tasks ===
The following quick copy and paste may be helpful creating new tasks.
<pre><nowiki>== {{header|Icon}} and {{header|Unicon}} ==
▲== {{header|Icon}} and {{header|Unicon}} ===
<lang Icon>
</lang>
| |||