Re: close() vs. closesocket()

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: pgsql(at)mohawksoft(dot)com
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: close() vs. closesocket()
Date: 2003-04-25 16:16:08
Message-ID: 200304251616.h3PGG8A24353@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

pgsql(at)mohawksoft(dot)com wrote:
> > pgsql(at)mohawksoft(dot)com wrote:
> >> >
> >> > We have never been into abstraction for the sake of abstraction.
> >>
> >> Would you say that is a *good* thing or a *bad* thing?
> >
> > A good thing --- too much abstraction is bad --- look at Mozilla for a
> > chilling example.
> >
> Anyone can find a *bad* example of something good. I did justify my
> statement with a "reasonable" cause.

Mozilla is an example of a case where too much abstraction is bad ---
hence supporting my statement:

> >> > We have never been into abstraction for the sake of abstraction.

As far as examples, we are doing a few you mention already, and will
review the others once we are done. If there are too many special
cases, we can look at abstraction, but there has to be more than what I
have seen so far.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message pgsql 2003-04-25 16:17:22 Re: close() vs. closesocket()
Previous Message Bruce Momjian 2003-04-25 16:09:10 Re: close() vs. closesocket()

Browse pgsql-patches by date

  From Date Subject
Next Message pgsql 2003-04-25 16:17:22 Re: close() vs. closesocket()
Previous Message Bruce Momjian 2003-04-25 16:09:10 Re: close() vs. closesocket()