gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[gnunet-texinfo] branch master updated (dcba501 -> 5a98ad8)


From: gnunet
Subject: [gnunet-texinfo] branch master updated (dcba501 -> 5a98ad8)
Date: Thu, 14 Nov 2019 11:48:36 +0100

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

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

    from dcba501  attempting to give ref manual reasonable structure
     new d933a7d  fix indent
     new dfd491c  Fix typo in developer.texi (though -> through)
     new 5a98ad8  final commit, makefile.

The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 Makefile       |  2 +-
 developer.texi | 30 +++++++++++++++++++++---------
 2 files changed, 22 insertions(+), 10 deletions(-)

diff --git a/Makefile b/Makefile
index 17d4465..5b56ebf 100644
--- a/Makefile
+++ b/Makefile
@@ -11,4 +11,4 @@ all:  pdf html
 
 .PHONY: clean
 clean:
-       rm *.aux *.log *.toc *.pdf *.cp *.cps *.html
+       rm *.aux *.log *.toc *.pdf *.cp *.cps *.html *.info
diff --git a/developer.texi b/developer.texi
index 939455e..ce6b160 100644
--- a/developer.texi
+++ b/developer.texi
@@ -764,9 +764,15 @@ is used if the method for advancing in the loop is not a 
straightforward
 increment operation. In particular, we use:@
 
 @example
-next = head; while (NULL != (pos = next)) @{ next = pos->next; if (!
-should_free (pos)) continue; GNUNET_CONTAINER_DLL_remove (head, tail, pos);
-GNUNET_free (pos); @}
+next = head;
+while (NULL != (pos = next))
+@{
+  next = pos->next;
+  if (! should_free (pos))
+    continue;
+  GNUNET_CONTAINER_DLL_remove (head, tail, pos);
+  GNUNET_free (pos);
+@}
 @end example
 
 
@@ -776,8 +782,11 @@ simple @code{for} paradigm of @code{for(INIT;TEST;INC)}). 
However, for loops
 that do follow the simple @code{for} paradigm we do use @code{for}, even if it
 involves linked lists:
 @example
-/* simple iteration over a linked list */ for
-(pos = head; NULL != pos; pos = pos->next) @{ use (pos); @}
+/* simple iteration over a linked list */
+for (pos = head; NULL != pos; pos = pos->next)
+@{
+   use (pos);
+@}
 @end example
 
 
@@ -801,14 +810,17 @@ using deeply nested @code{if} statements. However, except 
for addition and
 multiplication, all operators should use parens. This is fine:@
 
 @example
-if ( (1 == foo) || ((0 == bar) && (x != y)) ) return x;
+if ( (1 == foo) || ((0 == bar) && (x != y)) )
+  return x;
 @end example
 
 
 However, this is not:
 @example
-if (1 == foo) return x; if (0 == bar && x != y)
-return x;
+if (1 == foo)
+  return x;
+if (0 == bar && x != y)
+  return x;
 @end example
 
 
@@ -1171,7 +1183,7 @@ port conflict on that host.
 
 The testbed service (controller) is different from the other GNUnet services in
 that it is not started by ARM and is not supposed to be run as a daemon. It is
-started by the testbed API though a testbed helper. In a typical scenario
+started by the testbed API through a testbed helper. In a typical scenario
 involving multiple hosts, a controller is started on each host. Controllers
 take up the actual task of creating peers, starting and stopping them on the
 hosts they run.

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]