[Pidgin] CHowTo/DebugAPIHowTo modified

Pidgin trac at pidgin.im
Sun Apr 15 03:15:09 EDT 2012


Changed page "CHowTo/DebugAPIHowTo" by QuLogic from 70.53.229.129*
Page URL: <http://developer.pidgin.im/wiki/CHowTo/DebugAPIHowTo>
Diff URL: <http://developer.pidgin.im/wiki/CHowTo/DebugAPIHowTo?action=diff&version=4>
Revision 4
Comment: Fix doxygen links

-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: CHowTo/DebugAPIHowTo
=========================================================================
--- CHowTo/DebugAPIHowTo (version: 3)
+++ CHowTo/DebugAPIHowTo (version: 4)
@@ -9,12 +9,12 @@
 Libpurple provides a generic `purple_debug()` function for use in printing messages, but at the same time provides convenience functions for each debugging level.  This How-To will focus on using the convenience functions for the convenience and simplicity they provide, as well as for their attractiveness to the lazy typist.
 
 == Debug Levels ==
-The documentation for the [/doxygen/dev/html/debug_8h.html debug.h] header file shows an enumeration listing each of the 6 debug levels defined.  Only the last five are typically used when writing debug messages, leaving `PURPLE_DEBUG_ALL` primarily for the UI's use.
+The documentation for the [/doxygen/dev2.x.y/html/debug_8h.html debug.h] header file shows an enumeration listing each of the 6 debug levels defined.  Only the last five are typically used when writing debug messages, leaving `PURPLE_DEBUG_ALL` primarily for the UI's use.
 
-The other debugging levels are fairly straightforward, and I'll leave it to you to read the [/doxygen/dev/html/debug_8h.html#e4789d7a365e1d70da6f232248a08259 enum's documentation] for the brief descriptions.  For the most part we're going to want to use `PURPLE_DEBUG_MISC` and `PURPLE_DEBUG_INFO` for plugin messages, but there are obviously situations in which we'll need other levels.
+The other debugging levels are fairly straightforward, and I'll leave it to you to read the [/doxygen/dev2.x.y/html/debug_8h.html#e4789d7a365e1d70da6f232248a08259 enum's documentation] for the brief descriptions.  For the most part we're going to want to use `PURPLE_DEBUG_MISC` and `PURPLE_DEBUG_INFO` for plugin messages, but there are obviously situations in which we'll need other levels.
 
 == Using the Debug Functions ==
-If you browse the [/doxygen/dev/html/debug_8h.html debug.h] doxygen documentation further, you will see that all of the debug functions provided show a `...` for their final parameter.  This means that the function is a variadic function, which can take a variable number of parameters.  These functions are defined as such because they behave like the standard library's `printf()` function in many ways.  You will see the evidence of this once we show the actual source of the plugin.
+If you browse the [/doxygen/dev2.x.y/html/debug_8h.html debug.h] doxygen documentation further, you will see that all of the debug functions provided show a `...` for their final parameter.  This means that the function is a variadic function, which can take a variable number of parameters.  These functions are defined as such because they behave like the standard library's `printf()` function in many ways.  You will see the evidence of this once we show the actual source of the plugin.
 
 You will also notice that the functions take a category parameter.  The category makes it easy to tell what generated each specific debug message when reading the debug log.  You can use pretty much anything you want here, but for the purposes of demonstration, we're going to stick with the plugin ID for the category.  The recommended best practice is to use the plugin's ID or static name.
 

-------8<------8<------8<------8<------8<------8<------8<------8<--------

* The IP shown here might not mean anything if the user or the server is
behind a proxy.

--
Pidgin <http://pidgin.im>
Pidgin

This is an automated message. Someone at http://pidgin.im added your email
address to be notified of changes on CHowTo/DebugAPIHowTo. If it was not you, please
report to .


More information about the Wikiedit mailing list