[Python-Dev] xreadlines : readlines :: xrange : range
Guido van Rossum
Wed, 03 Jan 2001 09:56:31 -0500
> Apparently getc_unlocked() is in the Single Unix spec. Not sure how
> widespread that is -- do Linux developers pay attention to this
> standard at all? According to the webpage it's (c) 1997.
Erno Kuusela gave me some more info about this; glibc supports it.
I did a quick test which suggests that it is a lot faster than regular
getc() -- on a small test file it's actually faster than GNU
getline(), even with the proper flockfile() / funlockfile() calls.
(The test file was 6Mb -- 10 copies of /etc/termcap, which has short
lines -- avg 43 chars.)
This together with Tim's Win32x specific hacks might be the best we
can do for get_line(). However, raw xreadlines is still almost twice
as fast, so it's still under consideration.
Maybe MS supports a similar unlocked getc macro, and a separate
primitive to lock/unlock a file? That would allow more unified code.
(Quick research shows that it exists, but only in internal form. We
could probably call _lock_file() and _unlock_file(), and define our
own getc_lk(), protected by the proper set of macros. This could all
be presented by config.h as flockfile(), funlockfile(), and
--Guido van Rossum (home page: http://www.python.org/~guido/)