[
https://issues.apache.org/jira/browse/COR-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333505#comment-14333505
]
Peter Kelly commented on COR-46:
--------------------------------
I think it's probably worth having a discussion about coding style, if there's
desire to change it. I don't particularly care what style we follow, but if we
change it, then I think we should aim for consistency, so that all code
conforms to the same style (and if we do change, then change everything).
The style I followed when writing all the original code is as follows:
- Line length: 100
- Indentation: Four spaces (no tabs)
- Curly brackets: on separate line for function definitions, same line for
everything else (structs, if statements, while loops)
- Formal parameters (function definitions): spaces after commas
- Actual parameters (function calls): no spaces after commas
I'm not tied to this style - it's what I typically work in but I don't claim it
to be the "one true style".
Thoughts?
(and Gabriella: Please don't be discouraged by this - I'm very glad to see you
contributing - I just want to ensure we retain consistency in coding style
throughout the codebase).
> set line length to 70 char, added spaces between variables in parameter lists
> -----------------------------------------------------------------------------
>
> Key: COR-46
> URL: https://issues.apache.org/jira/browse/COR-46
> Project: Corinthia
> Issue Type: Improvement
> Components: DocFormats - API
> Affects Versions: 0.5
> Reporter: Gabriela Gibson
> Priority: Minor
> Attachments: operations.patch
>
>
> File: /DocFormats/api/src/Operations.c
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
