Anonymous user
Category talk:Unicon: Difference between revisions
→Template/ How to write up Icon and Unicon markup: 3rd case
m (→Template/ How to write up Icon and Unicon markup: italic emphasis) |
|||
Line 92:
* the same code (or nearly the same code is usable with only minor differences requiring comment)
* there is a significant benefit to a Unicon only solution that requires a separate example
* there is no Icon solution provided (or possible) and the Unicon solution makes use of significant features exclusive to the dialect
A template for the general case is shown below. It has the following characteristics (a) the listing in a task is concise and visibly shows that the solution is the same, (b) both languages are indexed by the header macro, (c) the Icon language template is used for keyword coloring, etc., (d) someone searching the page for either language will find them with a text search, (e) where pages/indices are split the code shows in the first half of the alphabet making it more accessible.
Line 128:
sample output</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.
<pre><nowiki>
==Icon and {{header|Unicon}}==
The following code uses features exclusive to Unicon.
<lang Unicon>procedure main()
# Unicon code
...
nd</lang></nowiki></pre>
=== Template / Other Useful Markup ===
| |||