Fwd: Communicating Event Loops

I think that this would be the first mail to smalltalk-research

Begin forwarded message:


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

On 3 February 2010 10:33, Stéphane Ducasse <[hidden email]> wrote:
> I think that this would be the first mail to smalltalk-research
>
Err, what you mean?

All i could say, that this scheme already discussed on squeak-dev
couple of years ago... This is exactly the way where i think we should
eventually go to. So what is new about it?



--
Best regards,
Igor Stasenko AKA sig.

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

On Feb 3, 2010, at 12:34 PM, Igor Stasenko wrote:

> On 3 February 2010 10:33, Stéphane Ducasse <[hidden email]> wrote:
>> I think that this would be the first mail to smalltalk-research
>>
> Err, what you mean?
>
> All i could say, that this scheme already discussed on squeak-dev
> couple of years ago... This is exactly the way where i think we should
> eventually go to. So what is new about it?


Do we request that only new things are discussed on Smalltalk-research?

LOOM is very old, too... in general, there is a lot of wisdom espececially in old
papers. Partly because it was possible to publish easily cool ideas without having
to have every open question already answered.
... the good old days :-)

The problem is that if new people start, they have to read old papers. Else
how can they learn? There are even things that experienced people don't know.
For example, because they did not do research in this direction in the past.

        Marcus

--
Marcus Denker  -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Igor

You know Concurrent Smalltalk was certainly like that too.
Now my point is that this is good to share ideas that there are old or not.
Already discussed or not.
For example I would like to see the cost of it at the level of the GC.

Stef


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

On 3 February 2010 14:27, Stéphane Ducasse <[hidden email]> wrote:
> Igor
>
> You know Concurrent Smalltalk was certainly like that too.
> Now my point is that this is good to share ideas that there are old or not.
> Already discussed or not.

Yes, that's why i asked , because i didn't understood your message.

> For example I would like to see the cost of it at the level of the GC.
>

The main problem here, as also mentioned in discussion, is how GC
should deal with far references, i.e.
how to determine correctly when object which is referenced by some far
ref become garbage.
As for the rest of it, its not any different from usual approach: GC
could sweep a single vat space at any moment it wants,
regardless of what other vats currently doing.



--
Best regards,
Igor Stasenko AKA sig.

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

>
>> Igor
>>
>> You know Concurrent Smalltalk was certainly like that too.
>> Now my point is that this is good to share ideas that there are old or not.
>> Already discussed or not.
>
> Yes, that's why i asked , because i didn't understood your message.

So I repeat it.
Right now on my desktop when I open any Smalltalk I still have some old ideas moving inside.
And we would like to create a different world in which even old ideas that were discussed
long time ago but never arrived to my current desktop could be discussed.
If we want people to invent the future, they should at least know the past and gets also ideas
from others.

>> For example I would like to see the cost of it at the level of the GC.
>>
>
> The main problem here, as also mentioned in discussion, is how GC
> should deal with far references, i.e.
> how to determine correctly when object which is referenced by some far
> ref become garbage.

May be a lifecycle like in Corba solution is needed at the level of each vat.

> As for the rest of it, its not any different from usual approach: GC
> could sweep a single vat space at any moment it wants,
> regardless of what other vats currently doing.

Stef
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project