[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Chicken-janitors] Re: #493: set! returns its value when compiled
From: |
Chicken Trac |
Subject: |
[Chicken-janitors] Re: #493: set! returns its value when compiled |
Date: |
Wed, 09 Feb 2011 16:47:05 -0000 |
#493: set! returns its value when compiled
-----------------------+----------------------------------------------------
Reporter: zbigniew | Owner:
Type: defect | Status: new
Priority: minor | Milestone: 4.7.0
Component: compiler | Version: 4.6.x
Resolution: | Keywords:
-----------------------+----------------------------------------------------
Comment(by zbigniew):
The inconsistency. It seems the core relies on a (void) return in at
least one place (tcp). Once in a while display will return the empty
string instead of void. This is disconcerting, because if you are at the
REPL making TCP connections, 1 out of every 10 displays might return a
value, which makes the user wonder what happened. Therefore I consider
this to violate the principle of least surprise. Placing a (void) at the
end of the output-port writing procedure is a quick way to quiet this
behavior.
--
Ticket URL: <http://bugs.call-cc.org/ticket/493#comment:2>
Chicken Scheme <http://www.call-with-current-continuation.org/>
Chicken Scheme is a compiler for the Scheme programming language.