November 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] (no subject)

by merlyn＠stonehenge.com

>>>>> "Lukas" == Lukas Renggli <renggli(a)gmail.com> writes: Lukas> I know the refactoring engine of Eclipse. It must be 20 years ahead of Lukas> Smalltalk. Ironic, since Eclipse was originally written in Smalltalk. :) -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <merlyn(a)stonehenge.com> <URL:http://www.stonehenge.com/merlyn/> Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion

Nov. 24, 2009

Re: [Pharo-project] (no subject)

by csrabak＠bol.com.br

Is there a kind of comparison table of the features available in Eclipse versus the Smalltalks' RBs? I wonder where are they 20 years ahead?! Em 24/11/2009 15:08, Damien Cassou <damien.cassou(a)gmail.com> escreveu: On Mon, Nov 23, 2009 at 7:53 PM, StÃ©phane Ducasse wrote: >> I know the refactoring engine of Eclipse. It must be 20 years ahead of Smalltalk. > > Not sure because it is full of bugs because Java is complex. I use Eclipse and its refactorings everyday. They work quite well. _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Nov. 24, 2009

Re: [Pharo-project] Pharo by Example - chapter about Exception - Error - Notification - Abort?

by Alexandre Bergel

> I enjoyed the chapter :-). It was very informative, and illustrated > yet again how flexible Smalltalk can be. Is there any particular > reason why this 'essential' chapter was not included in the first > edition of Pharo by Example? lack of time was the reason. > I also have a question about the contents. In chapter '1.14 Catching > sets of exceptions' it is explained how catch a set of exceptions > but not how to define a different handler on each exception. For > instance i want to handle a more specific FileDoesNotExistException > in a different way than a more general FileStreamException, or even > Exception. The way i can do this, i see, is to test which type of > exception is coming into the do: block and execute appropriate code. > This is a very bad solution. Or secondly, to create nested on: do: > blocks with the most specific exception as inner block. This seems > better, but is kind of verbose. > Is there another way to solve this problem? Visualworks uses HandlerList for this. One of the think you can do, is * either to nest block handlers [[ ex ] on: Error1 do: [:ex|...]] on: Error2 do: [:ex|...]. But in that case you should take care of inheritance relationship between Error1 and Error2. It does not work for any Error1 and Error2 classes * you can use a double dispatch on the exception Cheers, Alexandre > > Kind regards, > > Bart > > 2009/11/23 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > > Enjoy I had a lot of fun writing it when my family went to the > swimming pool and I could concentrate :) > > Stef > > On Nov 23, 2009, at 9:05 AM, Bart Gauquie wrote: > > > Dear all, > > > > I've been searching the Pharo by Example book about how to handle > Exception, Error, ... in Pharo. > > > > I've found some information about it in the SUnit chapter, in > method 7.11: Catching test case errors and failures; this is only a > small fragment however. > > > > Is there any chapter planned about this topic? It would be very > useful i think, since it is an important topic, and I've read that > Smalltalks exception handling is very powerful, but I don't know > much about it and like to learn it. > > > > Kind Regards, > > > > Bart > > > > -- > > imagination is more important than knowledge - Albert Einstein > > Logic will get you from A to B. Imagination will take you > everywhere - Albert Einstein > > Learn from yesterday, live for today, hope for tomorrow. The > important thing is not to stop questioning. - Albert Einstein > > The true sign of intelligence is not knowledge but imagination. - > Albert Einstein > > Gravitation is not responsible for people falling in love. - > Albert Einstein > > _______________________________________________ > > 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 > > > > -- > imagination is more important than knowledge - Albert Einstein > Logic will get you from A to B. Imagination will take you everywhere > - Albert Einstein > Learn from yesterday, live for today, hope for tomorrow. The > important thing is not to stop questioning. - Albert Einstein > The true sign of intelligence is not knowledge but imagination. - > Albert Einstein > Gravitation is not responsible for people falling in love. - Albert > Einstein > _______________________________________________ > 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 24, 2009

Re: [Pharo-project] (no subject)

by Damien Cassou

On Mon, Nov 23, 2009 at 7:53 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> I know the refactoring engine of Eclipse. It must be 20 years ahead of Smalltalk. > > Not sure because it is full of bugs because Java is complex. I use Eclipse and its refactorings everyday. They work quite well. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Nov. 24, 2009

[Pharo-project] Some comments about Filesystem

by Alexandre Bergel

Some comments about Filesystem: I am trying to use your library for file processing. I had the following: (FileStream fileNamed: 'inc.c.xml' ) readStream next => $< With Filesystem, I obtain the following: (FSDiskFilesystem current referenceTo: 'inc.c.xml') readStream next => 60 The problem is that the XML library does the #next, which expects a character, and not integer. I do instead: (FSDiskFilesystem current referenceTo: filenameString) readStreamDo: [:stream | . document := self parse: (ReadStream on: stream contents asString). ... But there should be a nicer way to obtain a character stream from a file. Another comment, why not to have FSReference>>files and FSReference>>directories? Although the visitors are convenient, I feel it will be useful to add #files and #directories. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 24, 2009

[Pharo-project] [ANN] Twitter account for Pharo...

by Marcus Denker

Hi, There is now a twitter for pharo: https://twitter.com/pharoproject I think we will use this for short news (e.g. new updates) in a way that it is more accessible than the mailinglist for people not subscribed. We have a News subsection for pharo-project.org ready to be deployed, too (for larger news). Marcus

Nov. 24, 2009

Re: [Pharo-project] Pharo by Example - chapter about Exception - Error - Notification - Abort?

by Henrik Johansen

On Nov 24, 2009, at 11:09 44AM, Bart Gauquie wrote: > I enjoyed the chapter :-). It was very informative, and illustrated yet again how flexible Smalltalk can be. Is there any particular reason why this 'essential' chapter was not included in the first edition of Pharo by Example? It wasn't done yet, probably :) > > I also have a question about the contents. In chapter '1.14 Catching sets of exceptions' it is explained how catch a set of exceptions but not how to define a different handler on each exception. For instance i want to handle a more specific FileDoesNotExistException in a different way than a more general FileStreamException, or even Exception. The way i can do this, i see, is to test which type of exception is coming into the do: block and execute appropriate code. This is a very bad solution. Or secondly, to create nested on: do: blocks with the most specific exception as inner block. This seems better, but is kind of verbose. > Is there another way to solve this problem? This was discussed abit some time ago, might want to read: http://n2.nabble.com/better-error-handling-td3750946.html#a3750946 Cheers, Henry

Nov. 24, 2009

Re: [Pharo-project] Pharo by Example - chapter about Exception - Error - Notification - Abort?

by Bart Gauquie

I enjoyed the chapter :-). It was very informative, and illustrated yet again how flexible Smalltalk can be. Is there any particular reason why this 'essential' chapter was not included in the first edition of Pharo by Example? I also have a question about the contents. In chapter '1.14 Catching sets of exceptions' it is explained how catch a set of exceptions but not how to define a different handler on each exception. For instance i want to handle a more specific FileDoesNotExistException in a different way than a more general FileStreamException, or even Exception. The way i can do this, i see, is to test which type of exception is coming into the do: block and execute appropriate code. This is a very bad solution. Or secondly, to create nested on: do: blocks with the most specific exception as inner block. This seems better, but is kind of verbose. Is there another way to solve this problem? Kind regards, Bart 2009/11/23 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > > Enjoy I had a lot of fun writing it when my family went to the swimming > pool and I could concentrate :) > > Stef > > On Nov 23, 2009, at 9:05 AM, Bart Gauquie wrote: > > > Dear all, > > > > I've been searching the Pharo by Example book about how to handle > Exception, Error, ... in Pharo. > > > > I've found some information about it in the SUnit chapter, in method > 7.11: Catching test case errors and failures; this is only a small fragment > however. > > > > Is there any chapter planned about this topic? It would be very useful i > think, since it is an important topic, and I've read that Smalltalks > exception handling is very powerful, but I don't know much about it and like > to learn it. > > > > Kind Regards, > > > > Bart > > > > -- > > imagination is more important than knowledge - Albert Einstein > > Logic will get you from A to B. Imagination will take you everywhere - > Albert Einstein > > Learn from yesterday, live for today, hope for tomorrow. The important > thing is not to stop questioning. - Albert Einstein > > The true sign of intelligence is not knowledge but imagination. - Albert > Einstein > > Gravitation is not responsible for people falling in love. - Albert > Einstein > > _______________________________________________ > > 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 > -- imagination is more important than knowledge - Albert Einstein Logic will get you from A to B. Imagination will take you everywhere - Albert Einstein Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Albert Einstein The true sign of intelligence is not knowledge but imagination. - Albert Einstein Gravitation is not responsible for people falling in love. - Albert Einstein

Nov. 24, 2009

[Pharo-project] [update 1.1] #11060

by Marcus Denker

11060 ----- Issue 1495: 1.1: fix some tests related to printing self-evaluation arrays Issue 1496: clean some unsent messages.... Issue 1497: Saving preferences to disk gives an error Marcus -- Marcus Denker -- http://www.marcusdenker.de

Nov. 24, 2009

Re: [Pharo-project] Pharo by Example - chapter about Exception - Error - Notification - Abort?

by csrabak＠bol.com.br

I started reading it. It seems to me that at page 5 the last paragraph "If Smalltalk did provide exception-handling support, then the tiny example we saw in the previous section would be written something like this," is missing a negative like Â«"If Smalltalk did *not* provide exception-handling support..."Â». Isn't it? -- Cesar Rabak Em 23/11/2009 16:57, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr > escreveu: > Enjoy I had a lot of fun writing it when my family went to the swimming pool and I could > concentrate :)

Nov. 24, 2009