Re: pljava revisited

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: Andrew Rawnsley <ronz(at)ravensfield(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pljava revisited
Date: 2003-12-10 18:04:39
Message-ID: 3FD76037.7050605@Yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Rawnsley wrote:

>> Other pl* (perl, python, tcl) languages have vanilla C glue code.
>> Might be better to stick to this. If you aren't using advanced C++
>> features that shouldn't be too hard - well structured C can be just as
>> readable as well structured C++. At the very lowest level, about the
>> only things C++ buys you are the ability to declare variables in
>> arbitrary places, and // style comments.
>>
>
> Agreed. Given that the rest of the code base is C....I would imagine
> that the Powers that Be would frown a bit on merging
> C++ code in, and relegate it to contrib for eternity...

It will probably have to live on GBorg right from the beginning anyway,
so "the Powers" might not care at all.

Thus far _all_ procedural languages are loadable modules. VM or not, I
don't see why this one would be any different. That also answers the "on
demand" question to some extent, doesn't it?

Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Hallgren 2003-12-10 18:15:22 Re: pljava revisited
Previous Message Joe Conway 2003-12-10 17:27:27 Re: Strange permission problem regarding pg_settings