J/HouseStyle: Difference between revisions

From Rosetta Code
< J
Content deleted Content added
Tikkanz (talk | contribs)
→‎goals: starting suggestions
Tikkanz (talk | contribs)
m →‎goals: formatting
Line 2:
 
== goals ==
<ol>
* <li>increase the usage of J by:
* increasing its exposure (coverage of tasks)
<ul>
* showcasing its strengths (terseness, clarity)
* <li>increasing its exposure (coverage of tasks)</li>
* making examples accessible to newbies (e.g. judicious naming of code segments)
* <li>showcasing its strengths (terseness, clarity of solutions)</li>
* provide resource of "good" example J code to J learners
* <li>making examples accessible to newbies (e.g. judicious naming of code segments)</li>
* provide a Rosetta stone for explicit and tacit forms of J
</ul>
</li>
* <li>provide resource of "good" example J code to J learners</li>
* <li>provide a Rosetta stone for explicit and tacit forms of J</li>
</ol>
 
== style guidelines ==

Revision as of 21:45, 12 October 2009

This page is a sandbox for discussing the goals of the J community on RC, and to develop guidelines and standards for J code to help achieve those goals. The result will be a J house style.

goals

  1. increase the usage of J by:
    • increasing its exposure (coverage of tasks)
    • showcasing its strengths (terseness, clarity of solutions)
    • making examples accessible to newbies (e.g. judicious naming of code segments)
  2. provide resource of "good" example J code to J learners
  3. provide a Rosetta stone for explicit and tacit forms of J

style guidelines