fasl-write error message wrong about textual output ports
Bug #194232 reported by
Derick Eddington
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ikarus Scheme |
Fix Committed
|
Medium
|
Abdulaziz Ghuloum |
Bug Description
`sop' is not a binary-port so fasl-write is erroring, but it is an output-port. It looks like you can just make that message be "not a binary output port".
Ikarus Scheme version 0.0.3+ (revision 1403, build 2008-02-21)
Copyright (c) 2006-2008 Abdulaziz Ghuloum
> (define-record-type my-thing (fields x))
> (define t0 (make-my-thing 123))
> (define-values (sop sop-getter) (open-string-
> (fasl-write t0 sop)
Unhandled exception
Condition components:
1. &assertion
2. &who: fasl-write
3. &message: "not an output port"
4. &irritants: (#<output-port (textual) "*string-
Changed in ikarus: | |
milestone: | none → 0.0.4 |
To post a comment you must log in.
Will fix. Thanks.