From: erik quanstrom <quanstro@quanstro.net>
To: fernanbolando@mailc.net, 9fans@9fans.net
Subject: Re: [9fans] Updating an old port . Warning! long lines of code
Date: Sun, 29 Jun 2008 09:38:11 -0400 [thread overview]
Message-ID: <8e22b4f51586172d72e55a8b895fead1@quanstro.net> (raw)
In-Reply-To: <1d5d51400806290432h58b60e4cm75936664c988d6a3@mail.gmail.com>
> /usr/fernan/tmp/scm/sys.c:628[sys.c:3613] initialization of incompatible
> pointers: sfptob
> IND FUNC(INT, IND STRUCT _7_) INT and IND FUNC(OLD, INT, LONG) INT
> /usr/fernan/tmp/scm/sys.c:629[sys.c:3614] initialization of incompatible
> pointers: sfptob
> IND FUNC(IND CONST CHAR, IND STRUCT _7_) INT and IND FUNC(OLD, IND CHAR,
> LONG) INT
in the first case, you're trying to assign
pointers of these types:
IND FUNC(INT, IND STRUCT _7_) INT
IND FUNC(OLD, INT, LONG) INT
these kenc's internal representation for
int (*)(int, struct _7_*);
int (*)(int, long); /* pre-ansi declaration */
so the problem here is that you're mixing a pointer to
a structure with a long.
similarly,
IND FUNC(IND CONST CHAR, IND STRUCT _7_) INT
IND FUNC(OLD, IND CHAR, LONG) INT
is
int (*)(const char*, struct _7_*);
int (*)(char*, long); /* pre-ansi declaration */
struct _7_ must be FILE, and the two functions must be fputc
fputs. (but you knew that.) so the solution would be to clean up the
declaration of sfputc and sfputs.
- erik
prev parent reply other threads:[~2008-06-29 13:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-29 11:32 Fernan Bolando
2008-06-29 11:38 ` Pietro Gagliardi
2008-06-29 13:11 ` Fernan Bolando
2008-06-29 13:38 ` erik quanstrom [this message]
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=8e22b4f51586172d72e55a8b895fead1@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=fernanbolando@mailc.net \
/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.
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).