Anonymous user
Rosetta Code:Village Pump/Dialects: Difference between revisions
Rosetta Code:Village Pump/Dialects (view source)
Revision as of 14:51, 28 January 2012
, 12 years agoheadinging change because there may be other examples worth discussing
(My position.) |
m (headinging change because there may be other examples worth discussing) |
||
Line 3:
|summary=What are, or should be, the Rosetta Code conventions for dialects of programming languages - implementations on specific platforms that may have minor differences of syntax and functionality from the official distributions?
}}
I would rather have different dialects not count as language of their own. Otherwise we have many main languages, which are similar in many ways, and many more items to show the code for. The navigation gets cluttered up and language lists would need to be structured in a hierarchy. This is already a problem with ZX80 Basic and C64 Basic and maybe more variants.
Line 12 ⟶ 11:
[[User:Codecop|Codecop]] 13:33, 28 January 2012 (UTC)
: My general position has been to leave the distinction to the language community. To a C++ programmer, all BASIC implementations might look alike, but to people with production code in QuickBasic, that's a nonsensical position. --[[User:Short Circuit|Michael Mol]] 14:44, 28 January 2012 (UTC)
:: I tend to agree, it will be very specific to the language and community. Guidance and suggestions are probably welcome and this would be a good anchor page, but I would not want to weigh in on any of the languages mentioned above. --[[User:Dgamey|Dgamey]] 14:51, 28 January 2012 (UTC)
=== An Example, Icon and Unicon ===▼
==Examples==
Hi, I did a lot of the work on [[Icon]] and [[Unicon]] which are closely related. Much of what I went through is discussed on the talk pages for [[Category_talk:Unicon]]. What you are proposing isn't far from what I did. Here's a summary, you can also see how it looks (there's over 450 examples on RC):
* Each distinct variant gets it's own page/category. If there are minor variants, it may make sense to put them in a section of the major variant's page.
| |||