incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reto Bachmann-Gmür (JIRA) <>
Subject [jira] Commented: (CLEREZZA-435) Coding convention compliance
Date Thu, 24 Feb 2011 11:22:38 GMT


Reto Bachmann-Gmür commented on CLEREZZA-435:

The coding guidelines might be enhanced to say more about scala.

"How a tab is rendered depends on the preference of the viewer, but for calculating the line
length (see below) we equate a tab to a length of 4 characters.

Avoid indents of more than 5 levels."

For scala the limit of 5 indentation level seems quite low, also a tab could be equated to
two spaces. But I'm not very convinced by the maximum line-length anyway.

> Coding convention compliance
> ----------------------------
>                 Key: CLEREZZA-435
>                 URL:
>             Project: Clerezza
>          Issue Type: Improvement
>            Reporter: Hasan
>            Priority: Trivial
>         Attachments: zz-coding-conventions.v1.txt
> This issue is about writing code which should comply to certain conventions within Clerezza's
> An initial document on the coding conventions is attached to this issue.
> If you want to update Clerezza code so that it complies with these conventions, please
use this issue number
> when you commit your changes. We might do this every now and then, therefore, please
don't resolve and close this issue.
> Please DON'T use this issue number in your commit, if you also have other changes in
the code besides changes
> due to coding conventions. If you could separate your commit in two steps, then it would
be the best. 
> One for the coding conventions (using this issue number in your commit) and the other
for the fix due to the "real" issue 
> you want to solve (using the respective issue number).

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message