Re: Multiple anyelement types - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: Multiple anyelement types
Date
Msg-id 162867790808110412t277c090bj61a130341dbba884@mail.gmail.com
Whole thread Raw
In response to Multiple anyelement types  (ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp>)
List pgsql-hackers
He

2008/8/11 ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp>:
> I'm working on improvements of orafce.
> http://pgfoundry.org/projects/orafce
>
> I found postgres supports only one type of anyelement at one time
> when I added nvl2() and decode(). I'd like to use multiple types of
> anyelement something like:
>
>  template < typename Expr, typename Ret >
>  CREATE FUNCTION nvl(Expr, Ret, Ret) RETURNS Ret
>
>  template < typename Expr, typename Ret >
>  CREATE FUNCTION decode(Expr, Expr, Ret, ..., Ret) RETURNS Ret
>
> I don't mean to propose the above C++-like syntax, but such feature
> is important to develop a generic porting tool. Two independent
> anyelements are enough for me, but three or more might be better
> for general use.
>

it's good idea - I though so 2 independent types are enough:
anyelement2, enyarray2. If you are C coder, you should use "any" type.

regards
Pavel Stehule

> What syntax is suitable for postgres? Comments welcome.
>
> Regards,
> ---
> ITAGAKI Takahiro
> NTT Open Source Software Center
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>


pgsql-hackers by date:

Previous
From: Zdenek Kotala
Date:
Subject: Re: Proposal: PageLayout footprint
Next
From: "Heikki Linnakangas"
Date:
Subject: Re: Proposal: PageLayout footprint