Folks,
I had an email exchange with Michael Mol the creator of the Rosetta Code
Project about how to deal with very similar languages like Unicon and Icon.
He's also pointed out that Rosetta Code is on Facebook, Reddit, and Village
pump (all accessible from the wiki sidebar) if
they're looking for more ways to ask questions.
> On Fri, Apr 2, 2010 at 4:34 PM, David Gamey <[email protected]>
wrote:
>> Mike,
>>
>> Just joined. A very
neat project you have going.
>>
>> A quick question.
What happens in the case of similar languages like Unicon
>> and Icon. Unicon does a lot more. Most (likely over 99+% of Icon will
>> run unaltered under Unicon).
>>
>> Should there be one or two languages?
>>
>> Thanks,
>> David
>>
>
> The site doesn't handle such things
elegantly. It's something I want
> to fix eventually, but I
haven't figured out how that could be
> elegantly handled under
MediaWiki.
>
> A similar case to yours is C and C++. For a
large number of things,
> the syntax to accomplish the same thing
is identical. Frequently,
> you'll see something like this on a
task page:
>
> =={header|C}==
> See [[#C++]].
>
=={header|C++}==
> <lang cpp>/* some code that happens to
work under both C and C++ */</lang>
>
>
> You
might also see it flipped around:
>
> =={header|C++}==
> <lang c>/* Some code that happens to work both under C and C++
*/</lang>
> =={header|C}==
> See [[#C]].
>
>
> I would recommend having Unicon defer to the Icon example in cases
> where the most idiomatic code is identical between the two languages:
>
> =={header|Unicon}==
> See [[#Icon]].
>
> If there's a better and/or more idiomatic way to accomplish the same
> thing
in Unicon, then I'd refer to the Icon example, but also show the
> Unicon-specific approach:
>
> =={header|Unicon}==
>
The [[#Icon]] example works, but a more native way to do it in Unicon
might
> be:
> <lang unicon>/* Some code that works
better (or only works) in Unicon
> */</lang>
>
> Mike------------------------------------------------------------------------------
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
