- Pharo-dev - lists.pharo.org

Re: [Pharo-project] open AtomBouncingMorphs in 3.7 and 3.9 is amazing...

by Bill Schwab

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

May 30, 2008

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

by Bill Schwab

Damien, That would be great. It does me little good in my current version of Dolphin, though I should look at the more recent versions. Making a long story short, D6 broke a lot of my code and reduced compatibility with win2k (the big show-stopper for me at the time), so I never upgraded. I am currently far more bothered by unwanted changes in Windows than I have ever been by deficiencies in Dolphin. IIRC, some of the breaking changes are now understood, so it might pay to have another look, though I still need to run on win2k, just (sadly IMHO) not as much as a few years ago. Another option would be to load code into Pharo and hit it with an up to date RB. 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:47 AM >>> On Fri, May 30, 2008 at 2:13 PM, Bill Schwab <BSchwab(a)anest.ufl.edu> wrote: > Interesting! As an aside, I have a love/hate relationship with the RB, and almost never let it rewrite any of my Dolphin code. The XP guys will recoil in horror at this, but I have too often been saved by 18 month old comments to have them disrespectfully scattered around my source. If that is fixed, I will become a believer. I *do* use pull up/down to great advantage, and will sometimes use other refactorings on new code that has not had time to accumulate valuable comments. This problem has been fixed some time ago IIRC. -- 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

May 30, 2008

[Pharo-project] open AtomBouncingMorphs in 3.7 and 3.9 is amazing...

by StÃ©phane Ducasse

Hi guys it would be really interesting to understand why there is a so large difference between the two. Stef

May 30, 2008

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

by Alexandre Bergel

I personally invoke the ObLoader2 method at each Pharo release to have the tools that I need.., Cheers, Alexandre On 30 May 2008, at 16:12, Damien Cassou wrote: > On Fri, May 30, 2008 at 3:54 PM, Alexandre Bergel > <alexandre(a)bergel.eu> wrote: >> I agree with Bil, it is hard to say whether people will find Pharo- >> dev >> useful. Just give a try :-) > > I was thinking about you guys who are working on Pharo himself. It > seems you all load OB, RB and the other manually. > > > -- > 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 > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 30, 2008

[Pharo-project] Re: Package Files has unsaved changes in latest Pharo

by Damien Cassou

On Fri, May 30, 2008 at 2:37 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > Hi, > > if you take latest released Pharo, open Monticello, select the package > Files and the repository Pharo, you will see changes in the class > declaration CrLfFileStream. Same for packages Sound and Compiler. Probably others. -- 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)

May 30, 2008

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

by Damien Cassou

On Fri, May 30, 2008 at 3:54 PM, Alexandre Bergel <alexandre(a)bergel.eu> wrote: > I agree with Bil, it is hard to say whether people will find Pharo-dev > useful. Just give a try :-) I was thinking about you guys who are working on Pharo himself. It seems you all load OB, RB and the other manually. -- 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)

May 30, 2008

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

by Alexandre Bergel

I agree with Bil, it is hard to say whether people will find Pharo-dev useful. Just give a try :-) Cheers, Alexandre On 30 May 2008, at 15:06, Damien Cassou wrote: > 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) > > _______________________________________________ > 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 30, 2008

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

by Damien Cassou

On Fri, May 30, 2008 at 2:13 PM, Bill Schwab <BSchwab(a)anest.ufl.edu> wrote: > Interesting! As an aside, I have a love/hate relationship with the RB, and almost never let it rewrite any of my Dolphin code. The XP guys will recoil in horror at this, but I have too often been saved by 18 month old comments to have them disrespectfully scattered around my source. If that is fixed, I will become a believer. I *do* use pull up/down to great advantage, and will sometimes use other refactorings on new code that has not had time to accumulate valuable comments. This problem has been fixed some time ago IIRC. -- 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)

May 30, 2008

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

by Damien Cassou

On Fri, May 30, 2008 at 2:13 PM, Bill Schwab <BSchwab(a)anest.ufl.edu> wrote: > The above said, I have considered doing something like your rewrite to fix stream method naming snags. Consider #next. As we have discussed, I think it should be named #nextOrNil, allowing #next to behave as it does in Dolphin. Yes, I have a bias toward Dolphin, but I also consider its streams to be elegantly/correctly built. > > One way to fix it would be to transform #next into #nextOrNil (which is what Squeak's #next does), and then add a #next that signals EndOfStream on exhaustion; I agree. > EndOfStream would have no default action in this scenario. If we could further transform any idioms such as > > aStream next ifNotNil:[ :x | ... ] > > into > > aStream nextIfPresent:[ :x | ... ] > > etc., that could be great if we did it well. Even a clean change to #nextOrNil would allow us to make an otherwise breaking change as painlessly as possible. > > FWIW, I have no direct problem with #on:, though I see where you are going. We might get a similar benefit by simply changing ReadStream in the system dictionary, making it an alias for NSReadStream?? Even without talking about Nile, I think it is a good thing to avoid direct references to ReadStream. This also renders the code more readable. A third benefit is that #readStream could now be implement differently on different kind of streamable things. In Nile for example, String overrides #readStream to return an improved ReadStream for strings. -- 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)

May 30, 2008

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

by Damien Cassou

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)

May 30, 2008