scsh-hackers
[Top] [All Lists]

[Scsh-hackers] [ scsh-Bugs-432565 ] receive-message, receive-message! bu

To: noreply@sourceforge.net
Subject: [Scsh-hackers] [ scsh-Bugs-432565 ] receive-message, receive-message! bug
From: noreply@sourceforge.net
Date: Tue, 12 Jun 2001 15:26:41 -0700
List-id: Discussion among the implementors <scsh-hackers.lists.sourceforge.net>
Sender: scsh-hackers-admin@lists.sourceforge.net
Bugs item #432565, was updated on 2001-06-12 15:26
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=110493&aid=432565&group_id=10493

Category: run-time
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Brian D. Carlstrom (bdc)
Assigned to: Brian D. Carlstrom (bdc)
Summary: receive-message, receive-message! bug

Initial Comment:
From: Gary Houston <scsh-special@arglist.com>
To: scsh-bugs@zurich.ai.mit.edu             
Subject: receive-message, receive-message! bug in scsh 
0.5.3
Date: 12 Jun 2001 21:20:20 -0000

This is old, but I don't think I ever reported it to 
scsh-bugs.

receive-message! usually returns a single value, the 
number of bytes
read from a socket.  According to the manual, it's 
supposed to return
two values: the number of bytes and the remote 
address.  It does
return the two values when it gets EOF on the socket.

It's this line in generic-receive-message! that 
returns the single value:

      (if (>= i end) (- i start)

A consequence of this bug is that receive-message 
usually fails since
it calls "receive-message!" and expects to get two 
values.








----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=110493&aid=432565&group_id=10493


<Prev in Thread] Current Thread [Next in Thread>
  • [Scsh-hackers] [ scsh-Bugs-432565 ] receive-message, receive-message! bug, noreply <=