[project @ 2004-05-12 15:19:06 by unknown_lamer]

2004-05-12  Clinton Ebadi  <clinton@unknownlamer.org>

	* source/DCCConnection.C (DCCConnection): Intialized `nuh' in the
	constructor with `n' This should fix the segfaulting.

diff --git a/ChangeLog b/ChangeLog
index 13d4c97..5d035ac 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2004-05-12  Clinton Ebadi  <clinton@unknownlamer.org>
+
+       * source/DCCConnection.C (DCCConnection): Intialized `nuh' in the
+       constructor with `n' This should fix the segfaulting.
+
 2004-01-28  Clinton Ebadi  <clinton@unknownlamer.org>
 
        * ChangeLog: Updated copyright notice

diff --git a/bobot++.info b/bobot++.info
index 4e52901..de04f1c 100644 (file)
--- a/bobot++.info
+++ b/bobot++.info
@@ -1,4 +1,4 @@
-This is bobot++.info, produced by makeinfo version 4.3 from
+This is bobot++.info, produced by makeinfo version 4.6 from
 bobot++.texinfo.
 
    This file documents Bobot++ by Clinton Ebadi and Etienne Bernard
@@ -44,8 +44,7 @@ File: bobot++.info,  Node: Introduction,  Next: Configuration,  Prev: Top,  Up:
 Introduction
 ************
 
-   This manual feels abused and neglected because it has almost no
-content.
+This manual feels abused and neglected because it has almost no content.
 
 \1f
 File: bobot++.info,  Node: Configuration,  Next: Using the Bot,  Prev: Introduction,  Up: Top
@@ -53,7 +52,7 @@ File: bobot++.info,  Node: Configuration,  Next: Using the Bot,  Prev: Introduct
 Configuration
 *************
 
-   Bobot++ is easy to configure. The configuration file format may be
+Bobot++ is easy to configure. The configuration file format may be
 changing in the 2.1 series, so it is not documented for now. See the
 `examples' directory for an example configuration.
 
@@ -78,7 +77,7 @@ File: bobot++.info,  Node: bot.conf,  Prev: Configuration File Syntax,  Up: Conf
 bot.conf
 --------
 
-   bot.conf is the main configuration file for a Bobot++. The available
+bot.conf is the main configuration file for a Bobot++. The available
 configuration variables are listed below in the format "VARIABLE
 <default-value>: description"
 
@@ -106,10 +105,10 @@ File: bobot++.info,  Node: Configure File Placement,  Prev: Configuration File S
 Configuration File Placement
 ============================
 
-   Bobot++ will look in `/etc/bobotpp/default/' for its default config
-if none is specified on the command line. Put the configuration files
-you want to be loaded by default in this directory. If you are not root
-or you want to have your own personal configration, put it in
+Bobot++ will look in `/etc/bobotpp/default/' for its default config if
+none is specified on the command line. Put the configuration files you
+want to be loaded by default in this directory. If you are not root or
+you want to have your own personal configration, put it in
 `~/.bobotpp/config/default/'.
 
 \1f
@@ -118,7 +117,7 @@ File: bobot++.info,  Node: Using the Bot,  Next: Scripting,  Prev: Configuration
 Using Bobot++
 *************
 
-   FIXME: stuff here...
+FIXME: stuff here...
 
 * Menu:
 
@@ -130,7 +129,7 @@ File: bobot++.info,  Node: User Levels,  Prev: Using the Bot,  Up: Using the Bot
 User Levels
 ===========
 
-   There are five levels that a user may be when interfacing with a bot:
+There are five levels that a user may be when interfacing with a bot:
 NONE, USER, TRUSTED_USER, FRIEND, MASTER. All users default to NONE
 unless they are changed by a script, the `!adduser' command or the
 `bot.users' file. NONE is for everyone--very few commands (e.g. help)
@@ -150,7 +149,7 @@ File: bobot++.info,  Node: Scripting,  Next: Concept Index,  Prev: Using the Bot
 Scripting
 *********
 
-   Bobot++'s most powerful feature is its scripting system. You write
+Bobot++'s most powerful feature is its scripting system. You write
 scripts using Guile Scheme. This manual does not cover how to use Guile
 or how to learn Scheme. *Note Guile Reference Manual: (guile)Top, for
 the Guile reference manual and
@@ -177,7 +176,7 @@ File: bobot++.info,  Node: Adding New Commands,  Next: Hooks,  Prev: Scripting,
 Adding New Commands
 ===================
 
-   Adding a new command is simple. To register a new command use
+Adding a new command is simple. To register a new command use
 `bot:addcommand'. The prototype for `bot:addcommand' is
 `(bot:addcommand name func needs-channel? num-of-args min-level)'. The
 `name' is a string representing the name of the command being added.
@@ -206,7 +205,7 @@ File: bobot++.info,  Node: Hooks,  Next: Scheme User Levels,  Prev: Adding New C
 Hooks
 =====
 
-   Hooks are a powerful feature of Bobot++. Hooks are a hybrid of ircII
+Hooks are a powerful feature of Bobot++. Hooks are a hybrid of ircII
 and tiny fugue (a MUD bot) hooks with a little bit of extra stuff added
 in. The basic idea of a hook if that you match a text against regular
 expression and call a function if text in a message matches that regex.
@@ -230,20 +229,20 @@ File: bobot++.info,  Node: Creating a Hook,  Next: Hook Types,  Prev: Hooks,  Up
 Creating a Hook
 ---------------
 
-   To add a new hook you use the function `bot:addhook'. `bot:addhook'
-is prototyped as `(bot:addhook type regex function pri fall name)'.
-`type' specifies the type of hook (the types of hooks are listed in
-*Note Hook Types::). `regex' is a standard regular expression. If
-`regex' is matched, `function' will be called. `function' will take a
-different number of args depending on the hook type. `pri' specifies
-the priority of the hook--higher priority hooks are executed first.
-This argument is optional and defaults to `0'. `fall' is `#t' if the
-hook is a fallthrough hook and `#f' is the hook is not a fallthrough
-hook. This arg is also optional and default to `#t'. `name' is the
-optional name of the hook that defaults to "DEFAULT". If you set the
-name then you can have more than one hook that matches the same regexp,
-as long as they have the same name. E.g. in a log script you could have
-the regexps for the log function all be `".*"' and set their names to
+To add a new hook you use the function `bot:addhook'. `bot:addhook' is
+prototyped as `(bot:addhook type regex function pri fall name)'. `type'
+specifies the type of hook (the types of hooks are listed in *Note Hook
+Types::). `regex' is a standard regular expression. If `regex' is
+matched, `function' will be called. `function' will take a different
+number of args depending on the hook type. `pri' specifies the priority
+of the hook--higher priority hooks are executed first. This argument is
+optional and defaults to `0'. `fall' is `#t' if the hook is a
+fallthrough hook and `#f' is the hook is not a fallthrough hook. This
+arg is also optional and default to `#t'. `name' is the optional name
+of the hook that defaults to "DEFAULT". If you set the name then you
+can have more than one hook that matches the same regexp, as long as
+they have the same name. E.g. in a log script you could have the
+regexps for the log function all be `".*"' and set their names to
 `"log"' to avoid a conflict with other hooks.
 
 \1f
@@ -252,8 +251,8 @@ File: bobot++.info,  Node: Hook Types,  Prev: Creating a Hook,  Up: Hooks
 Hook Types
 ----------
 
-   Here is a list of the various hooks are notes on each one. The
-general format of a hook is:
+Here is a list of the various hooks are notes on each one. The general
+format of a hook is:
 
    * `hooks/name' (this is the Scheme variable name of the hook)
         - Description of the hook
@@ -416,7 +415,7 @@ File: bobot++.info,  Node: Scheme User Levels,  Next: Sending Messages,  Prev: H
 Scheme User Levels
 ==================
 
-   There are five levels that a user may be when interfacing with a bot:
+There are five levels that a user may be when interfacing with a bot:
 NONE, USER, TRUSTED_USER, FRIEND, MASTER. The Scheme variables for the
 user levels are `bot:user-none', `bot:user-user', `bot:user-trusted',
 `bot:user-friend', and `bot:user-master'. See *Note User Levels:: for
@@ -439,7 +438,7 @@ File: bobot++.info,  Node: Sending Messages,  Next: Misc Scripting Stuff,  Prev:
 Sending Messages
 ================
 
-   There are several types of messages you can send with Bobot++ from
+There are several types of messages you can send with Bobot++ from
 scripts. There is the simple, but rather limited, `bot:say',
 `bot:action' and `bot:msg', and the more powerful, but lower level,
 `bot:send-MESSAGE' functions. Most bots will probably only need the
@@ -457,7 +456,7 @@ File: bobot++.info,  Node: High Level Message Functions,  Next: Low Level Messag
 "High Level" Message Functions
 ------------------------------
 
-   ...
+...
 
 \1f
 File: bobot++.info,  Node: Low Level Message Functions,  Prev: High Level Message Functions,  Up: Sending Messages
@@ -465,7 +464,7 @@ File: bobot++.info,  Node: Low Level Message Functions,  Prev: High Level Messag
 "Low Level" Message Functions
 -----------------------------
 
-   The "Low Level" messaging functions allow you to do things like send
+The "Low Level" messaging functions allow you to do things like send
 CTCP messages. You probably want to read rfc 2812 and the CTCP spec
 before using these. If you have no idea what these do, read rfc 2812
 (IRC Client Protocol) and CTCP spec. These functions all return
@@ -483,7 +482,7 @@ File: bobot++.info,  Node: Misc Scripting Stuff,  Prev: Sending Messages,  Up: S
 Misc. Scripting Stuff
 =====================
 
-   These are a few useful things that I thought people writing scripts
+These are a few useful things that I thought people writing scripts
 might want to know.
 
    If you want to execute code when the bot exits, just do `add-hook!
@@ -552,24 +551,24 @@ Variable Index
 Tag Table:
 Node: Top\7f517
 Node: Introduction\7f1246
-Node: Configuration\7f1437
-Node: Configuration File Syntax\7f1823
-Node: bot.conf\7f2030
-Node: Configure File Placement\7f2865
-Node: Using the Bot\7f3339
-Node: User Levels\7f3513
-Node: Scripting\7f4517
-Node: Adding New Commands\7f5425
-Node: Hooks\7f6692
-Node: Creating a Hook\7f7666
-Node: Hook Types\7f8805
-Node: Scheme User Levels\7f12279
-Node: Sending Messages\7f13408
-Node: High Level Message Functions\7f14019
-Node: Low Level Message Functions\7f14233
-Node: Misc Scripting Stuff\7f14986
-Node: Concept Index\7f15405
-Node: Function Index\7f15587
-Node: Variable Index\7f15848
+Node: Configuration\7f1434
+Node: Configuration File Syntax\7f1817
+Node: bot.conf\7f2024
+Node: Configure File Placement\7f2856
+Node: Using the Bot\7f3327
+Node: User Levels\7f3498
+Node: Scripting\7f4499
+Node: Adding New Commands\7f5404
+Node: Hooks\7f6668
+Node: Creating a Hook\7f7639
+Node: Hook Types\7f8775
+Node: Scheme User Levels\7f12246
+Node: Sending Messages\7f13372
+Node: High Level Message Functions\7f13980
+Node: Low Level Message Functions\7f14191
+Node: Misc Scripting Stuff\7f14941
+Node: Concept Index\7f15357
+Node: Function Index\7f15539
+Node: Variable Index\7f15800
 \1f
 End Tag Table

diff --git a/source/DCCConnection.C b/source/DCCConnection.C
index 5f2ffea..16349e5 100644 (file)
--- a/source/DCCConnection.C
+++ b/source/DCCConnection.C
@@ -33,7 +33,7 @@ DCCConnection::DCCConnection(unsigned long address,
 
 DCCConnection::DCCConnection(Bot *b, String n, unsigned long address, 
                                     int port)
-  : Connection(address, port), bot(b),lastSpoken(time(0)), autoRemove(true)
+  : Connection(address, port), bot(b), nuh (n), lastSpoken(time(0)), autoRemove(true)
 { }
 
 // bool

diff --git a/source/DCCManager.C b/source/DCCManager.C
index 8f51521..3ea012b 100644 (file)
--- a/source/DCCManager.C
+++ b/source/DCCManager.C
@@ -22,6 +22,7 @@ DCCManager::addConnection (DCCConnection *cnx)
 {
   DCCPerson *person = new DCCPerson (cnx);
   String temp = person->getAddress ();
+  cnx->get_bot()->logLine (temp);
   if (dcc_map[temp])
     delete dcc_map[temp];
   dcc_map[person->getAddress ()] = person;