April 2014 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Question on style

by nacho

Damien, Thanks a lot for your comments and the time taken to review the code. It makes a lot of sense what you said, and it's a great aid in learning to not only solve a given problem but also to do it with style and in a better Smalltalk way. I will refactor this to reflect your suggestions. I read in a message that someone was asking about 99 problems for Smalltalk and I thought that it would be a wonderful idea to have simple problems solved in a very good way (not only solving the problem but also doing it with style), so I started to formulate some problems for me. I'm writing notes to myself for every problem solved and if you don't mind I will like to quote what you say. May be in the future as I go on with this little, but increasing problems, someone could benefit also by having not only the code, but also some comments on why some approach was taken, or problem tackled. Thanks again best Nacho ----- Nacho Smalltalker apprentice. Buenos Aires, Argentina. -- View this message in context: http://forum.world.st/Question-on-style-tp4752165p4752261.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 2, 2014

Re: [Pharo-users] lasergame problem with Blankcell

by Roelof Wobben

April 2, 2014

Re: [Pharo-users] lasergame problem with Blankcell

by Mark Rizun

> > And only on this method the test fail on should: > > testCellOnState > | cell | > cell := BlankCell new. > cell should: [ cell isOff ]. > cell shouldnt: [ cell isOn ]. > Yes it does, inasmuch on the bottom of this page ( http://squeak.preeminent.org/tut2007/html/017.html ) both methods return *false*. I think later the implementation of this two methods will be changed so don't worry.

April 2, 2014

Re: [Pharo-users] lasergame problem with Blankcell

by Roelof Wobben

April 2, 2014

Re: [Pharo-users] lasergame problem with Blankcell

by Roelof Wobben

April 2, 2014

Re: [Pharo-users] lasergame problem with Blankcell

by Mark Rizun

Hi, You probably misunderstood the task. On the first part I have to make a class named BlankCell which is a > subclass of TestCase. > You had to create the class *BlankCellTestCase* (not BlankCell) which is a subclass of *TestCase*. BlankCell and BlankCellTestCase are two different classes. -BlankCell is a class that represents a model of an empty cell (its size, segments etc.) -BlankCellTestCase is basically a class that helps you to control (and test) methods that you have on BlankCell class. But when you are on the MirrorCell part BlankCell must be a subclass of > Cell. > Cell class is an abstract, which is a superclass for following classes: BlankCell, MirrorCell, TargetCell. It provides some basic behavior or properties for BlankCell, MirrorCell, TargetCell, which all of them have in common But then the tests will fail because should: cannot be found. > Sure it fails. in order to use *should:* the class BlankCellTestCase has to be a subclass of TestCase. But it is recommended to use *assert:* instead of *should:* The manual says nothing about that the new class Cell must be a part of > TestCase. > Cell has to be a subclass of an Object. Cheers, Mark

April 2, 2014

Re: [Pharo-users] lasergame problem with Blankcell

by Nicolai Hess

2014-04-02 13:21 GMT+02:00 Roelof Wobben <r.wobben(a)home.nl>: > Hello, > > On the first part I have to make a class named BlankCell which is a > subclass of TestCase. > So far no problem. > No, firstly, all cells are just subclasses of Object ( http://squeak.preeminent.org/tut2007/html/015.html) And in step http://squeak.preeminent.org/tut2007/html/015A.html class BlankCellTestCase is a subclass of TestCase > > > But when you are on the MirrorCell part BlankCell must be a subclass of > Cell. > But then the tests will fail because should: cannot be found. > In step http://squeak.preeminent.org/tut2007/html/025.html, you create a new abstract class Cell and moves the BlankCell under the new abstract class. > The manual says nothing about that the new class Cell must be a part of > TestCase. > No, the TestCases are just "using" your Cell classes. In http://squeak.preeminent.org/tut2007/html/026.html you are moving the MirrorCell under Cell as well. And only testcase BlankCellTestCase is a subclass of TestCase. And then you are createinga new subclass of TestCase -> MirrorCellTestCase > > How to solve this ? > > Roelof > > >

April 2, 2014

Re: [Pharo-users] lasergame problem with Blankcell

by Camille Teruel

On 2 avr. 2014, at 13:21, Roelof Wobben <r.wobben(a)home.nl> wrote: > Hello, > > On the first part I have to make a class named BlankCell which is a subclass of TestCase. > So far no problem. > But when you are on the MirrorCell part BlankCell must be a subclass of Cell. > But then the tests will fail because should: cannot be found. BlankCell is a class of your domain not a test case. I guess the tutorial ask you to create a BlankCellTests test case. #should is a method of TestCase. Your tests are methods whose names begin with 'test' in subclasses of TestCase. > The manual says nothing about that the new class Cell must be a part of TestCase. > How to solve this ? > Roelof > >

April 2, 2014

lasergame problem with Blankcell

by Roelof Wobben

Hello, On the first part I have to make a class named BlankCell which is a subclass of TestCase. So far no problem. But when you are on the MirrorCell part BlankCell must be a subclass of Cell. But then the tests will fail because should: cannot be found. The manual says nothing about that the new class Cell must be a part of TestCase. How to solve this ? Roelof

April 2, 2014

changes and sources file availability

by Usman Bhatti

Hello, In Pharo 2.0, we could enforce the image not to look for sources and changes file at the startup with: SmalltalkImage checkChangesFileAvailability: false; checkSourcesFileAvailability: false. I could not found these selectors anymore in my Pharo 3.0 image. Clement mentioned to me a while ago that it was due to the change of compiler (Opal) and it might not be safe to remove these files (if I remember correctly). So, my question: 1/ Can I remove these two files safely from my production image? 2/ If the answer to 1/ is yes, how can I tell my image not to look for these files at image startup? tx, Usman

April 2, 2014