>No, we don't have any concept of member functions. Just create the
>composite type (I'm assuming it needs to be composite) and then create
>functions that take it as parameter.
>
>Note that because PG allows function overloading, there's no conflict
>between, say, to_string(D_Temp_Element) and to_string(Some_Other_Type).
>If you were only using member functions to prevent that kind of
>conflict, I don't think you need to worry too much.
OK thanks.
>PS: this is not an appropriate question for -hackers. Please direct
>simple usage questions to -general in future.
Sorry.
