From: C H Forsyth <forsyth@vitanuova.com>
To: 9fans@9fans.net
Subject: Re: [9fans] APE: a further note.
Date: Sat, 17 Apr 2010 18:09:15 +0100 [thread overview]
Message-ID: <80c5b75909ab54c1c7cc4d629e1c62f9@vitanuova.com> (raw)
In-Reply-To: <b89b3bf8af504576a2d3a9a1d126d3ab@quintile.net>
> -T is great. But Python can't be built with it. Python explicitly
> creates functions with type signatures that don't match and this makes
> -T very unhappy.
the examples i had to fix (that didn't simply require
#pragma incomplete) were errors, for instance something like the following:
one function expecting a value in the middle
of a structure that was #ifdef'd out for another function's compilation,
because different #defines were in scope.
next prev parent reply other threads:[~2010-04-17 17:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 18:26 tlaronde
2010-04-15 18:30 ` erik quanstrom
2010-04-15 18:51 ` Federico G. Benavento
2010-04-15 18:57 ` erik quanstrom
2010-04-16 9:20 ` ron minnich
2010-04-16 9:36 ` Steve Simon
2010-04-17 17:09 ` C H Forsyth [this message]
2010-04-16 12:04 ` erik quanstrom
2010-04-16 7:27 ` tlaronde
2010-04-16 12:15 ` erik quanstrom
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=80c5b75909ab54c1c7cc4d629e1c62f9@vitanuova.com \
--to=forsyth@vitanuova.com \
--cc=9fans@9fans.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).