Re: encode in base code - Mailing list pgsql-patches

From Peter Eisentraut
Subject Re: encode in base code
Date
Msg-id Pine.LNX.4.30.0107031734290.677-100000@peter.localdomain
Whole thread Raw
In response to Re: encode in base code  (Marko Kreen <marko@l-t.ee>)
List pgsql-patches
Marko Kreen writes:

> On Mon, Jul 02, 2001 at 07:50:45PM +0200, Peter Eisentraut wrote:
> > Would you mind changing the copyright to match the rest of the source?
>
> Ok, I needed the BSD-style for separate distribution.
>
> Should it be only line:
>
> Copyright (c) 2001 PostgreSQL Global Development Group

You can keep your name if you want, but I don't see a point in having 73
slightly differently worded BSD-like licenses in the core.

> > I think we've covered before that 'uint' is not a standard data type.
> > VARSIZE is of type int32 (signed).
>
> I have not seen this discussion.  I used uint as simply handy
> shortcut.  When I want unsigned var, should it be 'uint32' or
> simply 'unsigned'?  Or should I avoid using unsigned vars?  Why?

(Might have been related to your digest module.)  AFAIK, 'uint' isn't a
standard type at all.  You can use uint32 (BSD-style, also used
by PostgreSQL) or uint32_t (C99, <inttypes.h>).

--
Peter Eisentraut   peter_e@gmx.net   http://funkturm.homeip.net/~peter


pgsql-patches by date:

Previous
From: Marko Kreen
Date:
Subject: Re: encode in base code
Next
From: Damien Clermonté
Date:
Subject: [PATCH] Patch to make pg_hba.conf handle virtualhost access control and samehost keyword