kreyren/Zernit
1
0
Fork 0
Code Issues 129 Pull Requests Releases Activity

REQUEST: Implement standard for C lang #118

New Issue
Open
opened 2020-05-09 09:35:05 +02:00 by Kreyren · 0 comments
Kreyren commented 2020-05-09 09:35:05 +02:00 (Migrated from github.com)
Copy Link
Copy Source

Describe the feature

C lang is notirious for terrible standard that is kept behind a paywall and with open-std that conflicts with the official release so most of the C developers are using their own standard which will conflict on zernit. We need to implement out own community maintained standard to avoid C lang's incompetence when it comes to standardization.

Expected behavior

  • Code style
  • Memory leak prevention
  • Peer-review requirement
  • Copyright notice requirement
  • Tracking for used versions
  • Always written to be cross-platform - The code is expected to account for cross-platform, developer is not expected to write the code for all platforms by themselfs
  • Abstracting - Mandatory! To avoid futile logic and terrible implementations
  • Linting requirements - At minimum it should have a comment informing about linting used so that we know that the code is reliable from linting point of view
  • Proper copyright notice standardization
  • Compatibility for GCC and Clang - Generally if the code doesn't built on either of those it indicates a possible code quality issue and/or memory leak.
### Describe the feature <!-- Give us a **short** summary of your proposed feature --> C lang is notirious for terrible standard that is kept behind a paywall and with open-std that conflicts with the official release so most of the C developers are using their own standard which will conflict on zernit. We need to implement out own community maintained standard to avoid C lang's incompetence when it comes to standardization. ### Expected behavior <!-- What do you expect to happend instead of current behavior? --> - Code style - Memory leak prevention - Peer-review requirement - Copyright notice requirement - Tracking for used versions - Always written to be cross-platform - The code is expected to account for cross-platform, developer is not expected to write the code for all platforms by themselfs - Abstracting - Mandatory! To avoid futile logic and terrible implementations - Linting requirements - At minimum it should have a comment informing about linting used so that we know that the code is reliable from linting point of view - Proper copyright notice standardization - Compatibility for GCC and Clang - Generally if the code doesn't built on either of those it indicates a possible code quality issue and/or memory leak.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
kreyren (Jacob Hrbek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kreyren/Zernit#118
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?