Re: why not remove AF_LOCAL sockets on last close?

[der Mouse <mouse%Rodents-Montreal.ORG@localhost>]

>>> A reason might be that every other system behaves the same way and
>>> being different will just lead to non-portable code.
>> Non-portable *how*?  What exactly would happen?
> I don't know, and if you've got an argument that code written for
> either behavior will be ok both places I don't have a problem with
> it.  The only thing I can think of is that code that does an explicit
> unlink and checks for error on the unlink may complain, which is
> pretty mild.

Well, code that expects the automatic unlink is liable to break
unexpectedly (and probably cryptically) on "traditional" systems.

/~\ The ASCII                             Mouse
\ / Ribbon Campaign
 X  Against HTML                mouse%rodents-montreal.org@localhost
/ \ Email!           7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B