Date: Sun, 5 Mar 2000 15:48:55 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Martin Str|mberg <ams AT ludd DOT luth DOT se>
cc: DJGPP-WORKERS <djgpp-workers AT delorie DOT com>
Subject: Re: iso646.h and some questions
In-Reply-To: <200003051136.MAA03256@father.ludd.luth.se>
Message-ID: <Pine.SUN.3.91.1000305154441.2134B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 5 Mar 2000, Martin Str|mberg wrote:

> Here's the (standard) file iso646.h.

Thanks!

> Some files #defines constants several times. E. g. NULL is in wchar.h
> and in stddef.h.

No, wchar.h simply includes stddef.h.  So there's no problem in that 
case.

> Should those #defines be wrapped in #ifndef/#endif?

It should be decided on a case by case basis.  Please tell the specifics 
of each and every case like that.

> Shall I send header files containing new functions, so other people
> can start implementing them?

IMHO, the prototypes should be added to the headers only *after* the
functions are already available.  Otherwise, we might get conflicts (when
building a package that provides its private versions of the missing
functions), and some people think that the existence of a prototype is an
evidence that the function is provided by the library.