Michael Rueger <m.rueger at acm.org> wrote:
> > Anyway,with the pause in place I later get funky results from
> > SocketStream>>upTo:. Your SocketSteam is obviously not "compatible" with
> > the one in Comanche. I have code that does this:
> > 
> > getResponse
> > 	"Get the next line from the server."
> > 	| nextLine |
> > 	nextLine _ stream upTo: Character lf.
> > 	stream next.
> > 	^nextLine
> 
> the stream next shouldn't be there, "standard" upTo: semantic is to skip 
> the delimiter:

Hmmm, right. I can perhaps test and see if it get's better. Right now I
have gotten Sqcvs working with Comanche as a prerequisite. Will do for a
little while.

How about that timeout? Any clues? Tested on WinXP with latest VM from
SF.
 
> Answer a subcollection from the current access position to the
> 	occurrence (if any, but not inclusive) of anObject
> 
> > ...and this seems to result in a String with 10 LFs in it. Hmmm, haven't
> > looked deeper here so I can't give more feedback right now.
> 
> Hmm, are using the stream as binary or ascii?

Hmm, good question. Can check that too. But it will be later in the
weekend I think.

> Michael

regards, Göran