Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
de:develop:guidelines [2013/03/11 19:41] – created valerius | de:develop:guidelines [2018/06/07 20:30] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 29: | Line 29: | ||
Each levels/part of the os should have a specific prefix that allows a developer to easily find what part of the os a header/ | Each levels/part of the os should have a specific prefix that allows a developer to easily find what part of the os a header/ | ||
- | #include < | + | |
+ | < | ||
and code shared by all commandline tools should include: | and code shared by all commandline tools should include: | ||
- | #include < | + | |
+ | < | ||
Try to create as few shared code headers as possible. Each “shared” directory should contain one (1) library (.lib) file (xxx_shared.lib) with all shared code and each “include” directory should contain one main header file including all other (xxx_shared.h). | Try to create as few shared code headers as possible. Each “shared” directory should contain one (1) library (.lib) file (xxx_shared.lib) with all shared code and each “include” directory should contain one main header file including all other (xxx_shared.h). | ||
Line 43: | Line 45: | ||
// Do NOT include os2.h, use osfree.h instead | // Do NOT include os2.h, use osfree.h instead | ||
- | #include < | + | |
+ | < | ||
// Include any needed normal C library | // Include any needed normal C library | ||
+ | |||
+ | < | ||
#include < | #include < | ||
#include < | #include < | ||
+ | </ | ||
// Include all shared code and shared code for command line tools | // Include all shared code and shared code for command line tools | ||
+ | |||
+ | < | ||
#include < | #include < | ||
#include < | #include < | ||
+ | </ | ||
==== Dokumentation ==== | ==== Dokumentation ==== | ||
Line 90: | Line 99: | ||
* Maintainers will often reply in response to your patch, pointing out things to fix up, etc. before a patch can be checked in. Please always follow the maintainer suggestions closely and respond by sending a new corrected patch. Please do not expect the maintainers to rework your changes, you want to be able to claim all the credit for your great patches! | * Maintainers will often reply in response to your patch, pointing out things to fix up, etc. before a patch can be checked in. Please always follow the maintainer suggestions closely and respond by sending a new corrected patch. Please do not expect the maintainers to rework your changes, you want to be able to claim all the credit for your great patches! | ||
- | + | ~~DISCUSSION~~ | |
- | === Discussion === | + | |