print statement and multithreading
Paul Duffin
pduffin at hursley.ibm.com
Fri Aug 25 11:59:54 EDT 2000
More information about the Python-list mailing list
Fri Aug 25 11:59:54 EDT 2000
- Previous message (by thread): print statement and multithreading
- Next message (by thread): print statement and multithreading
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Aahz Maruch wrote: > > In article <39A69194.A9B1131A at hursley.ibm.com>, > Paul Duffin <pduffin at hursley.ibm.com> wrote: > >Tim Peters wrote: > >> > >> "ANSI C" is universally taken to mean the version of the language as defined > >> by the American National Standards Institute, working committee X3J11, in > >> 1989, and as amended by a Technical Corrigendum sometime in the mid-90's. > >> Before late 1999, there was no ambiguity here as that was the *only* C > >> standard. > > > >While that may be true for people who are used to working with > >standards in there raw form I dount that the majority of people > >developing open source software would immediately think of the above > >when you said "ANSI C". > > > >They are more likely to think of the 2nd Edition of K&R. > > Yes, and that's what K&R2 is based on. Direct lineage. So is K&R 2nd Edition the definitive definition of C that Python will use ?
- Previous message (by thread): print statement and multithreading
- Next message (by thread): print statement and multithreading
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list