libirc_doc_faq.h   libirc_doc_faq.h 
skipping to change at line 14 skipping to change at line 14
* This library is free software; you can redistribute it and/or modify it * This library is free software; you can redistribute it and/or modify it
* under the terms of the GNU Lesser General Public License as published by * under the terms of the GNU Lesser General Public License as published by
* the Free Software Foundation; either version 2 of the License, or (at yo ur * the Free Software Foundation; either version 2 of the License, or (at yo ur
* option) any later version. * option) any later version.
* *
* This library is distributed in the hope that it will be useful, but WITH OUT * This library is distributed in the hope that it will be useful, but WITH OUT
* ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
* FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public * FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public
* License for more details. * License for more details.
* *
* $Id: libirc_doc_faq.h,v 1.4 2004/10/07 19:13:44 gyunaev Exp $ * $Id: libirc_doc_faq.h,v 1.6 2004/10/31 13:43:47 gyunaev Exp $
*/ */
/*! /*!
* \file libirc_doc_faq.h * \file libirc_doc_faq.h
* \author Georgy Yunaev * \author Georgy Yunaev
* \version 1.0 * \version 1.0
* \date 09.2004 * \date 09.2004
* \brief This file contains libircclient FAQ. * \brief This file contains libircclient FAQ.
*/ */
/*! \page pagefaq Frequently Asked Questions /*! \page pagefaq Frequently Asked Questions
\section faq FAQ \section faq FAQ
\subsection faq1 Why the IRC server generates all these event_numeric event s, and what they are? \subsection faq1 Why the IRC server generates all these event_numeric event s, and what is their meaning?
The IRC protocol itself is asynchronous and server-driven. The IRC protocol itself is asynchronous and server-driven.
For you, this means the following: For you, this means the following:
- For any IRC command, it is not possible to obtain an immediate response - For any IRC command, it is not possible to obtain an immediate response
whether the command succeed or not. Instead the server will send the whether the command succeed or not. Instead the server will send the
reply in a short (or long) period of time. reply in a short (or long) period of time.
- For some IRC command there is no 'success' response at all. For example, - For some IRC command there is no 'success' response at all. For example,
when you send a text message, IRC server will not send anything to confir m when you send a text message, IRC server will not send anything to confir m
that the message is already sent. that the message is already sent.
- You can send several commands to the IRC server, and then receive several - You can send several commands to the IRC server, and then receive several
skipping to change at line 119 skipping to change at line 119
their own CTCP codes. The built-in handler reacts on TIME, VERSION, PING an d their own CTCP codes. The built-in handler reacts on TIME, VERSION, PING an d
FINGER CTCP queries. If you need to react on other queries, you'll have to FINGER CTCP queries. If you need to react on other queries, you'll have to
write your own CTCP handler. See the source code of libirc_event_ctcp_inter nal write your own CTCP handler. See the source code of libirc_event_ctcp_inter nal
to get an idea how to write it. to get an idea how to write it.
\subsection faq5 Why don't I receive event_umode when I am made +o (a chann el operator)? \subsection faq5 Why don't I receive event_umode when I am made +o (a chann el operator)?
Because this is a channel mode, not a user mode. The user mode \c +o means that Because this is a channel mode, not a user mode. The user mode \c +o means that
this user is an IRC network operator, not just a channel operator. this user is an IRC network operator, not just a channel operator.
\subsection faq6 Why I get a LIBIRC_ERR_SOCKET error using static library u nder Win32? \subsection faq6 Why do I get a LIBIRC_ERR_SOCKET error while using static library under Win32?
Because if you use static library, you have to initialize winsock manually: Because if you use static library, you have to initialize Winsock manually:
\code \code
WORD wVersionRequested = MAKEWORD (1, 1); WORD wVersionRequested = MAKEWORD (1, 1);
WSADATA wsaData; WSADATA wsaData;
if ( WSAStartup (wVersionRequested, &wsaData) != 0 ) if ( WSAStartup (wVersionRequested, &wsaData) != 0 )
// report an error // report an error
// And now we can use libircclient // And now we can use libircclient
\endcode \endcode
 End of changes. 4 change blocks. 
4 lines changed or deleted 4 lines changed or added


 libirc_params.h   libirc_params.h 
skipping to change at line 14 skipping to change at line 14
* This library is free software; you can redistribute it and/or modify it * This library is free software; you can redistribute it and/or modify it
* under the terms of the GNU Lesser General Public License as published by * under the terms of the GNU Lesser General Public License as published by
* the Free Software Foundation; either version 2 of the License, or (at yo ur * the Free Software Foundation; either version 2 of the License, or (at yo ur
* option) any later version. * option) any later version.
* *
* This library is distributed in the hope that it will be useful, but WITH OUT * This library is distributed in the hope that it will be useful, but WITH OUT
* ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
* FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public * FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public
* License for more details. * License for more details.
* *
* $Id: libirc_params.h,v 1.6 2004/10/10 16:36:36 gyunaev Exp $ * $Id: libirc_params.h,v 1.9 2004/11/08 20:49:37 gyunaev Exp $
*/ */
#ifndef INCLUDE_IRC_PARAMS_H #ifndef INCLUDE_IRC_PARAMS_H
#define INCLUDE_IRC_PARAMS_H #define INCLUDE_IRC_PARAMS_H
#ifndef IN_INCLUDE_LIBIRC_H #ifndef IN_INCLUDE_LIBIRC_H
#error This file should not be included directly, include just libir cclient.h #error This file should not be included directly, include just libir cclient.h
#endif #endif
#define LIBIRC_VERSION_HIGH 0x0000 #define LIBIRC_VERSION_HIGH 0x0001
#define LIBIRC_VERSION_LOW 0x0007 #define LIBIRC_VERSION_LOW 0x0000
#define LIBIRC_BUFFER_SIZE 1024 #define LIBIRC_BUFFER_SIZE 1024
#define LIBIRC_DCC_BUFFER_SIZE 1024 #define LIBIRC_DCC_BUFFER_SIZE 1024
#define LIBIRC_STATE_INIT 0 #define LIBIRC_STATE_INIT 0
#define LIBIRC_STATE_LISTENING 1 #define LIBIRC_STATE_LISTENING 1
#define LIBIRC_STATE_CONNECTING 2 #define LIBIRC_STATE_CONNECTING 2
#define LIBIRC_STATE_CONNECTED 3 #define LIBIRC_STATE_CONNECTED 3
#define LIBIRC_STATE_DISCONNECTED 4 #define LIBIRC_STATE_DISCONNECTED 4
#define LIBIRC_STATE_CONFIRM_SIZE 5 // Used only by DCC send to confirm the amount of sent data #define LIBIRC_STATE_CONFIRM_SIZE 5 // Used only by DCC send to confirm the amount of sent data
 End of changes. 2 change blocks. 
3 lines changed or deleted 3 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/