Folks,
One question that comes up is how different does the Unicon code have to be to
have it's own version?
Clearly anything that takes advantage of a major feature of Unicon should. But
how about minor differences? I think a case could be made either way. The
trick would not to be overwhelmed by minor differences.
An example of an entry where a small but significant difference shows up would
be in the old Icon way to do sockets/messaging and the Unicon way as in:
http://rosettacode.org/wiki/HTTP
But what if we're highlighting essentially syntactic sugar like the following?
* local var := value
* procedure x(y:integer)
It might be better to find one or two examples only for these where they make
the most sense. To date, I'm not including this a significant enough.
It might be an idea to list these (or a link to these) on the language pages:
* http://rosettacode.org/wiki/Icon
* http://rosettacode.org/wiki/UniconNote: As I understand it the
language page is not intended to duplicate language home pages or Wikipedia
pages. By way of example some of the better language pages are for Oz, Python,
TCL, and J
David
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Unicon-group mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/unicon-group
