[Chicken-janitors] Re: #493: set! returns its value when compiled

[Chicken Trac]

#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 felix):

 Replying to [comment:2 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.

 Then this is about `display`, not `set!`?

-- 
Ticket URL: <http://bugs.call-cc.org/ticket/493#comment:3>
Chicken Scheme <http://www.call-with-current-continuation.org/>
Chicken Scheme is a compiler for the Scheme programming language.