eliminate NS_BASE_STREAM_EOF

VERIFIED FIXED in M11

Status

()

Core
Networking
P3
normal
VERIFIED FIXED
18 years ago
18 years ago

People

(Reporter: Warren Harris, Assigned: Warren Harris)

Tracking

Trunk
x86
Windows NT
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

18 years ago
Brendan and I decided that EOF should be denoted by the read/write-count
out-parameter being 0, not a success or failure nsresult code. This will allow
JS authors to call Read/Write on streams with less overhead.

Also, NS_BASE_STREAM_WOULD_BLOCK should become a failure code. This will cause
an exception in JS, and require callers to deal with latent streams more
explicitly.
(Assignee)

Updated

18 years ago
Target Milestone: M11
(Assignee)

Comment 1

18 years ago
Fixes in my tree.
(Assignee)

Updated

18 years ago
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
(Assignee)

Comment 2

18 years ago
done

Updated

18 years ago
Status: RESOLVED → VERIFIED

Comment 3

18 years ago
Bulk move of all Necko (to be deleted component) bugs to new Networking

component.
Depends on: 129492
You need to log in before you can comment on or make changes to this bug.