Re: [HACKERS] Re: inet/cidr/bind

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: darcy(at)druid(dot)net (D'Arcy J(dot)M(dot) Cain)
Cc: paul(at)vix(dot)com, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Re: inet/cidr/bind
Date: 1998-10-20 00:03:28
Message-ID: 199810200003.UAA25020@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> And besides:
>
> if (strlen("D'Arcy J.M. Cain") > strlen("Paul Vixie"))
> printf("Who's the big name now? :-)\n");
>
> And look at all that StUdLy punctuation. :-)

That was funny.

> > > I think we are just about there. If we go with my plan (completely
> > > different functionality for now and fold it later) there should be
> > > no API change later. There will be code and catalogue changes but
> > > they should be relatively painless.
> >
> > so shall i test the inet_cidr_ functions and punt them on in?
>
> Ok, before I have a reality shift, the inet_cidr_ functions are simply
> the original inet_net_ functions renamed, right?
>
> I so hate it when the universe does that stuttering thing.

Just a clarification. If you have function that can be called with
either type, you can put two entries in pg_proc(or I can :-) ), and that
way the one function can take two types as parameters. Allows use to
maintain the type easier, and less bloat.

--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message D'Arcy J.M. Cain 1998-10-20 01:57:38 Re: [HACKERS] Postgres - Y2K Compliant....Yes or No
Previous Message Bruce Momjian 1998-10-19 23:59:17 Re: [HACKERS] Re: inet/cidr/bind