[DGD]Kernel mudlib oddity

[Noah Lee Gibbs]

  Okay, never mind, they're both my fault.

  If I register an empty object manager, no bodies to the functions except
where I have to return a value (and then just returning a constant), then
disconnection doesn't work.  If I don't register *any* object manager, it
does.
  Looking at driver.c and the driver kernel mudlib docs, it doesn't look
like an object manager has any particular duties -- it just gets notified
when things happen.  Anybody know why registering an empty object manager
might stop disconnection from working?

On Mon, 11 Jun 2001, Noah Lee Gibbs wrote:

>    Hmm...  Part of this *was* me.  Part still isn't.  Not seeing what
> people say was my problem, but not logging out may still not be --
> user.c's receive_message is returning MODE_DISCONNECT, but it's not
> disconnecting -- though it looks like the auto object _is_ calling
> destruct_object on the user object.
>   I'll keep looking.
> 
> On Mon, 11 Jun 2001, Noah Lee Gibbs wrote:
> 
> >   I upgraded to 1.2.24 from 1.2 and I've noticed something funny with the
> > Kernel mudlib.  I originally thought I must have messed it up myself, but
> > logging into the (un-overridden) binary port gives the same behavior, so I
> > don't *think* it's me...
> >   "Say"s don't get to other people logged in, and if you type "quit" it
> > goes to a blank line but doesn't close the connection.  If you hit return
> > again, you get another prompt.
> >   Anybody else seen this in the Kernel mudlib in 1.2.24?
> > 
> > 
> > List config page:  http://list.imaginary.com/mailman/listinfo/dgd
> > 
> 
> 
> List config page:  http://list.imaginary.com/mailman/listinfo/dgd
> 


List config page:  http://list.imaginary.com/mailman/listinfo/dgd