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

Re: [Pharo-users] SandstoneDB on Pharo 2.0 - done - what next?

by Esteban Lorenzano

well, repository in squeaksource is open, so you should commit your changes. also, I noticed there is no "ConfigurationOfSandstoneDB"... if you are brave enough, you could also add a configuration to load it, and copy it to MetacelloRepository and/or MetaRepoForPharo20 :) cheers, Esteban ps: and thank you very much! :) On Apr 25, 2013, at 8:47 AM, Ingo Hohmann <pharo(a)ingohohmann.de> wrote: > Hi, > > because I haven't found a version of SondstoneDB for Pharo 2.0, I have > migrated it myself. > > All tests are green, except for 2 performance tests. > > Well, it's the first time I did anything on someone elses code, that's > worth sharing, so I'm a little bit unsure on the etiquette, and what to > do technically. > > > Kind regards, > > Ingo > >

April 25, 2013

SandstoneDB on Pharo 2.0 - done - what next?

by Ingo Hohmann

Hi, because I haven't found a version of SondstoneDB for Pharo 2.0, I have migrated it myself. All tests are green, except for 2 performance tests. Well, it's the first time I did anything on someone elses code, that's worth sharing, so I'm a little bit unsure on the etiquette, and what to do technically. Kind regards, Ingo

April 25, 2013

Re: [Pharo-users] Cannot be recompiled

by Mariano Martinez Peck

On Wed, Apr 24, 2013 at 10:08 AM, Martin Dias <tinchodias(a)gmail.com> wrote: > Hi, > > (forwarded from pharo-users) > > Object > subclass: #A > instanceVariableNames: '' > classVariableNames: '' > poolDictionaries: '' > category: 'Unclassified'. > > (Smalltalk at: #A) > subclass: #B > instanceVariableNames: '' > classVariableNames: '' > poolDictionaries: '' > category: 'Unclassified'. > > Object > variableSubclass: #A > instanceVariableNames: '' > classVariableNames: '' > poolDictionaries: '' > category: 'Unclassified'. > > I'm working in the "new class builder" [1]. It automatically propagates > this format change to the subclasses, instead of raising the error like the > current class builder does. ie, the class B becomes variable when A becomes > variable. > > Do you agree? > > What happens if a subclass was already variable but not simple variable, like byte or words? they will be changed? > Cheers, > Martin > > [1]: https://ci.inria.fr/pharo-contribution/job/Slot/ > > > > On Tue, Apr 23, 2013 at 2:05 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > >> Hi, >> >> In: >> >> Object >> subclass: #A >> instanceVariableNames: '' >> classVariableNames: '' >> poolDictionaries: '' >> category: 'Unclassified'. >> >> (Smalltalk at: #A) >> subclass: #B >> instanceVariableNames: '' >> classVariableNames: '' >> poolDictionaries: '' >> category: 'Unclassified'. >> >> Object >> variableSubclass: #A >> instanceVariableNames: '' >> classVariableNames: '' >> poolDictionaries: '' >> category: 'Unclassified'. >> >> ---> why do we raise the error "B cannot be recompiled"? >> >> what's the problem with reformatting subclasses automatically? >> >> best regards, >> Martin >> >> >> >> > -- Mariano http://marianopeck.wordpress.com

April 25, 2013

Re: [Pharo-users] Slot Image

by Camillo Bruni

On 2013-04-25, at 00:43, Paul Davidowitz <pdavidow(a)fastmail.fm> wrote: > Camillo Bruni <camillobruni@...> writes: > > ... >> There is also a very *old* image from back when we wrote the paper: >> https://dl.dropboxusercontent.com/u/18184943/SlotImage.zip >> Beware, it will only run with an old VM: http://www.squeakvm.org/index.html > ... > > Please provide instructions for unzipping and running the old image/VM > on a Windows7_32bit (also Windows7_64bit if available) platform. > Thanks, > -Paul For the unzipping part I cannot help you since it works out of the box on mac/linux. For the VM you can use one of the old squeak vms from here: http://files.pharo.org/vm/squeak/ let me know if you succeeded.

April 24, 2013

Re: [Pharo-users] Slot Image

by Paul Davidowitz

Camillo Bruni <camillobruni@...> writes: ... > There is also a very *old* image from back when we wrote the paper: > https://dl.dropboxusercontent.com/u/18184943/SlotImage.zip > Beware, it will only run with an old VM: http://www.squeakvm.org/index.html ... Please provide instructions for unzipping and running the old image/VM on a Windows7_32bit (also Windows7_64bit if available) platform. Thanks, -Paul

April 24, 2013

Re: [Pharo-users] Setters for instance variables

by Sean P. DeNigris

Mohammad Al Houssami (Alumni) wrote > What is the difference? To learn the basics, read one of the excellent free Smalltalk books, like Pharo By Example [1], in which you will find the answer to your question on page 82. [1] http://pharobyexample.org/ ----- Cheers, Sean -- View this message in context: http://forum.world.st/Setters-for-instance-variables-tp4683432p4683458.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 24, 2013

Re: [Pharo-users] Setters for instance variables

by Mohammad Al Houssami (Alumni)

Actually CamilLo you are right I do. I actually have everything on the class side and not on the instance side. What is the difference? And shall I assume it works if I move them to the instance side ? -----Original Message----- From: pharo-users-bounces(a)lists.gforge.inria.fr [mailto:pharo-users-bounces@lists.gforge.inria.fr] On Behalf Of Camillo Bruni Sent: Wednesday, April 24, 2013 9:14 PM To: A friendly place where any question about pharo is welcome Subject: Re: [Pharo-users] Setters for instance variables On 2013-04-24, at 21:46, "Mohammad Al Houssami (Alumni)" <mha53(a)mail.aub.edu> wrote: > Ok okay... im new here so I didn't know that. > So why is pharo complaining then ? I'd guess you installed the method on class side, and not instance side :)

April 24, 2013

Re: [Pharo-users] Setters for instance variables

by Camillo Bruni

On 2013-04-24, at 21:46, "Mohammad Al Houssami (Alumni)" <mha53(a)mail.aub.edu> wrote: > Ok okay... im new here so I didnât know that. > So why is pharo complaining then ? I'd guess you installed the method on class side, and not instance side :)

April 24, 2013

Re: [Pharo-users] Setters for instance variables

by Luc Fabresse

2013/4/24 Mohammad Al Houssami (Alumni) <mha53(a)mail.aub.edu> > Yes I do have them but without the ">>" signs > yes you should not see >> in the source code. >> is used by convention in books to express that a method belongs to a class. Example, if I write: aMethod ^1 you do not know which methods is it. But using: MyClass>>aMethod ^1 you know that is the one of MyClass > This is what I have inside the CharacterToken Class **** > > characterData: anObject**** > > characterData := anObject**** > > ** ** > > This is where pharo complains **** > > characterToken := CharacterToken new.**** > > *characterToken characterData: AMPERSAND.*** > > * > *It says it doesnât understand characterData though it is defined in the > CharacterToken class > ok I did not get where is your problem. can you send a small piece of your code? Luc > **** > > The setters and getters were generated by pharo. So im not sure about what > the >> is for > > > > > **** > > ** ** > > *From:* pharo-users-bounces(a)lists.gforge.inria.fr [mailto: > pharo-users-bounces(a)lists.gforge.inria.fr] *On Behalf Of *Luc Fabresse > *Sent:* Wednesday, April 24, 2013 8:10 PM > *To:* A friendly place where any question about pharo is welcome > *Subject:* Re: [Pharo-users] Setters for instance variables**** > > ** ** > > Hi,**** > > ** ** > > 2013/4/24 Mohammad Al Houssami (Alumni) <mha53(a)mail.aub.edu>**** > > Hello again,**** > > > If I have an instance variable A in ClassA and I want to use it in ClassB. > **** > > If I do the following in ClassB**** > > objectA := ClassA new.**** > > **** > > objectA A: "new value for A". > > **** > > Why doesnât this work? Isnt this calling the setter of A on the objectA ? > Pharo doesnât understand it for some reason .**** > > ** ** > > yes.**** > > but a setter is regular method.**** > > did you defined the method in ClassA.**** > > also, by convention method names start with a lowercase.**** > > Example:**** > > ** ** > > Object subclass: #ClassA**** > > iv: 'a'**** > > ** ** > > ClassA>>a: newValue**** > > a := newValue**** > > ** ** > > objA := ClassA new.**** > > objA a: 1**** > > ** ** > > Cheers,**** > > ** ** > > Luc **** > > ** ** > > **** > > **** > > ** ** >

April 24, 2013

Re: [Pharo-users] Setters for instance variables

by Mohammad Al Houssami (Alumni)

Ok okay... im new here so I didnât know that. So why is pharo complaining then ? -----Original Message----- From: pharo-users-bounces(a)lists.gforge.inria.fr [mailto:pharo-users-bounces@lists.gforge.inria.fr] On Behalf Of Igor Stasenko Sent: Wednesday, April 24, 2013 8:40 PM To: A friendly place where any question about pharo is welcome Subject: Re: [Pharo-users] Setters for instance variables Class>>method ..... simply a way to show code snippet for a method and to which class it should belong to. Note that this notation is not syntactically correct in smalltalk. On 24 April 2013 21:24, Mohammad Al Houssami (Alumni) <mha53(a)mail.aub.edu> wrote: > Yes I do have them but without the ">>" signs This is what I have > inside the CharacterToken Class > > characterData: anObject > > characterData := anObject > > > > This is where pharo complains > > characterToken := CharacterToken new. > > characterToken characterData: AMPERSAND. > > > It says it doesnât understand characterData though it is defined in > the CharacterToken class > > The setters and getters were generated by pharo. So im not sure about > what the >> is for > > > > > > > From: pharo-users-bounces(a)lists.gforge.inria.fr > [mailto:pharo-users-bounces@lists.gforge.inria.fr] On Behalf Of Luc > Fabresse > Sent: Wednesday, April 24, 2013 8:10 PM > To: A friendly place where any question about pharo is welcome > Subject: Re: [Pharo-users] Setters for instance variables > > > > Hi, > > > > 2013/4/24 Mohammad Al Houssami (Alumni) <mha53(a)mail.aub.edu> > > Hello again, > > > If I have an instance variable A in ClassA and I want to use it in ClassB. > > If I do the following in ClassB > > objectA := ClassA new. > > > > objectA A: "new value for A". > > Why doesnât this work? Isnt this calling the setter of A on the objectA ? > Pharo doesnât understand it for some reason . > > > > yes. > > but a setter is regular method. > > did you defined the method in ClassA. > > also, by convention method names start with a lowercase. > > Example: > > > > Object subclass: #ClassA > > iv: 'a' > > > > ClassA>>a: newValue > > a := newValue > > > > objA := ClassA new. > > objA a: 1 > > > > Cheers, > > > > Luc > > > > > > > > -- Best regards, Igor Stasenko.

April 24, 2013