http://bugs.squeak.org/view.php?id=7733

2013/1/30 Eliot Miranda <eliot.miranda at gmail.com>:
>
> Personally I think it's important.  But I want to hear form others whether
> they find the hack I proposed acceptable or not.
>> > On Mon, Jan 21, 2013 at 3:51 PM, tim Rowledge <tim at rowledge.org> wrote:
>> >>
>> >>
>> >> On 21-01-2013, at 3:48 PM, Eliot Miranda <eliot.miranda at gmail.com>
>> >> wrote:
>> >> >
>> >> > Alas it bites at a slightly higher-level than that also.  Yes, the
>> >> > decoupling of positioning and reading is a problem for thread-safety.
>> >> > But
>> >> > so is the single buffer and the single position.  e.g. if one were to
>> >> > call
>> >> > your unified primitive below to fill the buffer that wouldn't prevent
>> >> > another thread reading at a different position into the same buffer
>> >> > and
>> >> > trashing the contents from the POV of the first thread. Since the
>> >> > programming tools are essentially single-threaded it's not *that* bad
>> >> > a
>> >> > problem, unless you're debugging source access (I *think*).
>> >>
>> >> Gotta start somewhere. Bottom is often good. Then other people can
>> >> build
>> >> upon that.
>> >
>> >
>> > Sure, but can't solve the immediate problem this way because it takes
>> > time
>> > for a VM change to percolate through.
>> > --
>> > best,
>> > Eliot
>> >
>> >
>> >
>
>
>
>
> --
> best,
> Eliot