Category talk:Unicon: Difference between revisions

m
header level fixup
m (moved background sections and guidance to end of page)
m (header level fixup)
Line 1:
Note: This page is linked to from the [[:Category_talk:Icon]] page.
 
== How to go about solving the tasks ==
 
== How to go about solving the tasks ==
 
== Intent .v. Direction of tasks ==
 
There was an interesting discussion on [http://sourceforge.net/mailarchive/forum.php?forum_name=unicon-group the Unicon group forum] about meeting the intent .v. literacy in solving tasks. The [[Loops/Break]] task was used as a point of discussion.
 
Line 13 ⟶ 10:
 
=== Style ===
 
We should be aiming for programs that are Icon/Unicon like. Not just for translations from something like JavaScript or Basic.
* What should be done with if we find code that looks like a bad translation of something else or even something that could better represent Icon/Unicon. Personally I think they should be replaced with examples that show how the language can be used. There may be a case for keeping them as an alternate version and calling out that it is a bad translation; however, given that this site is about showing off the essence of languages - why would you do that? --[[User:Dgamey|Dgamey]] 21:17, 8 April 2010 (UTC)
 
=== Quality ===
 
There are a number of aspects of the sample programs that need improvement. These include:
 
Line 27 ⟶ 22:
 
=== Multiple Solutions ===
 
What happens when there are multiple good examples of how to solve a task with different approaches? Should we show more than one?
 
Line 35 ⟶ 29:
 
=== 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)
 
= StuffHELP to DoWanted =
=== Icon and /Unicon Introductionfeatures ===
 
== HELP Wanted ==
 
* Object oriented examples
* Graphics examples, particularly where we can show differences between Unicon and Icon
Line 56 ⟶ 47:
 
== Errors/Review Lists ==
 
See [[Template:Example-needs-review]] and [[Template:Incorrect]]. I'm not sure how you're supposed to know what is to be reviewed. Examples I've seen don;t have a lot of explanation.
 
Line 69 ⟶ 59:
 
== The IPL and Uni Libraries ==
 
[[:Category:Solutions_by_Library]] need writing. Stubs have been created for:
 
Line 93 ⟶ 82:
 
== Unimplementable tasks ==
 
Mark tasks that aren't doable in Icon/Unicon as such. I believe there is an omit markup in curly braces, but I don't know much about it.
 
Line 106 ⟶ 94:
 
== Implementations ==
 
There are Category Pages for Implementations of other languages. There are certainly several variants that can be described for Icon including Jcon, MT Icon, IDOL, etc.
 
== Requesting Tasks ==
 
See [[Rosetta_Code:Village_Pump/Request_a_programming_task]]
 
Line 127 ⟶ 113:
* Anyone else I forgot?
 
= Wiki and Icon/Unicon task Formatting =
== How much to put in the language templates ==
 
One question that comes to mind when thinking about Rosetta Code is how much to put into the language category pages?
 
Line 136 ⟶ 122:
 
=== Category Page Language Box ===
 
I had a go at the main box. Unfortunately a lot of the terms aren't explicitly defined here.
* byte code compiled as I recall (way before Java made it popular)
Line 178 ⟶ 163:
 
=== Language Comparison Table ===
 
A first stab at the LCT
* paradigms = procedural, object oriented, goal-directed (not defined and is this the same as logical programming)
Line 199 ⟶ 183:
=== Other References ===
[[wp:Comparison_of_programming_languages|Wikipedia: Comparison of programming languages]]
 
=== Icon and Unicon Introduction ===
 
[[Icon+Unicon/Intro|To provide detailed introduction to Unicon and Icon that can be referenced in tasks.]]
 
== How to reasonably handle Icon .v. Union similarities and differences ==
 
=== Summary ===
 
Line 213 ⟶ 192:
 
=== Template/ How to write up Icon and Unicon markup ===
 
As a general rule for Icon and Unicon tasks, unless there is separate code or notations about differences the code should run under both dialects.
 
Line 373 ⟶ 351:
 
==== Consistency and Eliminating Duplication ====
 
It's desirable to present all Icon and Unicon code consistently. This discussion was started to help achieve that goal. To that end, there are some objectives:
* Eliminate duplication
Line 390 ⟶ 367:
 
===== Discussion on how this evolved =====
 
: May I suggest creating templates for these various references so that the wording can be adjusted uniformly if the need is felt? (Don't put the <nowiki>==...==</nowiki> in a template, though, because that breaks section editing's ability to pick out the right sections.) Also, insofar as Unicon is ''not'' actually Icon (I don't know either language so I can't judge this), for the second sort of cross-reference, use a header of the form ==[[Icon]]== instead because that will leave it on Icon's unimplemented list for people to work on as an Icon-only example. —[[User:Kevin Reid|Kevin Reid]] 11:22, 11 April 2010 (UTC)
::This is a good idea. I'm still not entirely happy with the way this works. I'd really like to be able to group Unicon and Icon side by side. But without doing something odd with the names the risk is that they would get moved at some point. --[[User:Dgamey|Dgamey]] 17:29, 11 April 2010 (UTC)
Anonymous user