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

Re: [Pharo-project] [ANN][Pharo-dev] First release

by StÃ©phane Ducasse

You lost me. >> yes we are. >> I hope to have a server soon for the universe > > I think it will be difficult to maintain a universe server (each time > you update a package on the squeak universe, you will have to do it > again for pharo).

May 31, 2008

Re: [Pharo-project] new to pharo

by StÃ©phane Ducasse

http://gforge.inria.fr/plugins/wiki/index.php?HowToContribute&id=1299&type=g

May 31, 2008

Re: [Pharo-project] new to pharo

by StÃ©phane Ducasse

>> >> >> 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 >> > > I don't understand these instructions: > > How do you do step 6? what does adding packages to packages > mean? alex meant all the dirty packages (because of your changes) that contain your changes > > > Slices sounds like MC2. Does Pharo use MC2? We would like but MC2 does not seem ready yet. But we will definitively give a try. Stef > > > -- > Matthew Fulmer -- http://mtfulmer.wordpress.com/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 31, 2008

Re: [Pharo-project] new to pharo

by StÃ©phane Ducasse

It is on the wiki :) How to submit changes (ok this wiki is terrible... we will change) Stef On May 31, 2008, at 1:31 AM, Bill Schwab wrote: > 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 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 31, 2008

Re: [Pharo-project] Replacing 'ReadStream on smth:' by 'smth readStream'

by StÃ©phane Ducasse

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

May 31, 2008

Re: [Pharo-project] Replacing 'ReadStream on smth:' by 'smth readStream'

by StÃ©phane Ducasse

excellent! > I knew the tests argument did not hold because there are so few tests > in Squeak, I was joking :-). I'm trying to do the changes carrefully, > that's why I commited things package after package instead of doing it > globally. Stef

May 31, 2008

Re: [Pharo-project] new to pharo

by StÃ©phane Ducasse

What is important is that we can load the slice. Bcause this is the problem with cs is that you can get packages that you cannot reload. Stef On May 31, 2008, at 11:47 AM, Alexandre Bergel wrote: >>> 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 > >> I don't understand these instructions: >> >> How do you do step 6? what does adding packages to packages >> mean? > > Right click or (command click if you're on a mac) on a package > listed in a Monticello browser. you will see "add required package". > Add all the packages that are prefixed by a * (resulting from > loading your .cs file). > > >> Slices sounds like MC2. Does Pharo use MC2? > > No. pharo uses MC1. We might switch to MC2 when it is ready, but for > now we stick to something that is reliable. > > I hope this is clearer now. > What Bill meant I guess is to add this information to a wiki. I will > refine what is already written over the time. > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > 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 >

May 31, 2008

Re: [Pharo-project] Re: [Sapphire-devl] sapphire to pharo :)

by StÃ©phane Ducasse

Done. Can you check? I will redo a full upgrade in a clean package cache. Stef On May 31, 2008, at 11:40 AM, Adrian Lienhard wrote: > Hi Stef, > > Today I tried again to load Pharo starting from a fresh 3.9.1 image > but I got the same error when loading "10015-Sap- > FixingInvisibleInTheRest..." (see my mail in this thread from May 16). > > I had a closer look and the problem is that script106 tries to load > Protocols-sd.13.mcz, which does not exist in the repository. > I guess the update worked for you because this file was in your > local cache. Can you copy this package to the repository? > > Adrian

May 31, 2008

Re: [Pharo-project] Re: [Sapphire-devl] sapphire to pharo :)

by StÃ©phane Ducasse

Ok I will Sorry. > Hi Stef, > > Today I tried again to load Pharo starting from a fresh 3.9.1 image > but I got the same error when loading "10015-Sap- > FixingInvisibleInTheRest..." (see my mail in this thread from May 16). > > I had a closer look and the problem is that script106 tries to load > Protocols-sd.13.mcz, which does not exist in the repository. > I guess the update worked for you because this file was in your > local cache. Can you copy this package to the repository? > > Adrian > > > On May 17, 2008, at 08:19 , StÃ©phane Ducasse wrote: > >> Yes this may happen. We are certainly stressing the server. >> Now #hex is really missing in 391. :) >> >> Stef >> >> On May 17, 2008, at 6:40 AM, Victor Rodriguez wrote: >> >>> On Sat, May 17, 2008 at 12:14 AM, Victor Rodriguez >>> <victor.palique(a)gmail.com> wrote: >>> ... >>>> It failed for me in update 10016. I attach the log. >>> >>> It must have been a network error, since started all over again >>> and it >>> is now in update 10020... >>> >>> Victor. >>> >>> _______________________________________________ >>> Sapphire-devl mailing list >>> Sapphire-devl(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/sapphire-devl >>> >> >> >> _______________________________________________ >> Sapphire-devl mailing list >> Sapphire-devl(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/sapphire-devl > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 31, 2008

Re: [Pharo-project] Replacing 'ReadStream on smth:' by 'smth readStream'

by StÃ©phane Ducasse

I agree with adrian. I would like to use the stream as a test for Call For Improvement Process. So could you come up with a kind of template Summary: Key points: Some tests to illustrate Actions/Process Stef On May 30, 2008, at 6:17 PM, Adrian Lienhard wrote: > > On May 30, 2008, at 15:37 , Damien Cassou wrote: > >> On Fri, May 30, 2008 at 2:18 PM, Adrian Lienhard <adi(a)netstyle.ch> >> 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. >> >> It should not break anything (if it does, the test will fail and I >> will fix things :-)). In fact, ReadStream only deals with >> SequenceableStreams so it should be ok. Do you agree? > > No I don't agree. Because it is not likely that there is a test for > Matrix that will show a potential bug. I just wanted to point out > that it is important to precisely look at the effect of such > "global" transformations. (E.g. like Edgar tried to replace all #== > with #= IIRC ;) > > With your proposed change, I think it is unlikely you will break > anything, but you cannot say for sure without detailled *manual* > checking. The difficulty is that you theoretically needed to verify > that there is never passed a Matrix instance to "ReadStream on:". > > Also to consider with such changes is that you may break external > code that you don't know of. To sum up, I'm not against such > improvements at all, but they have to be done carefully, i.e., the > argument that tests will show any problem does not hold. > > Cheers, > Adrian > >> -- >> 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 >

May 31, 2008