[GNUnet-SVN] [gnunet-texinfo] branch master updated: developer.texi: @section, @subsection, @subsubsection for chapter "introduction".

[gnunet]

This is an automated email from the git hooks/post-receive script.

ng0 pushed a commit to branch master
in repository gnunet-texinfo.

The following commit(s) were added to refs/heads/master by this push:
     new adcb89c  developer.texi: @section, @subsection, @subsubsection for 
chapter "introduction".
adcb89c is described below

commit adcb89c669f305e394ad564a745cc6200bc0b390
Author: ng0 <address@hidden>
AuthorDate: Fri Feb 17 16:58:08 2017 +0000

    developer.texi: @section, @subsection, @subsubsection for chapter
    "introduction".
---
 developer.texi | 39 +++++++++++++++++++++------------------
 1 file changed, 21 insertions(+), 18 deletions(-)

diff --git a/developer.texi b/developer.texi
index 224bc7f..3867eba 100644
--- a/developer.texi
+++ b/developer.texi
@@ -411,7 +411,7 @@ Current reports on test coverage are here.
 
 @c ***************************************************************************
 @node Project overview
address@hidden Project overview
address@hidden Project overview
 
 The GNUnet project consists at this point of several sub-projects. This section
 is supposed to give an initial overview about the various sub-projects. Note
@@ -463,7 +463,7 @@ that have a public website) which build on top of the 
GNUnet framework.
 
 @c ***************************************************************************
 @node Code overview
address@hidden Code overview
address@hidden Code overview
 
 This section gives a brief overview of the GNUnet source code. Specifically, we
 sketch the function of each of the subdirectories in the @code{gnunet/src/}
@@ -641,7 +641,7 @@ experimentation to evaluate transport and ats properties
 
 @c ***************************************************************************
 @node System Architecture
address@hidden System Architecture
address@hidden System Architecture
 
 GNUnet developers like legos. The blocks are indestructible, can be stacked
 together to construct complex buildings and it is generally easy to swap one
@@ -690,7 +690,7 @@ fail, but instead wait for the service process to be 
restarted by ARM.
 
 @c ***************************************************************************
 @node Subsystem stability
address@hidden Subsystem stability
address@hidden Subsystem stability
 
 This page documents the current stability of the various GNUnet subsystems.
 Stability here describes the expected degree of compatibility with future
@@ -782,17 +782,17 @@ This subsystem does not have an 
API/IPC-protocol/P2P-protocol
 
 @c ***************************************************************************
 @node Naming conventions and coding style guide
address@hidden Naming conventions and coding style guide
address@hidden Naming conventions and coding style guide
 
 Here you can find some rules to help you write code for GNUnet.
 
 @c ***************************************************************************
 @node Naming conventions
address@hidden Naming conventions
address@hidden Naming conventions
 
 @c ***************************************************************************
 @node include files
address@hidden include files
address@hidden include files
 
 @itemize @bullet
 @item _lib: library without need for a process
@@ -812,7 +812,7 @@ Here you can find some rules to help you write code for 
GNUnet.
 
 @c ***************************************************************************
 @node binaries
address@hidden binaries
address@hidden binaries
 
 @itemize @bullet
 @item gnunet-service-xxx: service process (has listen socket)
@@ -825,7 +825,7 @@ Here you can find some rules to help you write code for 
GNUnet.
 
 @c ***************************************************************************
 @node logging
address@hidden logging
address@hidden logging
 
 @itemize @bullet
 @item services and daemons use their directory name in GNUNET_log_setup (i.e.
@@ -846,7 +846,7 @@ GNUNET_log_from (kind, "example-api",__VA_ARGS__)
 
 @c ***************************************************************************
 @node configuration
address@hidden configuration
address@hidden configuration
 
 @itemize @bullet
 @item paths (that are substituted in all filenames) are in PATHS (have as few
@@ -857,7 +857,7 @@ as possible)
 
 @c ***************************************************************************
 @node exported symbols
address@hidden exported symbols
address@hidden exported symbols
 
 @itemize @bullet
 @item must start with "GNUNET_modulename_" and be defined in "modulename.c"
@@ -866,7 +866,7 @@ as possible)
 
 @c ***************************************************************************
 @node private (library-internal) symbols (including structs and macros)
address@hidden private (library-internal) symbols (including structs and macros)
address@hidden private (library-internal) symbols (including structs and macros)
 
 @itemize @bullet
 @item must NOT start with any prefix
@@ -877,7 +877,7 @@ src/modulename/ and NEVER be@ declared in src/include/.
 @end itemize
 
 @node testcases
address@hidden testcases
address@hidden testcases
 
 @itemize @bullet
 @item must be called "test_module-under-test_case-description.c"
@@ -885,8 +885,8 @@ src/modulename/ and NEVER be@ declared in src/include/.
 @end itemize
 
 @c ***************************************************************************
address@hidden performance tests
 @node performance tests
address@hidden performance tests
 
 @itemize @bullet
 @item must be called "perf_module-under-test_case-description.c"
@@ -895,8 +895,8 @@ src/modulename/ and NEVER be@ declared in src/include/.
 @end itemize
 
 @c ***************************************************************************
address@hidden src/ directories
 @node src/ directories
address@hidden src/ directories
 
 @itemize @bullet
 @item gnunet-NAME: end-user applications (i.e., gnunet-search, gnunet-arm)
@@ -911,18 +911,21 @@ libgnunet_plugin_transport_tcp)
 @end itemize
 
 @c ***************************************************************************
address@hidden Coding style
 @node Coding style
address@hidden Coding style
 
 @itemize @bullet
 @item GNU guidelines generally apply
 @item Indentation is done with spaces, two per level, no tabs
 @item C99 struct initialization is fine
 @item declare only one variable per line, so@
+
 @example
 int i; int j;
 @end example
+
 instead of
+
 @example
 int i,j;
 @end example
@@ -1065,7 +1068,7 @@ better to NOT have an empty line (this way, more code 
will fit on the screen).
 
 @c ***************************************************************************
 @node Build-system
address@hidden Build-system
address@hidden Build-system
 
 If you have code that is likely not to compile or build rules you might want to
 not trigger for most developers, use "if HAVE_EXPERIMENTAL" in your
@@ -1086,7 +1089,7 @@ If you want to obtain code coverage results, run 
configure with the@
 
 @c ***************************************************************************
 @node Developing extensions for GNUnet using the gnunet-ext template
address@hidden Developing extensions for GNUnet using the gnunet-ext template
address@hidden Developing extensions for GNUnet using the gnunet-ext template
 
 
 For developers who want to write extensions for GNUnet we provide the

-- 
To stop receiving notification emails like this one, please contact
address@hidden