J/HouseStyle: Difference between revisions
< J
Content deleted Content added
→goals: starting suggestions |
m →goals: formatting |
||
Line 2:
== goals ==
<ol>
* increasing its exposure (coverage of tasks)▼
<ul>
* showcasing its strengths (terseness, clarity)▼
* making examples accessible to newbies (e.g. judicious naming of code segments)▼
* provide resource of "good" example J code to J learners▼
* provide a Rosetta stone for explicit and tacit forms of J▼
</ul>
</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
- 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)
- provide resource of "good" example J code to J learners
- provide a Rosetta stone for explicit and tacit forms of J