Re: PL/pgSQL 2 - Mailing list pgsql-hackers

From Steven Lembark
Subject Re: PL/pgSQL 2
Date
Msg-id 20141007124214.736d0ab6.lembark@wrkhors.com
Whole thread Raw
In response to Re: PL/pgSQL 2  (Joel Jacobson <joel@trustly.com>)
Responses Re: PL/pgSQL 2
List pgsql-hackers
On Mon, 1 Sep 2014 15:19:41 +0200
Joel Jacobson <joel@trustly.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@wrkhors.com                                      +1 888 359 3508



pgsql-hackers by date:

Previous
From: Oleg Bartunov
Date:
Subject: Re: GIN pageinspect functions
Next
From: Heikki Linnakangas
Date:
Subject: Re: GIN pageinspect functions