zsh-workers
 help / color / mirror / code / Atom feed
From: Clint Adams <clint@zsh.org>
To: Peter Stephenson <pws@csr.com>
Cc: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: Termcap saga again
Date: Tue, 8 May 2001 09:34:04 -0400	[thread overview]
Message-ID: <20010508093404.A20808@dman.com> (raw)
In-Reply-To: <Tc0a88d01536464c3f9@mailsweeper01.cambridgesiliconradio.com>; from pws@csr.com on Tue, May 08, 2001 at 10:36:59AM +0100

> SunOS 5.8 is giving me
> 
> ../../../Src/Modules/termcap.c: In function `scantermcap':
> ../../../Src/Modules/termcap.c:327: `boolcodes' undeclared (first use in this function)
> ../../../Src/Modules/termcap.c:327: (Each undeclared identifier is reported only once
> ../../../Src/Modules/termcap.c:327: for each function it appears in.)
> ../../../Src/Modules/termcap.c:336: `numcodes' undeclared (first use in this function)
> ../../../Src/Modules/termcap.c:345: `strcodes' undeclared (first use in this function)

I don't get that from Forte C; these are the only warnings I get.

"parse.c", line 1911: warning: end-of-loop code not reached
"parse.c", line 1973: warning: end-of-loop code not reached
"parse.c", line 1983: warning: end-of-loop code not reached
"/usr/include/iso/stddef_iso.h", line 73: warning: macro redefined: offsetof
"termcap.c", line 132: warning: argument #3 is incompatible with prototype:
        prototype: pointer to function(char) returning int : "/usr/include/term.h", line 1205
        argument : pointer to function(int) returning int
"termcap.c", line 135: warning: improper pointer/integer combination: arg #1
"termcap.c", line 135: warning: argument #3 is incompatible with prototype:
        prototype: pointer to function(char) returning int : "/usr/include/term.h", line 1205
        argument : pointer to function(int) returning int
"terminfo.c", line 96: warning: argument #3 is incompatible with prototype:
        prototype: pointer to function(char) returning int : "/usr/include/term.h", line 1205
        argument : pointer to function(int) returning int

HAVE_CURSES_H is being defined.

On the other hand, I get what you get with gcc 2.95.2.

> which I find a bit alarming.  However, the arg 3 messages are because I
> have `int (*)(char)' as that argument's type whereas we're using `int
> (*)(int)', while the arg 1 message appears because tgoto is only defined if
> __STDC__ isn't.  So this doesn't seem really to be our fault

We could test for this and provide char (*)(int) and int (*)(char) versions
of putraw/putshout, but it hardly seems worth it.


  reply	other threads:[~2001-05-08 13:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-08  9:36 Peter Stephenson
2001-05-08 13:34 ` Clint Adams [this message]
2001-05-08 14:35 ` Bart Schaefer
2001-05-08 14:56   ` Peter Stephenson
2001-05-08 15:14     ` Bart Schaefer
2001-05-08 16:23       ` Peter Stephenson
2001-05-08 18:01         ` Andrej Borsenkow
2001-05-08 18:07         ` Bart Schaefer
2001-05-08 18:25           ` Peter Stephenson
2001-05-09  5:03             ` Bart Schaefer
2001-05-09  5:19               ` Andrej Borsenkow
2001-05-09  5:32               ` PATCH: " Andrej Borsenkow
2001-05-09  5:42                 ` Bart Schaefer
2001-05-09  5:37               ` PATCH (the last?) " Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010508093404.A20808@dman.com \
    --to=clint@zsh.org \
    --cc=pws@csr.com \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).