27 Jul
2009
27 Jul
'09
4:21 p.m.
On Mon, Jul 27, 2009 at 10:02:28AM -0400, Jorge Arellano Cid wrote:
On Sun, Jul 26, 2009 at 06:53:11PM +0200, Joerg Sonnenberger wrote:
The results for C++ are not different as far as ctype(3) are concerned.
It looks like it's the compiler the one that decides [1]. When porting dillo to minix3 I had this problem.
Yes, what I said is that it is irrelevant whether you have C or C++ for this. The argument for ctype(3) macros must always be either EOF or 0..255. At least on NetBSD you will also get a compiler warning when using (signed) char. Joerg