Re: plPHP and plRuby

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org, Neil Conway <neilc(at)samurai(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: plPHP and plRuby
Date: 2006-07-24 17:45:37
Message-ID: 20060724174537.GK5223@surnet.cl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joshua D. Drake wrote:
> Peter Eisentraut wrote:
> >Am Montag, 24. Juli 2006 18:49 schrieb Alvaro Herrera:
> >>Side question -- is it plRuby or PL/Ruby? We should be consistent. I
> >>just noticed the top-level README file has all the wrong names -- what
> >>is "pl/c" for starters? Or plPgsql? We've _never_ used those names.
> >
> >I'm beginning to think that this is part of some obscure plot by Joshua
> >Drake to confuse people.
>
> I sincerely hope you are kidding.

I understand that he is.

> >I advise all committers not to take any documentation
> >patches from him without careful scrutiny.
>
> Gah... aren't you just all sour grapes. The README was reviewed by
> several people, in fact it went through two versions to the patches list.

I saw those fly by and my gut feeling was "whoever commits this is
_certainly_ going to fix it". I'm not sure why I didn't comment on it.

> Sorry that nobody caught it (including myself), but good lord it isn't
> that big of a deal.

Consistency is important. It may not be _THAT_ big a deal, but we
should be at least a little careful.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joachim Wieland 2006-07-24 17:47:58 Re: Allow commenting of variables in postgresql.conf to - try 4
Previous Message Marc Munro 2006-07-24 17:31:13 Making config file parser available to add-ins