Anonymous user
Rosetta Code:Village Pump/Dialects: Difference between revisions
Rosetta Code:Village Pump/Dialects (view source)
Revision as of 15:03, 28 January 2012
, 12 years agoreal problem and other thoughts
m (headinging change because there may be other examples worth discussing) |
(real problem and other thoughts) |
||
Line 12:
: 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)
: I'm going to read into the proposal that navigation is really the issue and not pure numbers. If we worry about pure numbers, we have about 600 tasks and 450 languages which results in a pretty big matrix. Not that we will ever see that as other than a sparse-ish matrix. When that happens we will need to solve that problem. Until then I have to fall back onto YAGNI. I suggest we put some practical examples and suggestions/ideas here. Then when a community starts to have a problem they have a place to come for ideas. --[[User:Dgamey|Dgamey]] 15:03, 28 January 2012 (UTC)
==Examples==
=== Icon and Unicon ===
Line 17 ⟶ 18:
* 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.
* In tasks, I have one header with both major variant names in a single header line. Both Icon/Unicon were used because of recognition and to prevent orphaned headings (This may become more problematic as there is also a [[Jcon]] and [[ObjectIcon]]). Orphaned headings and duplicate efforts is a big problem if you have more than a few contributors. I found that having a combined header that sorts early worked best.
:: At one point I had thought of disambiguation pages as a possible part of the solution but I concluded I didn't really need them and they didn't add much in this case. That may not be true with a large number of true variants and also like named but unrelated languages (think Basic and VisualBasic).
* Under the task heading there is a structure that allows different solutions where there are differences. However, where the differences are very minor I usually rely upon description text.
I tried a couple of kicks at it and found this approach practical (not necessarily perfect). It may or may not work with others. Hope this helps.
| |||