Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Kea
Kea
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 427
    • Issues 427
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 69
    • Merge Requests 69
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • ISC Open Source Projects
  • KeaKea
  • Wiki
    • Processes
  • coding guidelines

coding guidelines · Changes

Page history
Banned GNU make authored May 24, 2020 by Francis Dupont's avatar Francis Dupont
Hide whitespace changes
Inline Side-by-side
Showing with 5 additions and 1 deletion
+5 -1
  • Processes/coding-guidelines.md Processes/coding-guidelines.md +5 -1
  • No files found.
Processes/coding-guidelines.md
View page @ cf3d5c02
......@@ -29,7 +29,7 @@ Dead code is bad; it suffers from code rot, and it looks unclean. There are some
Any dead code (both files that are unused and blocks of commented-out code) should in principle be removed. If there is a very good reason to keep it around for a while, it must be accompanied by a comment explaining why it is still there, and when it will be removed or enabled again. This comment should point to a ticket so that we do not forget about it.
# Python Style
We don't use python code anymore. If you found any leftovers, feel free to remove them.
We don't use python code anymore in the core code. If you found any leftovers, feel free to remove them.
# C++ Style
......@@ -571,6 +571,10 @@ Names of tests should be similar to classes and method names for that language.
# Makefile.am Guidelines
## Make portability
Makefiles must never depend on a particular make, for instance the `$(<function> ...)` construct of GNU make for shell, foreach, wildcard, etc, are forbidden.
## Subdirectories
If there is are one or more subdirectories, the first line in the file
......
Clone repository
  • Home
  • Hooks available
  • Processes
    • coding guidelines
    • gitlab howto
    • release process
    • smaller edits on gitlab
  • Release Notes
  • Simplified Flow Diagram
  • community developed tools
  • designs
    • Backend Assisted Lease Selection design
    • Basic LeaseQuery Design
    • Design documents
    • HA connection with MT support
    • HA split brain issues
    • Run external script hook
View All Pages