diff options
| author | Guido van Rossum <guido@python.org> | 1997-09-03 00:09:26 (GMT) |
|---|---|---|
| committer | Guido van Rossum <guido@python.org> | 1997-09-03 00:09:26 (GMT) |
| commit | 15a40394b0c21829ba9afbb739b2038b8211dabe (patch) | |
| tree | 007e934a360eeac8e87c76c0327d960db81c5fb4 /Doc/lib/libcode.tex | |
| parent | 2d30840b92d19f2229da75f47a5c7e8cbd254981 (diff) | |
| download | cpython-15a40394b0c21829ba9afbb739b2038b8211dabe.zip cpython-15a40394b0c21829ba9afbb739b2038b8211dabe.tar.gz cpython-15a40394b0c21829ba9afbb739b2038b8211dabe.tar.bz2 | |
Fix the bug Jeremy was experiencing: both the close() and the
dealloc() functions contained code to free/DECREF the buffer
(there were differences between I and O objects but the logic bug was
the same). Fixed this be setting the buffer pointer to NULL and
testing for that. (This also makes it safe to call close() more than
once.)
XXX Worry: what if you try to read() or write() once the thing is
closed?
Diffstat (limited to 'Doc/lib/libcode.tex')
0 files changed, 0 insertions, 0 deletions