Overview
Comment: | Remove - close from OFStream protocol. The reason is that closing a file isn't too useful, because an OFFile object can't be reused, whereas an OFTCPSocket can. So only the OFTCPSocket should have closed. Plus, we don't need to handle the case that someone tried to read from / write to a closed OFFile. |
---|---|
Downloads: | Tarball | ZIP archive | SQL archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA3-256: |
c83137e7cd31a6a7878c620905165f76 |
User & Date: | js on 2008-12-11 13:43:35 |
Other Links: | manifest | tags |
Context
2008-12-11
| ||
13:53 | Allow initialization without NItems for OFReadOrWriteFailedException. check-in: 5168142abe user: js tags: trunk | |
13:43 |
Remove - close from OFStream protocol. The reason is that closing a file isn't too useful, because an OFFile object can't be reused, whereas an OFTCPSocket can. So only the OFTCPSocket should have closed. Plus, we don't need to handle the case that someone tried to read from / write to a closed OFFile. check-in: c83137e7cd user: js tags: trunk | |
2008-12-10
| ||
20:53 | Fix FIXMEs in OFString; new exception. check-in: 4f7378978c user: js tags: trunk | |
Changes
Modified src/OFExceptions.h from [d80b50b5d0] to [7dd17fb763]. [diff]
Modified src/OFFile.m from [0b28d6c4b4] to [e3b833eee4]. [diff]
Modified src/OFStream.h from [a9317063cc] to [7bc3490907]. [diff]
Modified src/OFTCPSocket.h from [01c69a8231] to [dc54bd8b6a]. [diff]