This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author davidsarah
Recipients davidsarah
Date 2010-02-18.01:36:37
SpamBayes Score 3.52125e-06
Marked as misclassified No
Message-id <1266457000.48.0.280791340247.issue7952@psf.upfronthosting.co.za>
In-reply-to
Content
Correction: when input is followed by output, the call needed to avoid undefined behaviour has to be to a "file positioning function" (fseek, fsetpos, or rewind, but not fflush). Since fileobject.c does not use wide I/O operations, it should be sufficient to use _portable_fseek(fp, 0, SEEK_SET).

(_portable_fseek may call some function that is not strictly defined to be a "file positioning function", e.g. fseeko() or fseek64(). However, it would be insane for a stdio implementation not to treat those as being file positioning functions as far as the intent of the C or POSIX standards is concerned.)
History
Date User Action Args
2010-02-18 01:36:40davidsarahsetrecipients: + davidsarah
2010-02-18 01:36:40davidsarahsetmessageid: <1266457000.48.0.280791340247.issue7952@psf.upfronthosting.co.za>
2010-02-18 01:36:38davidsarahlinkissue7952 messages
2010-02-18 01:36:37davidsarahcreate