[Python-Dev] float atime/mtime/ctime - a bad idea? (original) (raw)
Barry A. Warsaw barry@python.org
Wed, 16 Oct 2002 09:07:23 -0400
- Previous message: [Python-Dev] float atime/mtime/ctime - a bad idea?
- Next message: [Python-Dev] float atime/mtime/ctime - a bad idea?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
"MvL" == Martin v Loewis <martin@v.loewis.de> writes:
>> +1 on the latter idea. Since the st_mtime, st_atime, and
>> st_ctime attributes, and the tuple-ish API are documented as
>> returning ints, I think you shouldn't change that. Provide
>> different field names for float values, e.g. f_mtime, f_ctime,
>> f_atime, or maybe just mtime, atime, and ctime... ?
MvL> The previous suggestion was st_mtimef, st_ctimef, ...
Names which differ by one character at the end of the name are error prone, IME. Plus it makes stuff like dabbrev-expand harder to use. :)
-Barry
- Previous message: [Python-Dev] float atime/mtime/ctime - a bad idea?
- Next message: [Python-Dev] float atime/mtime/ctime - a bad idea?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]