[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Problem report #15
From: |
Stuart D. Herring |
Subject: |
Re: Problem report #15 |
Date: |
Thu, 13 Apr 2006 08:28:55 -0700 (PDT) |
User-agent: |
SquirrelMail/1.4.3a-11.EL3 |
> Yes, you're right. I think I have fixed it now.
>
> However, I wonder, why not make conv_lisp_to_sockaddr signal
> a Lisp error if the family is not recognized. Is there any
> reason not to do this?
That's exactly what I suggested in the previous mail. However, it might
be good for get_lisp_to_sockaddr_size to signal if it can't figure out a
reasonable size, so that code doesn't break in the future if a new address
family or so is added to one and not the other.
Davis
--
This product is sold by volume, not by mass. If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.