From: Charles Forsyth <forsyth@terzarima.net>
To: fernanbolando@mailc.net, 9fans@9fans.net
Subject: Re: [9fans] How serious is incomatible type signatures?
Date: Sun, 27 Feb 2011 15:25:25 +0000 [thread overview]
Message-ID: <f8c0274652d86e3bdf8a8e0f8be5a47d@terzarima.net> (raw)
In-Reply-To: <AANLkTi=3qFhUg6bEwx8hB-MOcVvB20kQjkqWVHmGRVj1@mail.gmail.com>
>Removing -T from the compiler option seems to allow me to compile with
>no problems. The resulting compiled code seems to run just fine.
in many cases, that will be true, for instance because void* and int* are the same
size and interchangeable, and both point to something. (even then, int* and char* aren't compatible,
since they point to things of different size.)
better to fix the types, so that they both match what was intended.
it sounds as though the type of a signal handler is inconsistent.
prev parent reply other threads:[~2011-02-27 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 7:28 Fernan Bolando
2011-02-27 15:25 ` Charles Forsyth [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=f8c0274652d86e3bdf8a8e0f8be5a47d@terzarima.net \
--to=forsyth@terzarima.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).