-
Determine coding conventions we will follow and reference them in the documentation. See also #3
-
-
Please, do not write like this:
``` c
for(blah) {
foo
bar
}
```
Write it like this:
``` c
for(blah)
{
foo;
bar;
}
```
However, if you have only one string enclosed (i. e. only `fo…
Lwmte updated
9 years ago
-
This is suggestion for refactoring: [Coding Conventions](https://wiki.qt.io/Coding_Conventions)
I pick up the check list of summary. read the original document for long details.
---
### C++ Feature
…
-
Compromise on these coding conventions: https://root.cern.ch/coding-conventions#Preferred_Coding_Style
-
@proin Do you have code conventions for GDL? If you don't have any conventions yet, it looks to me like [Android Code Style](http://source.android.com/source/code-style.html) is good for us. Google pr…
-
Spike Plan
==============
**Name**:
## Context:
Outline the reason and context for the spike.
Example: Team needs to use a database to store data for application developed
during this subjec…
-
We use python and we need a case for that. Its snake case for variables and title case for classes right?
-
As a contributor or moderator, consistency of styling simplifies package maintenance and cuts down on pull request review lines of code since editors can adhere to standardization.
The project sho…
-
We should standardise coding conventions, the things that are not covered by TSLint.
We use different conventions in different files and it is very inconsistent sometimes. It can be very confusing …