June 2008 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] HowToContribute wiki page rewrite

by Damien Cassou

On Thu, Jun 5, 2008 at 11:31 AM, Serge Stinckwich <serge.stinckwich(a)doesnotunderstand.org> wrote: > I guess i'm not an administrator ;-) Fixed. -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

June 5, 2008

Re: [Pharo-project] About on:

by Damien Cassou

On Thu, Jun 5, 2008 at 8:52 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > > On Jun 5, 2008, at 00:27 , Bill Schwab wrote: > >> Stef, Damien, >> >> No surprise, I would argue that we proceed, and would also include a >> rename of #next to #nextOrNil and #next: to #nextAvailable:. All code in >> the image at the time should work as before. > > What would be the impact on code that is not in the image? Would all > external packages need to be adapted as well or would the current semantics > be preserved? In the case of changing 'ReadStream on: smth' to 'smth readStream' there is really nothing to change in external libraries. This change only enhance the code without changing anything. The refactoring can also be applied in some parts of the image without changing others. The change Bill proposes is completely different and I would propose to postpone it until we have more discussions and everybody agrees. There is no point in doing both at the same time. The changes are completely independent. -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

June 5, 2008

Re: [Pharo-project] About readStream on: vs readStream

by Damien Cassou

On Wed, Jun 4, 2008 at 8:36 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I was wondering why you think that ReadStream on: anObject is worse than > anObject readStream? > Because you do not hardcode ReadStream? I already gave my opinion that at least 3 times :-). Here is it again: - no more direct reference on ReadStream where it is not necessary - allows different implementation of #readStream depending on the receiver class (different collection classes can use specific streams as it is the case in Nile. In GnuSmalltalk, WriteStream>>readStream answers a ReadStream without needing copy the collection) - clarify the code: I noticed the code becomes much more readable - use a method that has been there for ages -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

June 5, 2008

Re: [Pharo-project] HowToContribute wiki page rewrite

by Serge Stinckwich

I guess i'm not an administrator ;-) 2008/6/5 Damien Cassou <damien.cassou(a)gmail.com>: > On Wed, Jun 4, 2008 at 8:07 PM, Serge Stinckwich > <serge.stinckwich(a)doesnotunderstand.org> wrote: >> How could i edit the main page ? > > Administer -> Project Summary > > -- > Damien Cassou > Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/

June 5, 2008

Re: [Pharo-project] HowToContribute wiki page rewrite

by Damien Cassou

On Wed, Jun 4, 2008 at 8:07 PM, Serge Stinckwich <serge.stinckwich(a)doesnotunderstand.org> wrote: > How could i edit the main page ? Administer -> Project Summary -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

June 5, 2008

Re: [Pharo-project] HowToContribute wiki page rewrite

by Damien Cassou

On Thu, Jun 5, 2008 at 5:10 AM, Victor Rodriguez <victorr(a)gmail.com> wrote: > On Wed, Jun 4, 2008 at 3:20 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Hi victor >> If you can, do it but >> pay attention that we will certainly use pier or cmsbox at the end. (I know >> that the current wiki is slow). > > I think it is worth to do it, since there doesn't appear to be a firm > idea on when a Pier or Cmsbox site will be ready. > > Project owners, *please* add me to the project! > >> If you do it can you mark each page of the old one with a link to the new >> one. > > Not a problem. > > Su servidor, > > VÃctor RodrÃguez. > >> Stef >> On Jun 4, 2008, at 7:58 PM, Victor Rodriguez wrote: >> >>> On Wed, Jun 4, 2008 at 1:39 PM, StÃ©phane Ducasse >>> <stephane.ducasse(a)inria.fr> wrote: >>>> >>>> Thanks so may be we should move the wiki contents to this one >>>> but more importantly the tasks. >>> >>> I'll volunteer to move the wiki pages, as long as people don't mind if >>> it takes the rest of the week to do it (I can only manage a few hours >>> per week of "free time" :-P ). >>> >>> Victor. >>> >>> ps. Please add me to the project as victorr(a)gmail.com. Done. I've added everyone for which I had a gmail email address on my address book. -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

June 5, 2008

Re: [Pharo-project] About on:

by Adrian Lienhard

On Jun 5, 2008, at 00:27 , Bill Schwab wrote: > Stef, Damien, > > No surprise, I would argue that we proceed, and would also include a > rename of #next to #nextOrNil and #next: to #nextAvailable:. All > code in the image at the time should work as before. What would be the impact on code that is not in the image? Would all external packages need to be adapted as well or would the current semantics be preserved? Adrian > The next step (part B) would be to add exception-aware #next and > #next:. > > Damien and I could cook it up, try it, and then return with an "all > clear." > > Bill > > > > > > Wilhelm K. Schwab, Ph.D. > University of Florida > Department of Anesthesiology > PO Box 100254 > Gainesville, FL 32610-0254 > > Email: bschwab(a)anest.ufl.edu > Tel: (352) 846-1285 > FAX: (352) 392-7029 > > >>>> stephane.ducasse(a)inria.fr 6/4/2008 10:36 AM >>> > > On Jun 4, 2008, at 5:20 PM, Damien Cassou wrote: > >> On Wed, Jun 4, 2008 at 1:45 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >>> here is what I propose for on: >>> I will move your package out of the inbox so that the discussion >>> can go on >>> and >>> I try to integrate all the other changes. >>> Then with bill and others you propose how to proceed. >>> Is it ok ? >> >> What do you mean by 'I will move your package out of the inbox'? Do >> you mean you simply delete the packages or you moved them to Pharo? > > I mean move them to the treatedBox without putting in the image > >> Replacing 'ReadStream on: smth' by 'smth readStream' is not >> mandatory. >> However, it makes the code simpler to read, avoids a direct class >> reference and allows different implementation of #readStream >> depending >> on the kind of collection it is sent to. I do not think anyone is >> against that as soon as I apply the automatic refactoring >> carefully. I >> did that and didn't see any place where the RB did a bad job. It even >> detected that SequenceableCollection>>readStream should not be >> changed >> to avoid infinite recursion. >> >> Do you think there is a problem that I might take care of? > > Now as a group how do we want to handle this case? > We give a try and trust damien? > > Stef > > >> >> >> >> -- >> Damien Cassou >> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good >> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 5, 2008

Re: [Pharo-project] HowToContribute wiki page rewrite

by Victor Rodriguez

On Wed, Jun 4, 2008 at 3:20 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi victor > If you can, do it but > pay attention that we will certainly use pier or cmsbox at the end. (I know > that the current wiki is slow). I think it is worth to do it, since there doesn't appear to be a firm idea on when a Pier or Cmsbox site will be ready. Project owners, *please* add me to the project! > If you do it can you mark each page of the old one with a link to the new > one. Not a problem. Su servidor, VÃctor RodrÃguez. > Stef > On Jun 4, 2008, at 7:58 PM, Victor Rodriguez wrote: > >> On Wed, Jun 4, 2008 at 1:39 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >>> >>> Thanks so may be we should move the wiki contents to this one >>> but more importantly the tasks. >> >> I'll volunteer to move the wiki pages, as long as people don't mind if >> it takes the rest of the week to do it (I can only manage a few hours >> per week of "free time" :-P ). >> >> Victor. >> >> ps. Please add me to the project as victorr(a)gmail.com. >> >>> stef >>> >>> On Jun 4, 2008, at 7:36 PM, Damien Cassou wrote: >>> >>>> On Wed, Jun 4, 2008 at 7:08 PM, Damien Cassou <damien.cassou(a)gmail.com> >>>> wrote: >>>>> >>>>> On Wed, Jun 4, 2008 at 7:01 PM, StÃ©phane Ducasse >>>>> <stephane.ducasse(a)inria.fr> wrote: >>>>>>> >>>>>>> I think Lukas mention sometimes ago to use Google code, much cleaner >>>>>>> interface than this one, the wiki seems also much simpler >>>>>>> and there is a simple bug tracker integrated. >>>>>> >>>>>> Yes may be we should use the Googlecode tracker. >>>>>> Cna someone give a try. >>>>> >>>> >>>> http://code.google.com/p/pharo/. It seems very cool and simple. >>>> >>>> >>>> >>>> >>>> -- >>>> Damien Cassou >>>> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good >>>> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 5, 2008

Re: [Pharo-project] About readStream on: vs readStream

by Bill Schwab

Stef, FWIW, I consider it to be negotiable, provided we can use ReadStream as a factory/facade for Nile classes. With some double-dispatch, I think we could end up with something similar to directories: code references the generic class and the system instantiates platform-specific subclasses. In Nile, ReadStream on:aStream would answer a Nile read stream for the relevant collection species. That said, #readStream is a preferable idiom to #on:. My leaning would be to keep the latter and strongly encourage use of the former. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 846-1285 FAX: (352) 392-7029 >>> stephane.ducasse(a)inria.fr 6/4/2008 1:36 PM >>> Hi damien I was wondering why you think that ReadStream on: anObject is worse than anObject readStream? Because you do not hardcode ReadStream? Stef _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 4, 2008

Re: [Pharo-project] About on:

by Bill Schwab

Stef, Damien, No surprise, I would argue that we proceed, and would also include a rename of #next to #nextOrNil and #next: to #nextAvailable:. All code in the image at the time should work as before. The next step (part B) would be to add exception-aware #next and #next:. Damien and I could cook it up, try it, and then return with an "all clear." Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 846-1285 FAX: (352) 392-7029 >>> stephane.ducasse(a)inria.fr 6/4/2008 10:36 AM >>> On Jun 4, 2008, at 5:20 PM, Damien Cassou wrote: > On Wed, Jun 4, 2008 at 1:45 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> here is what I propose for on: >> I will move your package out of the inbox so that the discussion >> can go on >> and >> I try to integrate all the other changes. >> Then with bill and others you propose how to proceed. >> Is it ok ? > > What do you mean by 'I will move your package out of the inbox'? Do > you mean you simply delete the packages or you moved them to Pharo? I mean move them to the treatedBox without putting in the image > Replacing 'ReadStream on: smth' by 'smth readStream' is not mandatory. > However, it makes the code simpler to read, avoids a direct class > reference and allows different implementation of #readStream depending > on the kind of collection it is sent to. I do not think anyone is > against that as soon as I apply the automatic refactoring carefully. I > did that and didn't see any place where the RB did a bad job. It even > detected that SequenceableCollection>>readStream should not be changed > to avoid infinite recursion. > > Do you think there is a problem that I might take care of? Now as a group how do we want to handle this case? We give a try and trust damien? Stef > > > > -- > Damien Cassou > Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 4, 2008