- Pharo-dev - lists.pharo.org

[Pharo-project] I added the 3.10.1 list of fixes to the wiki.
by StÃ©phane Ducasse June 1, 2008

June 1, 2008

1 0

Re: [Pharo-project] Replacing 'ReadStream on smth:' by 'smth readStream'
by Bill Schwab June 1, 2008

June 1, 2008

Stef, My email server crashed yesterday and was out of action for several hours. From emails I found this morning, it looks like Damien and I will cook up a plan on the Wiki. With luck, we will be able to get the RB to do the tedious work, and also leave a simple defined procedure for converting "old" code that we did not have loaded during the transformation. Transformed code should work as it always did; new code will be able to benefit from consistent semantics and exception handling. There will also be silently truncating methods for the situations (and they indeed exist) that call for them. More to come. 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 05/31/08 4:22 PM >>> On May 30, 2008, at 10:46 PM, Bill Schwab wrote: > Stef, > > Whether or not I agree depends on what you mean. While I think I > see where Damien is going, my read is that #on: is actually > negotiable, given that we should be able to either fix (or simply > replace and than alias) ReadStream - two different ways of solving > the same problem. But if you concerned about breaking some things > that Damien and I are committed to fixing as part of the change, > then I submit that we will be helpless when we move from the > relatively calm world of streams to the chaos of morphic. You lost me. :) > Which part bothers you? None :) > The plan is to rennovate (sometimes messy) and *then* slowly evolve > the resulting stable system, right? The plan is to move but be careful. This is why I would like you guys to tell us what you want to do (or are doing) so that we can document the changes and everybody can participate and help also fixing if necessary. I just want more organized communication when we have a "big" change. No more. Stef _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

2 1

[Pharo-project] [ANN][Pharo-dev] First release
by Damien Cassou June 1, 2008

June 1, 2008

Hi, I've published the first version of Pharo-dev. It is hosted on gforge as usual: https://gforge.inria.fr/frs/?group_id=1299. I will try to generate new pharo-dev images when I generate squeak-dev images if anyone is interested. Are you? Bye -- 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)

5 11

[Pharo-project] Resent messages?
by Bill Schwab June 1, 2008

June 1, 2008

Hello all, Did some messages get posted more than once? It beats losing them, but leaves me wondering whether it is my goofy email server or something about the list conversion. FWIW. 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

1 0

Re: [Pharo-project] new to pharo
by Alain Plantec June 1, 2008

June 1, 2008

On Saturday 31 May 2008 14:24:05 you wrote: > Alain, > > You have COMPLETELY missed the focus of my response; thanks for > objecting so we can clarify it. My point was that it is a great start > on explaining something that is indeed mysterious to many (including > myself!), and deserves to be built up into a Wiki page for future > reference vs. "lost" in an archived list. Excuse me, it seems that I have to improve my english alain > > Please continue questioning the experts, and document what they tell > you. We will have it right when the answer is a link to a page complete > with a FAQ. > > Bill > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > >

1 0

Fwd: Re: [Pharo-project] new to pharo
by Bill Schwab May 31, 2008

May 31, 2008

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

2 1

Re: [Pharo-project] new to pharo
by Alexandre Bergel May 31, 2008

May 31, 2008

>> The webpage https://gforge.inria.fr/plugins/wiki/index.php?HowToContribute&id=1299&type… >> should gives the big lines on how to contribute. > thanks, I should have found it myself. The website of Pharo is really. We plan to change it in a near future... >> Feel free to request for help if necessary. > > ok, I'm starting by chasing all senders to the isMorphic message Let us know about your progress... Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

4 6

Re: [Pharo-project] new to pharo
by Bill Schwab May 31, 2008

May 31, 2008

I think this needs to be carved onto the side of a monument somewhere, perhaps with a gigantic and stylized image of Avi or Colin smiting a helpless enemy :) Failing that, perhaps it should go on a wiki?? 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 >>> alexandre(a)bergel.eu 5/30/2008 4:27:18 PM >>> Hi Alain, I agree, the process is not that easy and intuitive. 1 - Take the latest pharo image, and click on update on the left tab 2 - Open Monticello 3 - Load your .cs file 4 - you should see some package with a * before them in Monticello 5 - Create a package named SLICE-Remove isMorphic message 6 - add to your SLICE package all the packages that have a * before their name as required 7 - Save your SLICE package in PharoInBox Cheers, Alexandre On 30 May 2008, at 20:39, Alain Plantec wrote: > >>> ok, I'm starting by chasing all senders to the isMorphic message > I've a .cs that touch a lot of methods everywhere**. > now, what is the procedure ? > can I put my .cs somewhere, give it to somebody, make a .mcz with > it ? (I do not known how) > sorry for all these stupid questions, I try to understand the update > process. > thanks > alain > > > ** > for all #isMorphic senders: > "self isMorphic ifTrue: [XXXXX] ifFalse: [YYYYY]" > is replaced with > "XXXXX" > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

4 3

Re: [Pharo-project] Replacing 'ReadStream on smth:' by 'smth readStream'
by Bill Schwab May 31, 2008

May 31, 2008

Stef, Whether or not I agree depends on what you mean. While I think I see where Damien is going, my read is that #on: is actually negotiable, given that we should be able to either fix (or simply replace and than alias) ReadStream - two different ways of solving the same problem. But if you concerned about breaking some things that Damien and I are committed to fixing as part of the change, then I submit that we will be helpless when we move from the relatively calm world of streams to the chaos of morphic. Which part bothers you? The plan is to rennovate (sometimes messy) and *then* slowly evolve the resulting stable system, right? 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 5/30/2008 3:27:20 PM >>> I agree with adrian. For pharo we should move but we should also make sure it is really stable. Stef On May 30, 2008, at 2:18 PM, Adrian Lienhard wrote: > Have you verified that your change does not inadvertently modify any > behavior? Its not likely, but changes like this can introduce subtle > bugs. For instance, Matrix overrides readStream. So if there exists > any use of "ReadStream on: aMatrix" that is there to bypass the > overridden behavior, the code will break. > > Cheers, > Adrian > > On May 30, 2008, at 10:47 , Damien Cassou wrote: > >> Hi, >> >> I've just published in the pharo inbox a package for the System >> category. This change has been generated automatically through the >> rewriter: >> >> ParseTreeRewriter new >> replace: 'ReadStream on: ``@object' with: '``@object readStream'; >> yourself >> >> The formatting of the changed method is completely different due to >> the use of the refactoring browser. This makes the diffs not >> readable. >> Even if it is a real problem, I don't see any simple solution. What >> do >> you think? >> >> -- >> 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

3 2

[Pharo-project] Replacing 'ReadStream on smth:' by 'smth readStream'
by Damien Cassou May 31, 2008

May 31, 2008

Hi, I've just published in the pharo inbox a package for the System category. This change has been generated automatically through the rewriter: ParseTreeRewriter new replace: 'ReadStream on: ``@object' with: '``@object readStream'; yourself The formatting of the changed method is completely different due to the use of the refactoring browser. This makes the diffs not readable. Even if it is a real problem, I don't see any simple solution. What do you think? -- 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)

4 9