www.delorie.com/archives/browse.cgi | search |
Date: | Sun, 16 May 1999 13:34:14 +0300 (IDT) |
From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
X-Sender: | eliz AT is |
To: | DJ Delorie <dj AT delorie DOT com> |
cc: | djgpp-workers AT delorie DOT com |
Subject: | Re: wctype.h and ctype.h |
In-Reply-To: | <199905131737.NAA09945@envy.delorie.com> |
Message-ID: | <Pine.SUN.3.91.990516133351.26252C-100000@is> |
MIME-Version: | 1.0 |
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 |
On Thu, 13 May 1999, DJ Delorie wrote: > It wrong for wctype.h to include inlines/ctype.ha. It should include > inlines/wctype.ha if it has inline functions. Why can't wctype.h use inlines/ctype.ha, if it needs it? Does the standard preclude it? If not, we simply need to find a way to avoid the conflict. > The user should be able > to include any headers in any order and expect them to work correctly. How about including ctype.h from wctype.h? Will that be good enough?
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |