- Pharo-dev - lists.pharo.org

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

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

May 31, 2008

Damien, The only potential problem is that you assume tests will catch everything. However, I think streams are broken, and I will certainly help fix what we break in getting them 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 >>> damien.cassou(a)gmail.com 05/30/08 9:37 AM >>> 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? -- 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

3 2

Re: [Pharo-project] open AtomBouncingMorphs in 3.7 and 3.9 is amazing...
by Bill Schwab May 31, 2008

May 31, 2008

Stef, Let me guess: 3.7 is MUCH faster, 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 05/30/08 11:25 AM >>> Hi guys it would be really interesting to understand why there is a so large difference between the two. 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

May 31, 2008

Begin forwarded message: > From: "Philippe Marschall" <philippe.marschall(a)gmail.com> > Date: May 30, 2008 10:52:50 PM CEDT > To: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr>, "Adrian > Lienhard" <alienhard(a)netstyle.ch> > Subject: patch for Squeak 3.9.2 / whatever > > http://bugs.squeak.org/view.php?id=6834 >

1 0

[Pharo-project] Fwd: Patch should be applied: Delay class>>timeoutSemaphore:afterMSecs:
by StÃ©phane Ducasse May 31, 2008

May 31, 2008

Begin forwarded message: > From: "Masashi UMEZAWA" <masashi.umezawa(a)gmail.com> > Date: May 31, 2008 4:56:00 AM CEDT > To: "stephane ducasse" <stephane.ducasse(a)free.fr> > Subject: Fwd: Patch should be applied: Delay > class>>timeoutSemaphore:afterMSecs: > > Hi Stef, > > This is just FYI (maybe you do not read v3dot10 list). > > 3.9.1 and Pharo have the same bug also. Networking application would > stop suddenly for this bug... > > ---------- Forwarded message ---------- > From: Masashi UMEZAWA <masashi.umezawa(a)gmail.com> > Date: 2008/5/29 > Subject: Patch should be applied: Delay > class>>timeoutSemaphore:afterMSecs: > To: "Discussion about development of Squeak 3.10" > <v3dot10(a)lists.squeakfoundation.org> > > > Hi all, > > I've downloaded 3.10.1, and found that an important patch on Delay > seems not applied. > > Please see the details on Mantis: > http://bugs.squeak.org/view.php?id=6834 > > Strangely, the patch is not applied on 3.9 series also. I think it is > clearly a bug and it should be fixed. > Socket timeout relies on this method, so the bug is fatal. > > Cheers, > -- > [:masashi | ^umezawa] > > Cheers, > -- > [:masashi | ^umezawa] >

1 0