From: Michael Robinson <robinson@public.bta.net.cn>
To: pgsql-interfaces@hub.org
Subject: RE: [INTERFACES] Updated IDL with considerations for COSS
Date: Tue, 17 Nov 1998 00:01:37 +0800 (GMT)
Message-ID: <199811161601.AAA15830@public.bta.net.cn> (raw)
"Taral" <taral@cyberjunkie.com> writes:
>module PostgreSQL { // Note we already separate our namespace
> module Types {
> typedef short int2;
> typedef short int4;
> // etc.
> }
Works for me.
>> I would recommend that fixed-length PostgreSQL types be defined as little-
>> endian arrays of long or octet type, whichever is appropriate. E.g.:
>>
>> typedef long pgtype_int8[2];
>> typedef long pgtype_int28[4];
>> typedef octet pgtype_macaddr[6];
>> typedef octet pgtype_filename[256];
I think I meant big-endian (that *is* "network order", isn't it? I always
forget). Anyway, you get the point.
>P.S. Would it be possible to make a pgsql/src/corba module and let me check
>this IDL file into it? That way I don't have to keep reposting it.
Well, until it's fairly stable, keep reposting it. That way people don't
have to keep checking for changes in the tree.
-Michael Robinson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: robinson@public.bta.net.cn, pgsql-interfaces@hub.org
Subject: RE: [INTERFACES] Updated IDL with considerations for COSS
In-Reply-To: <199811161601.AAA15830@public.bta.net.cn>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox