From 9c8b44176b47d2186c88743dc1f68023c26d780b Mon Sep 17 00:00:00 2001 From: brain Date: Mon, 4 Apr 2005 18:13:55 +0000 Subject: Added new documentation for ELine class and OnUserPostNick method git-svn-id: http://svn.inspircd.org/repository/trunk/inspircd@977 e03df62e-2008-0410-955e-edbf42e46eb7 --- docs/module-doc/classServer.html | 414 +++++++++++++++++++-------------------- 1 file changed, 207 insertions(+), 207 deletions(-) (limited to 'docs/module-doc/classServer.html') diff --git a/docs/module-doc/classServer.html b/docs/module-doc/classServer.html index f99f9bf56..23971e233 100644 --- a/docs/module-doc/classServer.html +++ b/docs/module-doc/classServer.html @@ -131,7 +131,7 @@ All modules should instantiate at least one copy of this class, and use its memb

-Definition at line 365 of file modules.h.

Constructor & Destructor Documentation

+Definition at line 371 of file modules.h.

Constructor & Destructor Documentation

@@ -161,10 +161,10 @@ Default constructor.

Creates a Server object.

-Definition at line 336 of file modules.cpp. +Definition at line 337 of file modules.cpp.

-

00337 {
-00338 }
+
00338 {
+00339 }
@@ -197,10 +197,10 @@ Default destructor.

Destroys a Server object.

-Definition at line 340 of file modules.cpp. +Definition at line 341 of file modules.cpp.

-

00341 {
-00342 }
+
00342 {
+00343 }
 
    
   
 
@@ -258,13 +258,13 @@ This allows modules to add extra commands into the command table. You must place
 typedef void (handlerfunc) (char**, int, userrec*); ... void handle_kill(char **parameters, int pcnt, userrec *user)

 When the command is typed, the parameters will be placed into the parameters array (similar to argv) and the parameter count will be placed into pcnt (similar to argv). There will never be any less parameters than the 'minparams' value you specified when creating the command. The *user parameter is the class of the user which caused the command to trigger, who will always have the flag you specified in 'flags' when creating the initial command. For example to create an oper only command create the commands with flags='o'.
 

-Definition at line 417 of file modules.cpp.
+Definition at line 418 of file modules.cpp.
 

 References createcommand().
 

-
00418 {
-00419         createcommand(cmd,f,flags,minparams);
-00420 }
+
00419 {
+00420         createcommand(cmd,f,flags,minparams);
+00421 }
 
    
   
 
@@ -303,16 +303,16 @@ This call is used to implement modes like +q and +a. The characteristics of thes
 (4) The mode and its parameter are NOT stored in the channels modes structure

 It is down to the module handling the mode to maintain state and determine what 'items' (e.g. users, or a banlist) have the mode set on them, and process the modes at the correct times, e.g. during access checks on channels, etc. When the extended mode is triggered the OnExtendedMode method will be triggered as above. Note that the target you are given will be a channel, if for example your mode is set 'on a user' (in for example +a) you must use Server::Find to locate the user the mode is operating on. Your mode handler may return 1 to handle the mode AND tell the core to display the mode change, e.g. '+aaa one two three' in the case of the mode for 'two', or it may return -1 to 'eat' the mode change, so the above example would become '+aa one three' after processing.
 

-Definition at line 562 of file modules.cpp.
+Definition at line 563 of file modules.cpp.
 

 References DoAddExtendedMode(), ModeMakeList(), and MT_CHANNEL.
 

-
00563 {
-00564         bool res = DoAddExtendedMode(modechar,MT_CHANNEL,false,1,1);
-00565         if (res)
-00566                 ModeMakeList(modechar);
-00567         return res;
-00568 }
+
00564 {
+00565         bool res = DoAddExtendedMode(modechar,MT_CHANNEL,false,1,1);
+00566         if (res)
+00567                 ModeMakeList(modechar);
+00568         return res;
+00569 }
 
    
   
 
@@ -373,28 +373,28 @@ Adds an extended mode letter which is parsed by a module.
 

 This allows modules to add extra mode letters, e.g. +x for hostcloak. the "type" parameter is either MT_CHANNEL, MT_CLIENT, or MT_SERVER, to indicate wether the mode is a channel mode, a client mode, or a server mode. requires_oper is used with MT_CLIENT type modes only to indicate the mode can only be set or unset by an oper. If this is used for MT_CHANNEL type modes it is ignored. params_when_on is the number of modes to expect when the mode is turned on (for type MT_CHANNEL only), e.g. with mode +k, this would have a value of 1. the params_when_off value has a similar value to params_when_on, except it indicates the number of parameters to expect when the mode is disabled. Modes which act in a similar way to channel mode +l (e.g. require a parameter to enable, but not to disable) should use this parameter. The function returns false if the mode is unavailable, and will not attempt to allocate another character, as this will confuse users. This also means that as only one module can claim a specific mode character, the core does not need to keep track of which modules own which modes, which speeds up operation of the server. In this version, a mode can have at most one parameter, attempting to use more parameters will have undefined effects.
 

-Definition at line 542 of file modules.cpp.
+Definition at line 543 of file modules.cpp.
 

 References DEBUG, DoAddExtendedMode(), MT_CLIENT, and MT_SERVER.
 

-
00543 {
-00544         if (type == MT_SERVER)
-00545         {
-00546                 log(DEBUG,"*** API ERROR *** Modes of type MT_SERVER are reserved for future expansion");
-00547                 return false;
-00548         }
-00549         if (((params_when_on>0) || (params_when_off>0)) && (type == MT_CLIENT))
-00550         {
-00551                 log(DEBUG,"*** API ERROR *** Parameters on MT_CLIENT modes are not supported");
-00552                 return false;
-00553         }
-00554         if ((params_when_on>1) || (params_when_off>1))
-00555         {
-00556                 log(DEBUG,"*** API ERROR *** More than one parameter for an MT_CHANNEL mode is not yet supported");
-00557                 return false;
-00558         }
-00559         return DoAddExtendedMode(modechar,type,requires_oper,params_when_on,params_when_off);
-00560 }
+
00544 {
+00545         if (type == MT_SERVER)
+00546         {
+00547                 log(DEBUG,"*** API ERROR *** Modes of type MT_SERVER are reserved for future expansion");
+00548                 return false;
+00549         }
+00550         if (((params_when_on>0) || (params_when_off>0)) && (type == MT_CLIENT))
+00551         {
+00552                 log(DEBUG,"*** API ERROR *** Parameters on MT_CLIENT modes are not supported");
+00553                 return false;
+00554         }
+00555         if ((params_when_on>1) || (params_when_off>1))
+00556         {
+00557                 log(DEBUG,"*** API ERROR *** More than one parameter for an MT_CHANNEL mode is not yet supported");
+00558                 return false;
+00559         }
+00560         return DoAddExtendedMode(modechar,type,requires_oper,params_when_on,params_when_off);
+00561 }
 
    
   
 
@@ -450,11 +450,11 @@ Calls the handler for a command, either implemented by the core or by another mo
 You can use this function to trigger other commands in the ircd, such as PRIVMSG, JOIN, KICK etc, or even as a method of callback. By defining command names that are untypeable for users on irc (e.g. those which contain a  or 

 ) you may use them as callback identifiers. The first parameter to this method is the name of the command handler you wish to call, e.g. PRIVMSG. This will be a command handler previously registered by the core or wih AddCommand(). The second parameter is an array of parameters, and the third parameter is a count of parameters in the array. If you do not pass enough parameters to meet the minimum needed by the handler, the functiom will silently ignore it. The final parameter is the user executing the command handler, used for privilage checks, etc.
 

-Definition at line 407 of file modules.cpp.
+Definition at line 408 of file modules.cpp.
 

-
00408 {
-00409         call_handler(commandname.c_str(),parameters,pcnt,user);
-00410 }
+
00409 {
+00410         call_handler(commandname.c_str(),parameters,pcnt,user);
+00411 }
 
    
   
 
@@ -497,13 +497,13 @@ Change GECOS (fullname) of a user.
 

 You should always call this method to change a user's GECOS rather than writing directly to the fullname member of userrec, as any change applied via this method will be propogated to any linked servers.
 

-Definition at line 495 of file modules.cpp.
+Definition at line 496 of file modules.cpp.
 

 References ChangeName().
 

-
00496 {
-00497         ChangeName(user,gecos.c_str());
-00498 }
+
00497 {
+00498         ChangeName(user,gecos.c_str());
+00499 }
 
    
   
 
@@ -546,13 +546,13 @@ Change displayed hostname of a user.
 

 You should always call this method to change a user's host rather than writing directly to the dhost member of userrec, as any change applied via this method will be propogated to any linked servers.
 

-Definition at line 490 of file modules.cpp.
+Definition at line 491 of file modules.cpp.
 

 References ChangeDisplayedHost().
 

-
00491 {
-00492         ChangeDisplayedHost(user,host.c_str());
-00493 }
+
00492 {
+00493         ChangeDisplayedHost(user,host.c_str());
+00494 }
 
    
   
 
@@ -595,11 +595,11 @@ Forces a user nickchange.
 

 This command works similarly to SVSNICK, and can be used to implement Q-lines etc. If you specify an invalid nickname, the nick change will be dropped and the target user will receive the error numeric for it.
 

-Definition at line 391 of file modules.cpp.
+Definition at line 392 of file modules.cpp.
 

-
00392 {
-00393         force_nickchange(user,nickname.c_str());
-00394 }
+
00393 {
+00394         force_nickchange(user,nickname.c_str());
+00395 }
 
    
   
 
@@ -642,13 +642,13 @@ Attempts to look up a user's privilages on a channel.
 

 This function will return a string containing either @, , +, or an empty string, representing the user's privilages upon the channel you specify.
 

-Definition at line 515 of file modules.cpp.
+Definition at line 516 of file modules.cpp.
 

 References cmode().
 

-
00516 {
-00517         return cmode(User,Chan);
-00518 }
+
00517 {
+00518         return cmode(User,Chan);
+00519 }
 
    
   
 
@@ -691,13 +691,13 @@ Returns true if two users share a common channel.
 

 This method is used internally by the NICK and QUIT commands, and the Server::SendCommon method.
 

-Definition at line 468 of file modules.cpp.
+Definition at line 469 of file modules.cpp.
 

 References common_channels().
 

-
00469 {
-00470         return (common_channels(u1,u2) != 0);
-00471 }
+
00470 {
+00471         return (common_channels(u1,u2) != 0);
+00472 }
 
    
   
 
@@ -731,11 +731,11 @@ Returns a count of the number of users on a channel.
 

 This will NEVER be 0, as if the chanrec exists, it will have at least one user in the channel.
 

-Definition at line 570 of file modules.cpp.
+Definition at line 571 of file modules.cpp.
 

-
00571 {
-00572         return usercount(c);
-00573 }
+
00572 {
+00573         return usercount(c);
+00574 }
 
    
   
 
@@ -769,11 +769,11 @@ Attempts to look up a channel and return a pointer to it.
 

 This function will return NULL if the channel does not exist.
 

-Definition at line 510 of file modules.cpp.
+Definition at line 511 of file modules.cpp.
 

-
00511 {
-00512         return FindChan(channel.c_str());
-00513 }
+
00512 {
+00513         return FindChan(channel.c_str());
+00514 }
 
    
   
 
@@ -807,11 +807,11 @@ Attempts to look up a nick and return a pointer to it.
 

 This function will return NULL if the nick does not exist.
 

-Definition at line 505 of file modules.cpp.
+Definition at line 506 of file modules.cpp.
 

-
00506 {
-00507         return Find(nick);
-00508 }
+
00507 {
+00508         return Find(nick);
+00509 }
 
    
   
 
@@ -844,11 +844,11 @@ Returns the information of the server as returned by the /ADMIN command.
 

 See the Admin class for further information of the return value. The members Admin::Nick, Admin::Email and Admin::Name contain the information for the server where the module is loaded.
 

-Definition at line 535 of file modules.cpp.
+Definition at line 536 of file modules.cpp.
 

-
00536 {
-00537         return Admin(getadminname(),getadminemail(),getadminnick());
-00538 }
+
00537 {
+00538         return Admin(getadminname(),getadminemail(),getadminnick());
+00539 }
 
    
   
 
@@ -881,11 +881,11 @@ Returns the network name, global to all linked servers.
 

 
 

-Definition at line 530 of file modules.cpp.
+Definition at line 531 of file modules.cpp.
 

-
00531 {
-00532         return getnetworkname();
-00533 }
+
00532 {
+00533         return getnetworkname();
+00534 }
 
    
   
 
@@ -918,11 +918,11 @@ Returns the server name of the server where the module is loaded.
 

 
 

-Definition at line 525 of file modules.cpp.
+Definition at line 526 of file modules.cpp.
 

-
00526 {
-00527         return getservername();
-00528 }
+
00527 {
+00528         return getservername();
+00529 }
 
    
   
 
@@ -956,28 +956,28 @@ Fetches the userlist of a channel.
 

 This function must be here and not a member of userrec or chanrec due to include constraints.
 

-Definition at line 372 of file modules.cpp.
+Definition at line 373 of file modules.cpp.
 

 References chanuserlist, clientlist, has_channel(), and isnick().
 

-
00373 {
-00374         chanuserlist userl;
-00375         userl.clear();
-00376         for (user_hash::const_iterator i = clientlist.begin(); i != clientlist.end(); i++)
-00377         {
-00378                 if (i->second)
-00379                 {
-00380                         if (has_channel(i->second,chan))
-00381                         {
-00382                                 if (isnick(i->second->nick))
-00383                                 {
-00384                                         userl.push_back(i->second);
-00385                                 }
-00386                         }
-00387                 }
-00388         }
-00389         return userl;
-00390 }
+
00374 {
+00375         chanuserlist userl;
+00376         userl.clear();
+00377         for (user_hash::const_iterator i = clientlist.begin(); i != clientlist.end(); i++)
+00378         {
+00379                 if (i->second)
+00380                 {
+00381                         if (has_channel(i->second,chan))
+00382                         {
+00383                                 if (isnick(i->second->nick))
+00384                                 {
+00385                                         userl.push_back(i->second);
+00386                                 }
+00387                         }
+00388                 }
+00389         }
+00390         return userl;
+00391 }
 
    
   
 
@@ -1011,13 +1011,13 @@ Returns true if a nick is valid.
 

 Nicks for unregistered connections will return false.
 

-Definition at line 500 of file modules.cpp.
+Definition at line 501 of file modules.cpp.
 

 References isnick().
 

-
00501 {
-00502         return (isnick(nick.c_str()) != 0);
-00503 }
+
00502 {
+00503         return (isnick(nick.c_str()) != 0);
+00504 }
 
    
   
 
@@ -1060,13 +1060,13 @@ Checks if a user is on a channel.
 

 This function will return true or false to indicate if user 'User' is on channel 'Chan'.
 

-Definition at line 520 of file modules.cpp.
+Definition at line 521 of file modules.cpp.
 

 References has_channel().
 

-
00521 {
-00522         return has_channel(User,Chan);
-00523 }
+
00522 {
+00523         return has_channel(User,Chan);
+00524 }
 
    
   
 
@@ -1100,13 +1100,13 @@ Returns true if the servername you give is ulined.
 

 ULined servers have extra privilages. They are allowed to change nicknames on remote servers, change modes of clients which are on remote servers and set modes of channels where there are no channel operators for that channel on the ulined server, amongst other things. Ulined server data is also broadcast across the mesh at all times as opposed to selectively messaged in the case of normal servers, as many ulined server types (such as services) do not support meshed links and must operate in this manner.
 

-Definition at line 402 of file modules.cpp.
+Definition at line 403 of file modules.cpp.
 

-References is_uline().
+References is_uline().
 

-
00403 {
-00404         return is_uline(server.c_str());
-00405 }
+
00404 {
+00405         return is_uline(server.c_str());
+00406 }
 
    
   
 
@@ -1155,11 +1155,11 @@ Forces a user to join a channel.
 

 This is similar to svsjoin and can be used to implement redirection, etc. On success, the return value is a valid pointer to a chanrec* of the channel the user was joined to. On failure, the result is NULL.
 

-Definition at line 362 of file modules.cpp.
+Definition at line 363 of file modules.cpp.
 

-
00363 {
-00364         return add_channel(user,cname.c_str(),key.c_str(),true);
-00365 }
+
00364 {
+00365         return add_channel(user,cname.c_str(),key.c_str(),true);
+00366 }
 
    
   
 
@@ -1202,11 +1202,11 @@ Writes a log string.
 

 This method writes a line of text to the log. If the level given is lower than the level given in the configuration, this command has no effect.
 

-Definition at line 412 of file modules.cpp.
+Definition at line 413 of file modules.cpp.
 

-
00413 {
-00414         log(level,"%s",s.c_str());
-00415 }
+
00414 {
+00415         log(level,"%s",s.c_str());
+00416 }
 
    
   
 
@@ -1249,14 +1249,14 @@ Matches text against a glob pattern.
 

 Uses the ircd's internal matching function to match string against a globbing pattern, e.g. *!*@*.com Returns true if the literal successfully matches the pattern, false if otherwise.
 

-Definition at line 349 of file modules.cpp.
+Definition at line 350 of file modules.cpp.
 

-
00350 {
-00351         char literal[MAXBUF],pattern[MAXBUF];
-00352         strlcpy(literal,sliteral.c_str(),MAXBUF);
-00353         strlcpy(pattern,spattern.c_str(),MAXBUF);
-00354         return match(literal,pattern);
-00355 }
+
00351 {
+00352         char literal[MAXBUF],pattern[MAXBUF];
+00353         strlcpy(literal,sliteral.c_str(),MAXBUF);
+00354         strlcpy(pattern,spattern.c_str(),MAXBUF);
+00355         return match(literal,pattern);
+00356 }
 
    
   
 
@@ -1305,11 +1305,11 @@ Forces a user to part a channel.
 

 This is similar to svspart and can be used to implement redirection, etc. Although the return value of this function is a pointer to a channel record, the returned data is undefined and should not be read or written to. This behaviour may be changed in a future version.
 

-Definition at line 367 of file modules.cpp.
+Definition at line 368 of file modules.cpp.
 

-
00368 {
-00369         return del_channel(user,cname.c_str(),reason.c_str(),false);
-00370 }
+
00369 {
+00370         return del_channel(user,cname.c_str(),reason.c_str(),false);
+00371 }
 
    
   
 
@@ -1354,14 +1354,14 @@ To the user, it will appear as if they typed /QUIT themselves, except for the fa
 WARNING!

 Once you call this function, userrec* user will immediately become INVALID. You MUST NOT write to, or read from this pointer after calling the QuitUser method UNDER ANY CIRCUMSTANCES! The best course of action after calling this method is to immediately bail from your handler.
 

-Definition at line 396 of file modules.cpp.
+Definition at line 397 of file modules.cpp.
 

 References userrec::nick, and send_network_quit().
 

-
00397 {
-00398         send_network_quit(user->nick,reason.c_str());
-00399         kill_link(user,reason.c_str());
-00400 }
+
00398 {
+00399         send_network_quit(user->nick,reason.c_str());
+00400         kill_link(user,reason.c_str());
+00401 }
 
    
   
 
@@ -1404,11 +1404,11 @@ Sends a line of text down a TCP/IP socket.
 

 This method writes a line of text to an established socket, cutting it to 510 characters plus a carriage return and linefeed if required.
 

-Definition at line 427 of file modules.cpp.
+Definition at line 428 of file modules.cpp.
 

-
00428 {
-00429         Write(Socket,"%s",s.c_str());
-00430 }
+
00429 {
+00430         Write(Socket,"%s",s.c_str());
+00431 }
 
    
   
 
@@ -1463,18 +1463,18 @@ Sends text from a user to a channel (mulicast).
 

 This method writes a line of text to a channel, with the given user's nick/ident /host combination prepended, as used in PRIVMSG etc commands (see RFC 1459). If the IncludeSender flag is set, then the text is also sent back to the user from which it originated, as seen in MODE (see RFC 1459).
 

-Definition at line 456 of file modules.cpp.
-

-
00457 {
-00458         if (IncludeSender)
-00459         {
-00460                 WriteChannel(Channel,User,"%s",s.c_str());
-00461         }
-00462         else
-00463         {
-00464                 ChanExceptSender(Channel,User,"%s",s.c_str());
-00465         }
-00466 }
+Definition at line 457 of file modules.cpp.
+

+
00458 {
+00459         if (IncludeSender)
+00460         {
+00461                 WriteChannel(Channel,User,"%s",s.c_str());
+00462         }
+00463         else
+00464         {
+00465                 ChanExceptSender(Channel,User,"%s",s.c_str());
+00466         }
+00467 }
 
    
   
 
@@ -1523,18 +1523,18 @@ Sends text from a user to one or more channels (mulicast).
 

 This method writes a line of text to all users which share a common channel with a given user, with the user's nick/ident/host combination prepended, as used in PRIVMSG etc commands (see RFC 1459). If the IncludeSender flag is set, then the text is also sent back to the user from which it originated, as seen in NICK (see RFC 1459). Otherwise, it is only sent to the other recipients, as seen in QUIT.
 

-Definition at line 473 of file modules.cpp.
-

-
00474 {
-00475         if (IncludeSender)
-00476         {
-00477                 WriteCommon(User,"%s",text.c_str());
-00478         }
-00479         else
-00480         {
-00481                 WriteCommonExcept(User,"%s",text.c_str());
-00482         }
-00483 }
+Definition at line 474 of file modules.cpp.
+

+
00475 {
+00476         if (IncludeSender)
+00477         {
+00478                 WriteCommon(User,"%s",text.c_str());
+00479         }
+00480         else
+00481         {
+00482                 WriteCommonExcept(User,"%s",text.c_str());
+00483         }
+00484 }
 
    
   
 
@@ -1583,11 +1583,11 @@ Sends text from a user to a socket.
 

 This method writes a line of text to an established socket, with the given user's nick/ident /host combination prepended, as used in PRIVSG etc commands (see RFC 1459)
 

-Definition at line 437 of file modules.cpp.
+Definition at line 438 of file modules.cpp.
 

-
00438 {
-00439         WriteFrom(Socket,User,"%s",s.c_str());
-00440 }
+
00439 {
+00440         WriteFrom(Socket,User,"%s",s.c_str());
+00441 }
 
    
   
 
@@ -1643,13 +1643,13 @@ modes[2] = user->nick;

 Srv->SendMode(modes,3,user);

 The modes will originate from the server where the command was issued, however responses (e.g. numerics) will be sent to the user you provide as the third parameter. You must be sure to get the number of parameters correct in the pcnt parameter otherwise you could leave your server in an unstable state!
 

-Definition at line 422 of file modules.cpp.
+Definition at line 423 of file modules.cpp.
 

 References server_mode().
 

-
00423 {
-00424         server_mode(parameters,pcnt,user);
-00425 }
+
00424 {
+00425         server_mode(parameters,pcnt,user);
+00426 }
 
    
   
 
@@ -1683,11 +1683,11 @@ Sends text to all opers.
 

 This method sends a server notice to all opers with the usermode +s.
 

-Definition at line 344 of file modules.cpp.
+Definition at line 345 of file modules.cpp.
 

-
00345 {
-00346         WriteOpers("%s",s.c_str());
-00347 }
+
00346 {
+00347         WriteOpers("%s",s.c_str());
+00348 }
 
    
   
 
@@ -1730,11 +1730,11 @@ Sends text from the server to a socket.
 

 This method writes a line of text to an established socket, with the servername prepended as used by numerics (see RFC 1459)
 

-Definition at line 432 of file modules.cpp.
+Definition at line 433 of file modules.cpp.
 

-
00433 {
-00434         WriteServ(Socket,"%s",s.c_str());
-00435 }
+
00434 {
+00435         WriteServ(Socket,"%s",s.c_str());
+00436 }
 
    
   
 
@@ -1787,22 +1787,22 @@ The format will become:

 :localserver TEXT

 Which is useful for numerics and server notices to single users, etc.
 

-Definition at line 442 of file modules.cpp.
+Definition at line 443 of file modules.cpp.
 

 References connection::fd.
 

-
00443 {
-00444         if (!Source)
-00445         {
-00446                 // if source is NULL, then the message originates from the local server
-00447                 Write(Dest->fd,":%s %s",this->GetServerName().c_str(),s.c_str());
-00448         }
-00449         else
-00450         {
-00451                 // otherwise it comes from the user specified
-00452                 WriteTo(Source,Dest,"%s",s.c_str());
-00453         }
-00454 }
+
00444 {
+00445         if (!Source)
+00446         {
+00447                 // if source is NULL, then the message originates from the local server
+00448                 Write(Dest->fd,":%s %s",this->GetServerName().c_str(),s.c_str());
+00449         }
+00450         else
+00451         {
+00452                 // otherwise it comes from the user specified
+00453                 WriteTo(Source,Dest,"%s",s.c_str());
+00454         }
+00455 }
 
    
   
 
@@ -1853,11 +1853,11 @@ These can be RFC specified modes such as +i, or module provided modes, including
 Serv->SendToModeMask("xi", WM_OR, "m00");

 Then the text 'm00' will be sent to all users with EITHER mode x or i. Conversely if you used WM_AND, the user must have both modes set to receive the message.
 

-Definition at line 357 of file modules.cpp.
+Definition at line 358 of file modules.cpp.
 

-
00358 {
-00359         WriteMode(modes.c_str(),flags,"%s",text.c_str());
-00360 }
+
00359 {
+00360         WriteMode(modes.c_str(),flags,"%s",text.c_str());
+00361 }
 
    
   
 
@@ -1900,17 +1900,17 @@ Sends a WALLOPS message.
 

 This method writes a WALLOPS message to all users with the +w flag, originating from the specified user.
 

-Definition at line 485 of file modules.cpp.
+Definition at line 486 of file modules.cpp.
 

-
00486 {
-00487         WriteWallOps(User,false,"%s",text.c_str());
-00488 }
+
00487 {
+00488         WriteWallOps(User,false,"%s",text.c_str());
+00489 }
 
    
   
 
 
The documentation for this class was generated from the following files:
-
Generated on Sat Apr 2 19:27:07 2005 for InspIRCd by
+
Generated on Mon Apr 4 18:12:54 2005 for InspIRCd by
 
 doxygen 
 1.3.3 

-- 
cgit v1.2.3