Closed port giving incorrect error about type instead of about being closed
Bug #178385 reported by
Derick Eddington
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ikarus Scheme |
Fix Released
|
Medium
|
Abdulaziz Ghuloum |
Bug Description
Ikarus Scheme version 0.0.2patched+ (revision 1284, build 2007-12-23)
Copyright (c) 2006-2007 Abdulaziz Ghuloum
> (define p #f)
> (call-with-
(lambda (op) (set! p op)))
> p
#<output-port "blah.hoho">
> (textual-port? p)
#t
> (write 123 p)
Unhandled exception
Condition components:
1. &assertion
2. &who: write-char
3. &message: "not a textual port"
4. &irritants: (#<output-port "blah.hoho">)
Changed in ikarus: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed in revision 1285.
Ikarus Scheme version 0.0.2patched+ (revision 1285, build 2007-12-23)
Copyright (c) 2006-2007 Abdulaziz Ghuloum
> (define p #f) output- file "blah.hoho"
> (call-with-
(lambda (op) (set! p op)))
> p
#<output-port "blah.hoho">
> (write 123 p)
Unhandled exception
Condition components:
1. &assertion
2. &who: write
3. &message: "port is closed"
4. &irritants: (#<output-port "blah.hoho">)
> (write-char #\a p)
Unhandled exception
Condition components:
1. &assertion
2. &who: write-char
3. &message: "port is closed"
4. &irritants: (#<output-port "blah.hoho">)
> (put-char p #\a)
Unhandled exception
Condition components:
1. &assertion
2. &who: put-char
3. &message: "port is closed"
4. &irritants: (#<output-port "blah.hoho">)
> ^D