March 2013 - Pharo-users - lists.pharo.org

[ANN] Phratch: Scratch on Pharo2.0

by jannik.laval

Hi Pharoers, I am porting Scratch and BYOB on Pharo 2.0. The name of the project is Phratch. To begin, I took Scat (a port of Scratch on Pharo1.3) and modify it to make it work on Pharo 2.0. For that I integrated FileSystem. Then, I took BYOB and port it in the project. I have some bugs, but the main features are working. The main issue is that it is slow. I will investigate that too. The goal for me is to use it for teaching software engineering and robotics. I hope to use Phratch and Pharo 2.0 to create new features. The project is on SmalltalkHub, and a google code page is available, mainly for reporting issues: https://code.google.com/p/phratch/ To download Phratch, just run this code: Gofer it url: 'http://smalltalkhub.com/mc/JLaval/Phratch/main'; package: 'ConfigurationOfPhratch'; load. (Smalltalk at: #ConfigurationOfPhratch) loadBleedingEdge. Cheers, Jannik

March 24, 2013

Re: [Pharo-users] NeoJSON Mappings

by Sven Van Caekenberghe

Hi Esteban, I have been thinking about you ;-) On 19 Mar 2013, at 15:26, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I think I understand what you want, and I know that you tried to explain the model (or a minimal version of it), but if you are writing out JSON according to some externally defined format (with the ideas and sharing), would it be possible to give me the specification of that format ? Maybe off list ? Without knowing exactly what your target is, it is hard for me, below is how I understand your problem and how I would solve it. > In any case, I will think about the issue you raised. There are book objects, with id, title and author. The first time you write them out, you write all the details. If you encounter the same book again in the same encoding session, you only write out the id. To do this, you need a custom writer subclass that can keep track of books seen, in the scope of the encoding session (incidentally, this is how you would do a writer that knows when it goes into cycles - but again, this has all been done in STON). Furthermore, to dynamically decide the encoding you have to overwrite #neoJsonOn: This is done here by delegating to the custom writer. There the decision is made to take the normal route (super) or to just write the id. The class side of book still have a normal mapping. Of course, a production quality implementation will be some more work. I hope that this is more or less what you were looking for. Regards, Sven ---- TestCase subclass: #NeoJSONBookTests instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'Neo-JSON-Example'! !NeoJSONBookTests methodsFor: 'testing' stamp: 'SvenVanCaekenberghe 3/24/2013 17:52'! testMultiple | book1 book2 | (book1 := NeoJSONBook new) id: 'B101'; title: 'The Hobbit'; author: 'JJR Tolkien'. (book2 := NeoJSONBook new) id: 'B102'; title: 'Lord Of The Rings'; author: 'JJR Tolkien'. NeoJSONCustomWriter toString: { book1. book1. book2. book1. book2 }! ! !NeoJSONBookTests methodsFor: 'testing' stamp: 'SvenVanCaekenberghe 3/24/2013 17:44'! testOne | book | (book := NeoJSONBook new) id: 'B101'; title: 'The Hobbit'; author: 'JJR Tolkien'. NeoJSONCustomWriter toString: book.! ! Object subclass: #NeoJSONBook instanceVariableNames: 'id title author' classVariableNames: '' poolDictionaries: '' category: 'Neo-JSON-Example'! !NeoJSONBook methodsFor: 'accessing' stamp: 'SvenVanCaekenberghe 3/24/2013 17:35'! author ^ author! ! !NeoJSONBook methodsFor: 'accessing' stamp: 'SvenVanCaekenberghe 3/24/2013 17:35'! author: anObject author := anObject! ! !NeoJSONBook methodsFor: 'accessing' stamp: 'SvenVanCaekenberghe 3/24/2013 17:35'! id ^ id! ! !NeoJSONBook methodsFor: 'accessing' stamp: 'SvenVanCaekenberghe 3/24/2013 17:35'! id: anObject id := anObject! ! !NeoJSONBook methodsFor: 'accessing' stamp: 'SvenVanCaekenberghe 3/24/2013 17:39'! neoJsonOn: neoJSONWriter neoJSONWriter writeBook: self! ! !NeoJSONBook methodsFor: 'accessing' stamp: 'SvenVanCaekenberghe 3/24/2013 17:35'! title ^ title! ! !NeoJSONBook methodsFor: 'accessing' stamp: 'SvenVanCaekenberghe 3/24/2013 17:35'! title: anObject title := anObject! ! "-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- "! NeoJSONBook class instanceVariableNames: ''! !NeoJSONBook class methodsFor: 'accessing' stamp: 'SvenVanCaekenberghe 3/24/2013 17:41'! neoJsonMapping: mapper mapper mapAllInstVarsFor: self! ! NeoJSONWriter subclass: #NeoJSONCustomWriter instanceVariableNames: 'books' classVariableNames: '' poolDictionaries: '' category: 'Neo-JSON-Example'! !NeoJSONCustomWriter methodsFor: 'initialize-release' stamp: 'SvenVanCaekenberghe 3/24/2013 17:52'! initialize super initialize. books := Set new! ! !NeoJSONCustomWriter methodsFor: 'accessing' stamp: 'SvenVanCaekenberghe 3/24/2013 17:35'! books ^ books! ! !NeoJSONCustomWriter methodsFor: 'accessing' stamp: 'SvenVanCaekenberghe 3/24/2013 17:35'! books: anObject books := anObject! ! !NeoJSONCustomWriter methodsFor: 'writing' stamp: 'SvenVanCaekenberghe 3/24/2013 17:53'! writeBook: aBook (self books includes: aBook id) ifTrue: [ self writeMapStreamingDo: [ :jsonMapWriter | jsonMapWriter writeKey: 'id' value: aBook id ] ] ifFalse: [ books add: aBook id. super writeObject: aBook ]! ! ---- -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

March 24, 2013

Re: [Pharo-users] Method Calling Inside Nested Blocks

by stephane ducasse

you should really read the syntax chapter of the Pharo by example because it explains all these points really precisely. I'm sure that you will get a ahhhhha effect once you read it. Stef On Mar 23, 2013, at 2:14 PM, Mohammad Al Houssami (Alumni) <mha53(a)mail.aub.edu> wrote: > Probably because I am not using dots except at the end of blocks which I think is wrong. > This is a sample of what I had earlier: > currentCharacter = CHARACTERTABULATION ifTrue: [anythingElseBoolean:= false > AfterDOCTYPENameState value: currentCharacter ]. > There should be a dot after false right ? Once I add the dot I get a complain. > > > From: pharo-users-bounces(a)lists.gforge.inria.fr [mailto:pharo-users-bounces@lists.gforge.inria.fr] On Behalf Of Esteban Lorenzano > Sent: Saturday, March 23, 2013 3:09 PM > To: A friendly place where any question about pharo is welcome > Subject: Re: [Pharo-users] Method Calling Inside Nested Blocks > > if it is a method, it needs the receiver, in this case "self" (remember, any call in smalltalk is: receiver+message). > If for some weird reason you did not need it before (like some chained call effect), that was just by chance... you just were lucky before :) > > Esteban > > On Mar 23, 2013, at 1:58 PM, "Mohammad Al Houssami (Alumni)" <mha53(a)mail.aub.edu> wrote: > > > So the method declaration should be self afterDOCTYPEPublicKeywordState: currentCharacter. ? > > But I have been doing the same for quite some time and I wasnât getting any complains. This is the first time and the only thing that changed is that I have two blocks in this case. As I said earlier if I move the method call outside the block it works with no complains J > > I'll change the names of all my methods to camel case. Thanks for that > > > From: pharo-users-bounces(a)lists.gforge.inria.fr [mailto:pharo-users-bounces@lists.gforge.inria.fr] On Behalf Of Esteban Lorenzano > Sent: Saturday, March 23, 2013 2:52 PM > To: A friendly place where any question about pharo is welcome > Subject: Re: [Pharo-users] Method Calling Inside Nested Blocks > > > On Mar 23, 2013, at 12:31 PM, "Mohammad Al Houssami (Alumni)" <mha53(a)mail.aub.edu> wrote: > > > > Hello everyone > > I was trying to save my method which has the below piece of code > > anythingElseBoolean = false ifFalse: [ > doctypeString := reader next: 6 > doctypeString asLowercase = 'public' ifTrue: [ > AfterDOCTYPEPublicKeywordState value: currentCharacter > ] > > I get a complain that the AfterDOCTYPEPublicKeywordState is unknown even though I have a method with this name. > > AfterDOCTYPEPublicKeywordState is a METHOD???? > then, you are missing some points: > > 1) it does not conforms conventions (it should start with lowercase) > 2) you need a self call > > so, it would be like this: > > self afterDOCTYPEPublicKeywordState value: currentCharacter. > > but that is also wrong from a design point of view (anti demeters law). So, you better create a (perhaps private) method who does the assignment. And then you have something like this: > > self afterDOCTYPEPublicKeywordState: currentCharacter. > > Esteban > > > > If I move the method call outside outside the ifTrue block to the ifFalse block it doesnât complain. > > Is the problem because of nested blocks ? If thatâs the case then what would be a good work around ? > > > > > Thanks > Mohammad

March 24, 2013

Re: [Pharo-users] Method Calling Inside Nested Blocks

by Ben Coman

Hi Mohammad, It seems you are trying to learn Smalltalk by leaping straight into experimenting with your own code, and seems you have missed a few fundamentals that may end up being very frustrating for you. Sometimes when things "seem to work" this only reinforces your misconceptions. I think you would benefit a lot from stepping back a moment and working through the excellent (and free) Pharo By Example book [1] - particularly Chapter 4 "Understanding message syntax" - but don't skip the rest of it or you will miss a lot of useful stuff. You will get best results if you use the image revision [2] matching the one the book was written for. [1] http://gforge.inria.fr/frs/download.php/25599/PBE1-2009-10-28.pdf [2] http://gforge.inria.fr/frs/download.php/31048/PBE-OneClick-1.1.app.zip regards -ben Mohammad Al Houssami (Alumni) wrote: > Probably because I am not using dots except at the end of blocks which I think is wrong. > This is a sample of what I had earlier: > currentCharacter = CHARACTERTABULATION ifTrue: [anythingElseBoolean:= false > AfterDOCTYPENameState value: currentCharacter ]. > There should be a dot after false right ? Once I add the dot I get a complain. > > > From: pharo-users-bounces(a)lists.gforge.inria.fr [mailto:pharo-users-bounces@lists.gforge.inria.fr] On Behalf Of Esteban Lorenzano > Sent: Saturday, March 23, 2013 3:09 PM > To: A friendly place where any question about pharo is welcome > Subject: Re: [Pharo-users] Method Calling Inside Nested Blocks > > if it is a method, it needs the receiver, in this case "self" (remember, any call in smalltalk is: receiver+message). > If for some weird reason you did not need it before (like some chained call effect), that was just by chance... you just were lucky before :) > > Esteban > > On Mar 23, 2013, at 1:58 PM, "Mohammad Al Houssami (Alumni)" <mha53(a)mail.aub.edu<mailto:mha53@mail.aub.edu>> wrote: > > > So the method declaration should be self afterDOCTYPEPublicKeywordState: currentCharacter. ? > > But I have been doing the same for quite some time and I wasn't getting any complains. This is the first time and the only thing that changed is that I have two blocks in this case. As I said earlier if I move the method call outside the block it works with no complains :) > > I'll change the names of all my methods to camel case. Thanks for that > > > From: pharo-users-bounces(a)lists.gforge.inria.fr<mailto:pharo-users-bounces@lists.gforge.inria.fr> [mailto:pharo-users-bounces@lists.gforge.inria.fr<mailto:users-bounces@lists.gforge.inria.fr>] On Behalf Of Esteban Lorenzano > Sent: Saturday, March 23, 2013 2:52 PM > To: A friendly place where any question about pharo is welcome > Subject: Re: [Pharo-users] Method Calling Inside Nested Blocks > > > On Mar 23, 2013, at 12:31 PM, "Mohammad Al Houssami (Alumni)" <mha53(a)mail.aub.edu<mailto:mha53@mail.aub.edu>> wrote: > > > > Hello everyone > > I was trying to save my method which has the below piece of code > > anythingElseBoolean = false ifFalse: [ > doctypeString := reader next: 6 > doctypeString asLowercase = 'public' ifTrue: [ > AfterDOCTYPEPublicKeywordState value: currentCharacter > ] > > I get a complain that the AfterDOCTYPEPublicKeywordState is unknown even though I have a method with this name. > > AfterDOCTYPEPublicKeywordState is a METHOD???? > then, you are missing some points: > > 1) it does not conforms conventions (it should start with lowercase) > 2) you need a self call > > so, it would be like this: > > self afterDOCTYPEPublicKeywordState value: currentCharacter. > > but that is also wrong from a design point of view (anti demeters law). So, you better create a (perhaps private) method who does the assignment. And then you have something like this: > > self afterDOCTYPEPublicKeywordState: currentCharacter. > > Esteban > > > > If I move the method call outside outside the ifTrue block to the ifFalse block it doesn't complain. > > Is the problem because of nested blocks ? If that's the case then what would be a good work around ? > > > > > Thanks > Mohammad > > >

March 23, 2013

Re: [Pharo-users] Tiling Window Manager port to Pharo 2.0

by Tudor Girba

If you commit, we give you a slot to demo the TillingWindowManager. Just let me know :). Cheers, Doru On Mar 23, 2013, at 11:05 AM, laurent laffont <laurent.laffont(a)gmail.com> wrote: > On Fri, Mar 22, 2013 at 10:58 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Great. > > It would be so cool to see a demo of this at PharoConf :) > > I'm trying to come on Wednesday, 3. > > Laurent > > > > Cheers, > Doru > > > On Thu, Mar 21, 2013 at 10:25 PM, laurent laffont <laurent.laffont(a)gmail.com> wrote: > Hi, > > Tiling Window Manager is ported to Pharo 2.0. Configuration in MetaRepoForPharo20. > > Now hosted on SmalltalkHub http://smalltalkhub.com/#!/~LaurentLaffont/TilingWindowManager > > Add the ability to cycle clockwise / counter clockwise among visible windows using Cmd+R,> and Cmd+R,< > > > > Thanks for Pharo 2.0, it feels really better. > > > Laurent Laffont > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- www.tudorgirba.com "We cannot reach the flow of things unless we let go."

March 23, 2013

Re: [Pharo-users] Method Calling Inside Nested Blocks

by Mohammad Al Houssami (Alumni)

This makes sense now. Thanks for clarifying the issue Esteban. Much appreciated :) From: pharo-users-bounces(a)lists.gforge.inria.fr [mailto:pharo-users-bounces@lists.gforge.inria.fr] On Behalf Of Esteban Lorenzano Sent: Saturday, March 23, 2013 3:23 PM To: A friendly place where any question about pharo is welcome Subject: Re: [Pharo-users] Method Calling Inside Nested Blocks yes, you need to end the statement (with a dot), then add the receiver. btw... the compiler will not complain if you do not put a dot, but your code will not work, because the compiler will interpret that you are sending the message AfterDOCTYPENameState to the object "false"... and then when you reach that place in your execution, you will have a doesNotUnderstand error :) Esteban On Mar 23, 2013, at 2:14 PM, "Mohammad Al Houssami (Alumni)" <mha53(a)mail.aub.edu<mailto:mha53@mail.aub.edu>> wrote: Probably because I am not using dots except at the end of blocks which I think is wrong. This is a sample of what I had earlier: currentCharacter = CHARACTERTABULATION ifTrue: [anythingElseBoolean:= false AfterDOCTYPENameState value: currentCharacter ]. There should be a dot after false right ? Once I add the dot I get a complain. From: pharo-users-bounces(a)lists.gforge.inria.fr<mailto:pharo-users-bounces@lists.gforge.inria.fr> [mailto:pharo-users-bounces@lists.gforge.inria.fr<mailto:users-bounces@lists.gforge.inria.fr>] On Behalf Of Esteban Lorenzano Sent: Saturday, March 23, 2013 3:09 PM To: A friendly place where any question about pharo is welcome Subject: Re: [Pharo-users] Method Calling Inside Nested Blocks if it is a method, it needs the receiver, in this case "self" (remember, any call in smalltalk is: receiver+message). If for some weird reason you did not need it before (like some chained call effect), that was just by chance... you just were lucky before :) Esteban On Mar 23, 2013, at 1:58 PM, "Mohammad Al Houssami (Alumni)" <mha53(a)mail.aub.edu<mailto:mha53@mail.aub.edu>> wrote: So the method declaration should be self afterDOCTYPEPublicKeywordState: currentCharacter. ? But I have been doing the same for quite some time and I wasn't getting any complains. This is the first time and the only thing that changed is that I have two blocks in this case. As I said earlier if I move the method call outside the block it works with no complains :) I'll change the names of all my methods to camel case. Thanks for that From: pharo-users-bounces(a)lists.gforge.inria.fr<mailto:pharo-users-bounces@lists.gforge.inria.fr> [mailto:pharo-users-bounces@lists.gforge.inria.fr<mailto:users-bounces@lists.gforge.inria.fr>] On Behalf Of Esteban Lorenzano Sent: Saturday, March 23, 2013 2:52 PM To: A friendly place where any question about pharo is welcome Subject: Re: [Pharo-users] Method Calling Inside Nested Blocks On Mar 23, 2013, at 12:31 PM, "Mohammad Al Houssami (Alumni)" <mha53(a)mail.aub.edu<mailto:mha53@mail.aub.edu>> wrote: Hello everyone I was trying to save my method which has the below piece of code anythingElseBoolean = false ifFalse: [ doctypeString := reader next: 6 doctypeString asLowercase = 'public' ifTrue: [ AfterDOCTYPEPublicKeywordState value: currentCharacter ] I get a complain that the AfterDOCTYPEPublicKeywordState is unknown even though I have a method with this name. AfterDOCTYPEPublicKeywordState is a METHOD???? then, you are missing some points: 1) it does not conforms conventions (it should start with lowercase) 2) you need a self call so, it would be like this: self afterDOCTYPEPublicKeywordState value: currentCharacter. but that is also wrong from a design point of view (anti demeters law). So, you better create a (perhaps private) method who does the assignment. And then you have something like this: self afterDOCTYPEPublicKeywordState: currentCharacter. Esteban If I move the method call outside outside the ifTrue block to the ifFalse block it doesn't complain. Is the problem because of nested blocks ? If that's the case then what would be a good work around ? Thanks Mohammad

March 23, 2013

Re: [Pharo-users] Method Calling Inside Nested Blocks

by Esteban Lorenzano

yes, you need to end the statement (with a dot), then add the receiver. btw... the compiler will not complain if you do not put a dot, but your code will not work, because the compiler will interpret that you are sending the message AfterDOCTYPENameState to the object "false"... and then when you reach that place in your execution, you will have a doesNotUnderstand error :) Esteban On Mar 23, 2013, at 2:14 PM, "Mohammad Al Houssami (Alumni)" <mha53(a)mail.aub.edu> wrote: > Probably because I am not using dots except at the end of blocks which I think is wrong. > This is a sample of what I had earlier: > currentCharacter = CHARACTERTABULATION ifTrue: [anythingElseBoolean:= false > AfterDOCTYPENameState value: currentCharacter ]. > There should be a dot after false right ? Once I add the dot I get a complain. > > > From: pharo-users-bounces(a)lists.gforge.inria.fr [mailto:pharo-users-bounces@lists.gforge.inria.fr] On Behalf Of Esteban Lorenzano > Sent: Saturday, March 23, 2013 3:09 PM > To: A friendly place where any question about pharo is welcome > Subject: Re: [Pharo-users] Method Calling Inside Nested Blocks > > if it is a method, it needs the receiver, in this case "self" (remember, any call in smalltalk is: receiver+message). > If for some weird reason you did not need it before (like some chained call effect), that was just by chance... you just were lucky before :) > > Esteban > > On Mar 23, 2013, at 1:58 PM, "Mohammad Al Houssami (Alumni)" <mha53(a)mail.aub.edu> wrote: > > > So the method declaration should be self afterDOCTYPEPublicKeywordState: currentCharacter. ? > > But I have been doing the same for quite some time and I wasnât getting any complains. This is the first time and the only thing that changed is that I have two blocks in this case. As I said earlier if I move the method call outside the block it works with no complains J > > I'll change the names of all my methods to camel case. Thanks for that > > > From: pharo-users-bounces(a)lists.gforge.inria.fr [mailto:pharo-users-bounces@lists.gforge.inria.fr] On Behalf Of Esteban Lorenzano > Sent: Saturday, March 23, 2013 2:52 PM > To: A friendly place where any question about pharo is welcome > Subject: Re: [Pharo-users] Method Calling Inside Nested Blocks > > > On Mar 23, 2013, at 12:31 PM, "Mohammad Al Houssami (Alumni)" <mha53(a)mail.aub.edu> wrote: > > > > Hello everyone > > I was trying to save my method which has the below piece of code > > anythingElseBoolean = false ifFalse: [ > doctypeString := reader next: 6 > doctypeString asLowercase = 'public' ifTrue: [ > AfterDOCTYPEPublicKeywordState value: currentCharacter > ] > > I get a complain that the AfterDOCTYPEPublicKeywordState is unknown even though I have a method with this name. > > AfterDOCTYPEPublicKeywordState is a METHOD???? > then, you are missing some points: > > 1) it does not conforms conventions (it should start with lowercase) > 2) you need a self call > > so, it would be like this: > > self afterDOCTYPEPublicKeywordState value: currentCharacter. > > but that is also wrong from a design point of view (anti demeters law). So, you better create a (perhaps private) method who does the assignment. And then you have something like this: > > self afterDOCTYPEPublicKeywordState: currentCharacter. > > Esteban > > > > If I move the method call outside outside the ifTrue block to the ifFalse block it doesnât complain. > > Is the problem because of nested blocks ? If thatâs the case then what would be a good work around ? > > > > > Thanks > Mohammad

March 23, 2013

Re: [Pharo-users] Method Calling Inside Nested Blocks

by Mohammad Al Houssami (Alumni)

Probably because I am not using dots except at the end of blocks which I think is wrong. This is a sample of what I had earlier: currentCharacter = CHARACTERTABULATION ifTrue: [anythingElseBoolean:= false AfterDOCTYPENameState value: currentCharacter ]. There should be a dot after false right ? Once I add the dot I get a complain. From: pharo-users-bounces(a)lists.gforge.inria.fr [mailto:pharo-users-bounces@lists.gforge.inria.fr] On Behalf Of Esteban Lorenzano Sent: Saturday, March 23, 2013 3:09 PM To: A friendly place where any question about pharo is welcome Subject: Re: [Pharo-users] Method Calling Inside Nested Blocks if it is a method, it needs the receiver, in this case "self" (remember, any call in smalltalk is: receiver+message). If for some weird reason you did not need it before (like some chained call effect), that was just by chance... you just were lucky before :) Esteban On Mar 23, 2013, at 1:58 PM, "Mohammad Al Houssami (Alumni)" <mha53(a)mail.aub.edu<mailto:mha53@mail.aub.edu>> wrote: So the method declaration should be self afterDOCTYPEPublicKeywordState: currentCharacter. ? But I have been doing the same for quite some time and I wasn't getting any complains. This is the first time and the only thing that changed is that I have two blocks in this case. As I said earlier if I move the method call outside the block it works with no complains :) I'll change the names of all my methods to camel case. Thanks for that From: pharo-users-bounces(a)lists.gforge.inria.fr<mailto:pharo-users-bounces@lists.gforge.inria.fr> [mailto:pharo-users-bounces@lists.gforge.inria.fr<mailto:users-bounces@lists.gforge.inria.fr>] On Behalf Of Esteban Lorenzano Sent: Saturday, March 23, 2013 2:52 PM To: A friendly place where any question about pharo is welcome Subject: Re: [Pharo-users] Method Calling Inside Nested Blocks On Mar 23, 2013, at 12:31 PM, "Mohammad Al Houssami (Alumni)" <mha53(a)mail.aub.edu<mailto:mha53@mail.aub.edu>> wrote: Hello everyone I was trying to save my method which has the below piece of code anythingElseBoolean = false ifFalse: [ doctypeString := reader next: 6 doctypeString asLowercase = 'public' ifTrue: [ AfterDOCTYPEPublicKeywordState value: currentCharacter ] I get a complain that the AfterDOCTYPEPublicKeywordState is unknown even though I have a method with this name. AfterDOCTYPEPublicKeywordState is a METHOD???? then, you are missing some points: 1) it does not conforms conventions (it should start with lowercase) 2) you need a self call so, it would be like this: self afterDOCTYPEPublicKeywordState value: currentCharacter. but that is also wrong from a design point of view (anti demeters law). So, you better create a (perhaps private) method who does the assignment. And then you have something like this: self afterDOCTYPEPublicKeywordState: currentCharacter. Esteban If I move the method call outside outside the ifTrue block to the ifFalse block it doesn't complain. Is the problem because of nested blocks ? If that's the case then what would be a good work around ? Thanks Mohammad

March 23, 2013

Re: [Pharo-users] Method Calling Inside Nested Blocks

by Esteban Lorenzano

if it is a method, it needs the receiver, in this case "self" (remember, any call in smalltalk is: receiver+message). If for some weird reason you did not need it before (like some chained call effect), that was just by chance... you just were lucky before :) Esteban On Mar 23, 2013, at 1:58 PM, "Mohammad Al Houssami (Alumni)" <mha53(a)mail.aub.edu> wrote: > So the method declaration should be self afterDOCTYPEPublicKeywordState: currentCharacter. ? > > But I have been doing the same for quite some time and I wasnât getting any complains. This is the first time and the only thing that changed is that I have two blocks in this case. As I said earlier if I move the method call outside the block it works with no complains J > > I'll change the names of all my methods to camel case. Thanks for that > > > From: pharo-users-bounces(a)lists.gforge.inria.fr [mailto:pharo-users-bounces@lists.gforge.inria.fr] On Behalf Of Esteban Lorenzano > Sent: Saturday, March 23, 2013 2:52 PM > To: A friendly place where any question about pharo is welcome > Subject: Re: [Pharo-users] Method Calling Inside Nested Blocks > > > On Mar 23, 2013, at 12:31 PM, "Mohammad Al Houssami (Alumni)" <mha53(a)mail.aub.edu> wrote: > > > Hello everyone > > I was trying to save my method which has the below piece of code > > anythingElseBoolean = false ifFalse: [ > doctypeString := reader next: 6 > doctypeString asLowercase = 'public' ifTrue: [ > AfterDOCTYPEPublicKeywordState value: currentCharacter > ] > > I get a complain that the AfterDOCTYPEPublicKeywordState is unknown even though I have a method with this name. > > AfterDOCTYPEPublicKeywordState is a METHOD???? > then, you are missing some points: > > 1) it does not conforms conventions (it should start with lowercase) > 2) you need a self call > > so, it would be like this: > > self afterDOCTYPEPublicKeywordState value: currentCharacter. > > but that is also wrong from a design point of view (anti demeters law). So, you better create a (perhaps private) method who does the assignment. And then you have something like this: > > self afterDOCTYPEPublicKeywordState: currentCharacter. > > Esteban > > > If I move the method call outside outside the ifTrue block to the ifFalse block it doesnât complain. > > Is the problem because of nested blocks ? If thatâs the case then what would be a good work around ? > > > > Thanks > Mohammad

March 23, 2013

Re: [Pharo-users] Method Calling Inside Nested Blocks

by Mohammad Al Houssami (Alumni)

I will be using petit parser at some point. Im currently doing it by hand to learn smalltalk and to get used to the requirements and all the things that come up. I think when I have a good grip on these I can move on to PetitParser. I made sure no weird characters are there but still doesn't work. Attached is the whole thing. -----Original Message----- From: pharo-users-bounces(a)lists.gforge.inria.fr [mailto:pharo-users-bounces@lists.gforge.inria.fr] On Behalf Of stephane ducasse Sent: Saturday, March 23, 2013 2:51 PM To: A friendly place where any question about pharo is welcome Subject: Re: [Pharo-users] Method Calling Inside Nested Blocks the following in syntactically valid. May be you pasted a strange character in your method. > anythingElseBoolean = false ifFalse: [ > doctypeString := reader next: 6. > doctypeString asLowercase = 'public' ifTrue: [ > AfterDOCTYPEPublicKeywordState value: currentCharacter > ] ] Now I think that building a HTML parser by hand in 2012 is a strange exercise when there are compiler compiler or cool framework for parsing like PetitParser. Stef

March 23, 2013