agora inbox for postgres@postgres.berkeley.edu  

help / color / mirror / Atom feed

From: Kai Petzke <wpp@marie.physik.tu-berlin.de>
To: Corey Sweeney <corey@bbs.xnet.com>
Cc: linux-postgres@native-ed.bc.ca
Subject: Re: postgres v4r2 for linux
Date: Sat, 9 Jul 1994 23:08:00 +0200 (MET DST)
Message-ID: <9407100853.AA27673@marie.physik.tu-berlin.de> (raw)
In-Reply-To: <9407030438.AA04e2p@bbs.xnet.com>

Corey Sweeney (corey@bbs.xnet.com) said:

> Hey! it finnally happened.  Now we can get some real work done :)
> 
> Ok here's my proposal for the plan.  (it's the same plan as before, with a
> couple of additions of my own)
> 
> 
> ok, first we get it working with -Wall.  (without warnings)

I think so, too.  I hope, that we can parallelize this task.
Everybody who wants to help catches a directory, and tries to
get all the files in it compiled without warnings.

I want to do the beginning: I choose ~postgres/src/backend/planner.

There are two problems, though:

a) Casts to a superclass.  C does no implicit casting from a
   subclass to a superclass, C++ does.  To turn of the C compiler
   warnings would require to add casts, which are bad for C++,
   though, because they inhibit type checking.

   I see the following alternatives:
   - ignore the C warnings about illegal pointers passed to functions.
   - add the casts, as a macro call.  Eg:
     #ifdef  __cplusplus
     #define super(x) (x)		/* C - Version */
     #define super(x) 			/* C++ - Version */
     #endif

     foo(super(Node) arg1, arg2);

     That would call the function foo() with arg1 converted to type
     Node (the base type of the Postgres), and arg2 unmodified.

b) Communication.  Does anybody know of a method to keep several
   world wide distributed versions of an RCS log identical?

   I guess, not, so we will have to go for something less
   sophisticated.  I can volunteer to collect patches.  E-mail is
   quite reliable here, despite the ftp problems.  The bad thing
   is for modifications to header files, because they affect
   everybody's work.  Maybe patches to headers should be posted
   to the list immediately.




Kai

reply

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: postgres@postgres.berkeley.edu
  Cc: wpp@marie.physik.tu-berlin.de, corey@bbs.xnet.com, linux-postgres@native-ed.bc.ca
  Subject: Re: postgres v4r2 for linux
  In-Reply-To: <9407100853.AA27673@marie.physik.tu-berlin.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox