[squeak-dev] re: What is the contract of SocketStream>>#next:?

Chris Muller asqueaker at gmail.com
Thu Oct 9 15:49:09 UTC 2014


On Thu, Oct 9, 2014 at 3:19 AM, Craig Latta <craig at netjam.org> wrote:
>
>> I feel I should be able to write:
>>
>>   header := mySocketStream next: 4
>>
>> and not have to check the length of header before I access it.
>
>      Yeah, Squeak socket support is broken here (and a lot of other
> places), I'd say.

That might be overstating it.  I've only ever seen the issue under
very heavy load, so there might be a timing bug in the SocketStream
wrapper.

I was just trying to confirm the contract of this method with y'all so
I could proceed with scrutinizing it on that basis.

>
>
> -C
>
> --
> Craig Latta
> netjam.org
> +31 6 2757 7177 (SMS ok)
> + 1 415 287 3547 (no SMS)
>
>


More information about the Squeak-dev mailing list