Changes in / [1098:f38d77f9cfd3:1101:40b48a3997a2] in freeDiameter

Files:

• include/freeDiameter/libfdcore.h (modified) (2 diffs)
• include/freeDiameter/libfdproto.h (modified) (1 diff)
• libfdcore/cnxctx.c (modified) (1 diff)
• libfdcore/p_sr.c (modified) (1 diff)
• libfdproto/messages.c (modified) (1 diff)

include/freeDiameter/libfdcore.h

@@ -950 +950 @@
         
         HOOK_MESSAGE_FAILOVER,
-                /* Hook called when a message that was sent to a peer is being requeued, because e.g. the connection was teared down.
+                /* Hook called when a message that was sent to a peer is being requeued, because e.g. the connection was torn down.
                    In that case the message will go again through the routing process.
                  - {msg} points to the corresponding request message (the answer is discarded). Again, the objects may not have been dictionary resolved. If you
@@ -1019 +1019 @@
 
 
-/* Type if the {permsgdata}. It is up to each extension to define its own structure. This is opaque for the framework. */
+/* Type of the {permsgdata} pointer. It is up to each extension to define its own structure. This is opaque for the framework. */
 struct fd_hook_permsgdata;
 

include/freeDiameter/libfdproto.h

@@ -80 +80 @@
 #include <stdarg.h>
 
-#ifdef DEBUG
-#include <libgen.h>     /* for basename if --dbg_file is specified */
-#endif /* DEBUG */
+#include <libgen.h>     /* for basename */
 
 #ifdef SWIG

libfdcore/cnxctx.c

@@ -1758 +1758 @@
         
                 default:
-                        TRACE_DEBUG(INFO, "Unknwon protocol: %d", conn->cc_proto);
+                        TRACE_DEBUG(INFO, "Unknown protocol: %d", conn->cc_proto);
                         ASSERT(0);
                         return ENOTSUP; /* or EINVAL... */

libfdcore/p_sr.c

@@ -196 +196 @@
         } while (1);
 error:  
-        ; /* pthread_cleanup_pop sometimes expands as "} ..." and the label beofre this cause some compilers to complain... */
+        ; /* pthread_cleanup_pop sometimes expands as "} ..." and the label before this cause some compilers to complain... */
         pthread_cleanup_pop( 1 );
         ASSERT(0); /* we have encountered a problem, maybe time to signal the framework to terminate? */

libfdproto/messages.c

@@ -1255 +1255 @@
                 return anscb ? EINVAL : 0; /* we associate with requests only */
         
-        CHECK_PARAMS( (anscb == NULL)    || (msg->msg_cb.anscb == NULL) ); /* We are not overwritting a cb */
-        CHECK_PARAMS( (expirecb == NULL) || (msg->msg_cb.expirecb == NULL) ); /* We are not overwritting a cb */
+        CHECK_PARAMS( (anscb == NULL)    || (msg->msg_cb.anscb == NULL) ); /* We are not overwriting a cb */
+        CHECK_PARAMS( (expirecb == NULL) || (msg->msg_cb.expirecb == NULL) ); /* We are not overwriting a cb */
         
         /* Associate callback and data with the message, if any */