Update Home

Booklordofthedings 2025-03-07 10:57:15 +01:00
parent 82bcdbfd5b
commit 62f64b60c2

@ -19,8 +19,11 @@ Its formatted as a list of rules to make it somewhat easier to read and understa
- Iterators for numerical reasons should use `i`, `j`, `k`, `ii`
*Two of the same character is fine since its visibly different, but further repetition should be avoided*
- Iterators in foreach type scenarios should use the singular version of the thing they are ( `line`, `entry`, `key`)
- Other common names: `toReturn/res/result`
- Public members, properties and functions should use `PascalCase`
- Private members or functions should use `camelCase` and prepend a `_` infront of them
- Local variables use `camelCase`
- Otherwise names should indicate what a variable is used for or what it contains
- Otherwise names should indicate what a variable is used for or what it contains
- `val/value` as a name should be avoided unless used in a generic setting, or in small scopes
- Namespaces should use `PascalCase`
- Namespaces should be used instead of prefixes
*Prefixes may only be used if the names of objects are very generic or overlap with corlib types*