Hi,

At Wed, 30 Jul 2003 11:19:54 +0900,
the_rev_dharma_roadkill wrote:
> 29 warnings like this (signed/unsigned ptr), down from 95 in preview4:
> cc: Warning: io.c, line 868: In the initializer for p, the referenced
> type of th
> e pointer value "((f)->_ptr)" is "unsigned char", which is not
> compatible with "
> const char" because they differ by signed/unsigned attribute.
> (ptrmismatch1)
>             const char *p = READ_DATA_PENDING_PTR(f);
> ----------------------------^
> I'm not very worried about those.

How is FILE_READPTR defined in config.h?

> A warning you said could be ignored:
> cc: Warning: stubs.c, line 94: Source file does not contain any
> declarations. (e
> mptyfile)
> #endif
> ------^

Although the warning is definitely OK to ignore, does inserting
this line at the top suppress it?

extern int ruby_tcltk_stubs();

Or just comments suppress it?

> A warning due to _XOPEN_SOURCE_EXTENDED not set in curses.h, probably
> not very important and dangerous to fix:
> cc: Warning: curses.c, line 434: In this statement, "keyname(...)" of
> type "int"
> , is being converted to "pointer to const char". (cvtdiftypes)
>   name = keyname(NUM2INT(c));
> --^

Agree.

-- 
Nobu Nakada