Changes between Version 8 and Version 9 of StudentTips

Timestamp:

2011-03-01T17:30:58Z (13 years ago)

Author:

Jiri Svoboda

Comment:

Revert change (duplicate text)

StudentTips

@@ -17 +17 @@
   * Stick to the [http://www.helenos.org/cstyle HelenOS coding style].
   * Adhere to good coding practices, such as adequate commenting, avoiding dense code, using horizontal spacing as visual delimiter and keeping the block nesting level under control.
-  * Respect copyright. Including third-party code (such as headers) is discouraged. When absolutely necessary and you do it, you '''must''' include proper copyright notices and attributions as required by the third-party license.
   * Self-contained code is good, but avoid poorly integrated code. Poorly integrated code is pointlessly concentrated in one subdirectory of the source tree. For example, putting new generic ADT's and IPC primitives under the networking directory is a sign of poorly integrated code.
   * As with the text of your thesis, similar citation rules should apply in your code. When using third party code, always give credit where the credit is due, always follow the license of the third party code. It would be kind of embarrassing to discover portions of e.g. Linux header file in code which you advertise as yours.