[DGD] Fatal error when no user object returned

[Blain]

"of an interest" => "if an inherited"

Anywho, I should make a list of these catches.  =)~

On Tue, Jun 5, 2018, 04:26 Blain <blain20 at gmail.com> wrote:

> I don't see the purpose.  Not every port mentioned in the config file is
> necessarily critical to MUD operation.  Sure, it's easy to do a workaround,
> but I question the purpose of the explicit fatal shutdown.  A dust object
> would need to be simple so as not to bug out of an interest or included
> file happened to be unstable.  The sudden shutdown would lose any data
> since the last data dump.  Keeping the game up and running and player data
> intact are extremely important on a MUD.  I don't see this as a valid
> excuse for losing data.
>
> On Tue, Jun 5, 2018, 01:34 Raymond Jennings <shentino at gmail.com> wrote:
>
>> In My Opinion (tm):
>>
>> Failing to return the proper type in a driver hook is a fundamental
>> API violation.
>>
>> However, I think you can still just cause a runtime error and not return
>> at all.
>>
>> Plus you could always have a burner object that just disconnects
>> immediately when it's assigned a connection.  Not that hard.
>>
>> On Mon, Jun 4, 2018 at 11:26 PM, Blain <blain20 at gmail.com> wrote:
>> > Instead of closing DGD when no user object is returned, would it be more
>> > prudent to just close the incoming connection?
>> > ____________________________________________
>> > https://mail.dworkin.nl/mailman/listinfo/dgd
>> ____________________________________________
>> https://mail.dworkin.nl/mailman/listinfo/dgd
>
>