Re: PL/pgSQL 2

From: Steven Lembark <lembark(at)wrkhors(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Cc: lembark(at)wrkhors(dot)com
Subject: Re: PL/pgSQL 2
Date: 2014-10-07 17:42:14
Message-ID: 20141007124214.736d0ab6.lembark@wrkhors.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 1 Sep 2014 15:19:41 +0200
Joel Jacobson <joel(at)trustly(dot)com> wrote:

> The fatal problems with Python3 and Perl6 was the inability to mix
> code between Python2/3 and Perl5/6.
> We don't have that problem with pl-languages in postgres, so please
> don't make that comparison, as it's incorrect.

Actually Perl6 can include Perl5 code allows you to "use v5.6" or "use
v6.0" to regulate how the code in any one block is compiled w/in the
program. Even Perl 5 allows mixing blocks/modules with different version
syntax w/in the same compiler.

The mistake Python made was not allowing the Python 3 compiler to
gracefully handle Pythin 2 input.

--
Steven Lembark 3646 Flora Pl
Workhorse Computing St Louis, MO 63110
lembark(at)wrkhors(dot)com +1 888 359 3508

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2014-10-07 17:56:38 Re: GIN pageinspect functions
Previous Message Oleg Bartunov 2014-10-07 17:36:33 Re: GIN pageinspect functions