diff options
| author | Sébastien Wilmet <swilmet@gnome.org> | 2017-09-17 15:01:34 +0200 |
|---|---|---|
| committer | Sébastien Wilmet <swilmet@gnome.org> | 2017-09-17 15:01:34 +0200 |
| commit | 4077c221f92fcdfec22f48793a2392463e41da4d (patch) | |
| tree | 9a340862e7e1a6690b4015026fb24ba30ad5eb73 /HACKING | |
| parent | 3d62448fc288fcd029ec714aed6ceeae0dd2a29c (diff) | |
| download | gtksourceview-4077c221f92fcdfec22f48793a2392463e41da4d.tar.gz | |
Hacking file: move some links at the end of relevant sections
Diffstat (limited to 'HACKING')
| -rw-r--r-- | HACKING | 16 |
1 files changed, 10 insertions, 6 deletions
@@ -55,6 +55,11 @@ conventions, but for new code it is better to follow them, for consistency. - As a general rule of thumb, follow the same coding style as the surrounding code. +See also: +https://developer.gnome.org/programming-guidelines/stable/ +https://wiki.gnome.org/Projects/GTK%2B/BestPractices +https://wiki.gnome.org/Projects/GLib/CompilerRequirements + Programming best-practices -------------------------- @@ -122,14 +127,13 @@ Here are some general advices: writing hacks or heuristics to work around a bug or a lack of feature in an underlying library. -See also --------- +See also: +https://blogs.gnome.org/swilmet/2012/08/01/about-code-quality-and-maintainability/ + +Other links +----------- -https://developer.gnome.org/programming-guidelines/stable/ -https://wiki.gnome.org/Projects/GTK%2B/BestPractices -https://wiki.gnome.org/Projects/GLib/CompilerRequirements http://ometer.com/hacking.html -https://blogs.gnome.org/swilmet/2012/08/01/about-code-quality-and-maintainability/ For a shared library: |