Gareth McCaughan wrote:
It's valid C99, meaning this is an unsigned long long.
since when does Python require C99 compilers?
/F
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
On Tuesday 2005-08-23 16:51, Fredrik Lundh wrote:
Gareth McCaughan wrote:
It's valid C99, meaning this is an unsigned long long.
since when does Python require C99 compilers?
/F
It doesn't, of course, and I hope it won't for a good while.
I was just responding to this:
| Perhaps OS
[Gareth]
It's valid C99, meaning this is an unsigned long long.
/F
since when does Python require C99 compilers?
Except from PEP 7:
Use ANSI/ISO standard C (the 1989 version of the standard).
___
Python-Dev mailing list
Python-Dev@python.org
Fredrik Lundh [EMAIL PROTECTED] writes:
Gareth McCaughan wrote:
It's valid C99, meaning this is an unsigned long long.
since when does Python require C99 compilers?
Well, it doesn't, but Raymond was suggesting the code was GCC
specific, or something.
Cheers,
mwh
--
Check out the
On Tue, 2005-08-23 at 11:51, Fredrik Lundh wrote:
Gareth McCaughan wrote:
It's valid C99, meaning this is an unsigned long long.
since when does Python require C99 compilers?
Why, since Python 3.0 of course! wink
-Barry
signature.asc
Description: This is a digitally signed message