[Pharo-project] pharo vision

Stéphane Ducasse stephane.ducasse at inria.fr
Mon Jan 30 14:44:19 EST 2012


in fact I wanted to send it to the mailing list of our team because I wanted to gather feedback before sending it to 
the mailing-list to ask for another set of feedback.

So I will finish it now :)


On Jan 30, 2012, at 5:46 PM, dimitris chloupis wrote:

> Thanks stef for this . The document informed me  of things I was not aware of and now after reading it I like Pharo even more . 
> From: Henrik Johansen <henrik.s.johansen at veloxit.no>
> To: Pharo-project at lists.gforge.inria.fr 
> Sent: Monday, 30 January 2012, 18:10
> Subject: Re: [Pharo-project] pharo vision
> On Jan 30, 2012, at 9:24 14AM, Stéphane Ducasse wrote:
>> <main.pdf>
> Nice!
> Some comments on the parts I'm most familiar with:
> 3.2
> I agree, the nice parts in FS to me is the path manipulation API.
> Going back to pure ANSI-streams as provided by FSFileStream is not really an option.
> Since it's a clean break from FileDirectory & friends though, it might be the perfect time to introduce XTreams; -or it might be too much hassle to have to change both parts in existing code at once.
> A good compromise would be to make it pluggable, using the existing Standard/MultiByteFileStreams by default, but making XStreams pluggable (on a use--by-use basis, so you can write new code with XStreams while maintaining old code where you have only had time to rewrite the path handling)
> 3.3
> "Using ephemerons we can then simplify the Announcement and make sure that clients do not have to worry about weak or not registration."
> You still have to worry about whether you want weak or strong registration.
> "Do I have strict requirements for when the announcement should stop being delivered in relation to subscriber lifespan?" is still a valid question.
> What you don't have to worry about, is what _type_ of subscription (action blocks or message sends), you are allowed to use when registering weakly.
> Ends with "In addition, " then nothing :)
> Cheers,
> Henry

More information about the Pharo-dev mailing list