sharpetronics/glade
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glade.git synced 2025-10-09 00:07:00 -04:00
Code Issues Projects Releases Wiki Activity

Add note about braces.

Browse Source
This commit is contained in:
Paolo Borelli 2003-11-07 15:30:37 +00:00
parent 1c953a06cf
commit e6462dfd37
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
HACKING
View File

@ -36,6 +36,23 @@ Coding Style
Code in Glade-3 should follow the GNOME Programming Guidelines Code in Glade-3 should follow the GNOME Programming Guidelines
(http://developer.gnome.org/doc/guides/programming-guidelines/), (http://developer.gnome.org/doc/guides/programming-guidelines/),
basically this means being consistent with the sorrounding code. basically this means being consistent with the sorrounding code.
The only exception is that we prefer having braces always on a new line
e.g.:
if (...)
{
...
}
Note however that a lot of the current codebase still uses the following
style:
if (...) {
...
}
Over time we'll migrate to the preferred form.
Naming conventions: Naming conventions:
- function names sholud be lowercase and prefixed with the - function names sholud be lowercase and prefixed with the
file name (or, if the function is static and the name too long, file name (or, if the function is static and the name too long,
@ -45,6 +62,7 @@ Naming conventions:
- variable names should be lowercase and be short but self explanatory; - variable names should be lowercase and be short but self explanatory;
if you need more than one word use an underscore, e.g: if you need more than one word use an underscore, e.g:
my_variable my_variable
Also try to order your functions so that prototypes are not needed. Also try to order your functions so that prototypes are not needed.