Date: Sun, 16 May 1999 09:18:38 -0400
Message-Id: <199905161318.JAA17119@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: eliz AT is DOT elta DOT co DOT il
CC: djgpp-workers AT delorie DOT com
In-reply-to: <Pine.SUN.3.91.990516133351.26252C-100000@is> (message from Eli
	Zaretskii on Sun, 16 May 1999 13:34:14 +0300 (IDT))
Subject: Re: wctype.h and ctype.h
References:  <Pine DOT SUN DOT 3 DOT 91 DOT 990516133351 DOT 26252C-100000 AT is>
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> Why can't wctype.h use inlines/ctype.ha, if it needs it?  Does the
> standard preclude it?

The inlines directory was added as a way to manage complexity and keep
the regular includes from getting messy.  <foo.h> should use
<inlines/foo.ha> for inlined ANSI functions, or <inlines/foo.hp> for
inlined POSIX functions, etc.

> How about including ctype.h from wctype.h?  Will that be good enough?

That would be the right way to do it.  Note that the user is allowed
to disable all inline functions (say, for debugging) with a single -D.
(um, -D__dj_ENFORCE_FUNCTION_CALLS) Please test these headers with
that option to make sure there are no hidden dependencies.

If needed, <inlines/ctype.ha> and <inlines/wctype.ha> can share a
common <inlines/...> header if they have stuff in common, but be
careful to allow including both headers in either order.