From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Fri, 16 Apr 2010 08:04:25 -0400
To: 9fans@9fans.net
Message-ID: <de4573ecff814b73a3d2e18f633b83a0@kw.quanstro.net>
In-Reply-To: <n2l13426df11004160220lfd514714hc6850ed974482cc1@mail.gmail.com>
References: <20100415182618.GA9844@polynum.com>
	<c23e52bd283ea6dfd3f37392f9fa6a04@ladd.quanstro.net>
	<n2j32d987d51004151151sc020cb7ek3b316d62cb22fef4@mail.gmail.com>
	<a5b5e502eee26a6bddfee47bb9e6b0e2@ladd.quanstro.net>
	<n2l13426df11004160220lfd514714hc6850ed974482cc1@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] APE: a further note.
Topicbox-Message-UUID: 0332163a-ead6-11e9-9d60-3106f5b1d025

On Fri Apr 16 05:23:38 EDT 2010, rminnich@gmail.com wrote:
> -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.

why would they do that?

> Just a warning: it's good to turn it on, but there are cases where it
> will lead to an error that is not an error (depending on how you
> define error).

of course the type signature is based on the c type, not the
machine type.  in the case of all supported architechtures,
long and int produce the same code.  so, for example,
-T will be unhappy if you say long and mean int,
program won't crash.  but neither will it be portable.

long is now a vestigial type.

- erik