Anonymous | Login | 12-09-2019 10:50 UTC |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | |||||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
0007167 | [Squeak] System | major | always | 08-29-08 11:46 | 09-19-09 20:55 | |||||||
Reporter | norbertf | View Status | public | |||||||||
Assigned To | ||||||||||||
Priority | normal | Resolution | open | |||||||||
Status | feedback | Product Version | 3.10 | |||||||||
Summary | 0007167: ReadWriteStream opened with "on: aCollection" always has readLimit 0 | |||||||||||
Description |
Example: "(ReadWriteStream on: 'abc') next" returns nil Encountered this when trying in vain: "Form fromBinaryStream: (RWBinaryOrTextStream on: file contents)" The reason is that ReadWriteStream is a subclass of WriteStream which does "readLimit := 0" in its WriteStream>on: method. my fix is: ----------- 'From Squeak3.10-basic of 26 May 2008 [latest update: 0007160] on 29 August 2008 at 1:27:05 pm'! !ReadWriteStream methodsFor: 'private' stamp: 'nf 8/29/2008 13:26'! on: aCollection 'fixing the bug that a ReadWriteStream had the readLimit set to 0 from the WriteStream>on: method' super on: aCollection. readLimit := aCollection size! ! ----------- After fixing this I saw immediately one side effect: A real time clock in a seaside interface showed extraneous garbage characters at the end. I suspect this is another bug. |
|||||||||||
Additional Information | A cursory glance at references to ReadWriteStream seems to indicate that most uses are for writing rather than reading which would explain why this bug was not noticed before. | |||||||||||
Attached Files | ||||||||||||
|
Mantis 1.0.8[^]
Copyright © 2000 - 2007 Mantis Group
49 total queries executed. 36 unique queries executed. |