I think we should probably follow the Eclipse coding style, which
is 4 spaces for indentation.
As part of the release, we should clean the code, see
https://github.com/eclipse/triquetrum/issues/79
I had assumed that part of this would be to use Eclipse to clean
the code using the Eclipse style formatter.
Longer lines are OK with me.
As a matter of personal preference, I prefer CamelCase names over
names that have abbreviations (CmlCs). However, we need not
enforce that.
I also prefer that code be well commented. A lot of open source
code has no comments and is very difficult to reuse.
_Christopher
On 6/16/16 6:49 AM, Erwin de Ley wrote:
Hi Jonah,
I have attached the exported prefs from the Java/Code
Style/Formatter preferences.
The main things :
- indentations are 2 spaces, no TABs
- longer lines (160 chars)
cheers
erwin
Op 16/06/2016 om 15:35 schreef Jonah Graham:
Hi Erwin,
Are there code formatting standards for Triq?
Thanks
Jonah
~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com
_______________________________________________
triquetrum-dev mailing list
triquetrum-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/triquetrum-dev
_______________________________________________
triquetrum-dev mailing list
triquetrum-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/triquetrum-dev
--
Christopher Brooks, PMP University of California
Academic Program Manager & Software Engineer US Mail: 337 Cory Hall
CHESS/iCyPhy/Ptolemy/TerraSwarm Berkeley, CA 94720-1774
cxh@xxxxxxxxxxxxxxxxx, 707.332.0670 (Office: 545Q Cory)
