[DGD] Re: dgd crashes on fatal errors

[Stephen Schmidt]

On Fri, 24 Oct 2003, Erwin Harte wrote:
> This is the same as what the original poster tried with the 'return
> nil;', except you're running with a different strict-typing mode.
> It'll cause an intentional coredump as s/he showed.

Hm, interesting. I can understand why the driver needs to insist
that binary_connect() be defined. I'm not sure I understand
why it can't return 0 or nil, but it can return an object that
instantly self-destructs. Is it because the driver makes a call
into the object after getting it back from binary_connect() and
doesn't check to make sure it has a legitimate value before
making the call? If so, then I understand why DGD aborts in
this case, but it would seem logical to me to allow binary_connect
to return nil if the programmer wants to ignore requests on the
binary port.

Another possibility is that the driver can't tell the difference
between a function that's undefined and one that returns nil,
but that strikes me as pretty unlikely.

> You can currently provide an array of port-numbers.  It's on the todo
> list to make it possible to put an empty array there and have no
> binary (or telnet) ports open at all.

Sounds good. Not a high priority, I imagine.

Steve


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