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

[Pharo-project] Class and Metaclass explanation in PBE
by Mariano Martinez Peck Oct. 21, 2009

Oct. 21, 2009

Hi folks. I was reading chapter 13 of PBE and there is something I don't understand. In page 283 it says: "Every metaclass is-a class, hence inherits from Class. Class in turn inherits from its superclasses, ClassDescription and Behavior." page 278, rule 8, it says: "Every metaclass inherits from Class and Behavior." However, if I open a class browser, I see that Metaclass inherits from ClassDescription, not Class. So, I don't understand :( Can anyone clarify me this? Thanks Mariano

3 3

[Pharo-project] scriptloader>>loadComanche
by Johan Brichau Oct. 21, 2009

Oct. 21, 2009

Hi there, Scriptloader has lost its #loadComanche method, which means that #loadSeaside30 does not work anymore. What happened? ;-) ---------------------------- Johan Brichau johan.brichau(a)uclouvain.be

5 11

[Pharo-project] bug with "Extended Search" of low panel of new inspector
by Mariano Martinez Peck Oct. 21, 2009

Oct. 21, 2009

Hi folks (Romain?) There is a bug with the NewInspector. To reproduce: 1) just inspect something. 2) now, in the inspector go to the lower panel and write something. 3) Select it, right button, and click on "Extended Search" I won't bring the extended search, but it will open again the context menu (as when you right click). Bug ticket: http://code.google.com/p/pharo/issues/detail?id=1350 BTW, can we please rename NewInspector to Inspector ??? Or at least the title of the windows. I think that names like "New Inspector" or "Shout Workspace" are difficult to understand for newcomers. So, I would change, at least, the windows title of them to "Inspector" and "Workspace"

3 2

Re: [Pharo-project] [squeak-dev] Re: Issue with traits
by Igor Stasenko Oct. 21, 2009

Oct. 21, 2009

2009/10/21 Andreas Raab <andreas.raab(a)gmx.de>: > Igor Stasenko wrote: >> >> now what i found interesting: >> >> (ABBAB methodDict at: #foo) == (ABBAC methodDict at: #foo) >> >> but as side effect, we got this one: >> >> (ABBAB methodDict at: #foo) methodClass Â ==> ABBAC >> >> which i find a bit disturbing :( > > Yes, seems wrong. VERY wrong. Try this: > > Object subclass: #BaseA > > BaseA>>foo > Â ^42 > > Object subclass: #BaseB > > BaseB>>foo > Â ^13 > > And then create subclasses of BaseA and BaseB which use your trait and have > the trait implementation use "^super foo". One of two things should happen: > > a) They both return the same (incorrect) value (which would be expected if > methodClass is the same). In this case it's just plain broken. > > b) They both return different values, in which case there is code that > handles super sends specifically and the sharing is simply an unnecessary > optimization. > > I hope it's the latter case which would mean you only need to throw out the > test for super sends and do whatever that code was doing to begin with ;-) > Ouch... so VM behavior depends on correct methodClass slot. Thanks for reminding! I remember that methodClass plays important role (and its important to have method and its methodClass being in sync with class where the method installed), but forgot the details :) That could lead to even worse results, if you use super sends, and then in base class , accessing the instance variables in base method. It could corrupt the memory & crash the VM. I hope this is already fixed, because the image where i checked it is quite old one - 3.10.2 > Cheers, > Â - Andreas -- Best regards, Igor Stasenko AKA sig.

1 0

[Pharo-project] Issue with traits
by Igor Stasenko Oct. 21, 2009

Oct. 21, 2009

Create a trait: Trait named: #ABBA uses: {} category: 'ABBA'. - add a method #foo to ABBA trait Then create 2 classes which using it: Object subclass: #ABBAB uses: ABBA instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'ABBA'. Object subclass: #ABBAC uses: ABBA instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'ABBA'. now what i found interesting: (ABBAB methodDict at: #foo) == (ABBAC methodDict at: #foo) but as side effect, we got this one: (ABBAB methodDict at: #foo) methodClass ==> ABBAC which i find a bit disturbing :( I'm not sure if given issue could have a major impact somewhere... But i would just #clone the trait method before installing it.. Yes, it takes more space, but it makes each of such methods unrelated. And i strongly assume that these methods should be unrelated, and moreover, recompiled for each class separately, because global var in one class could be a class var in another one, so a trait method, like: foo ^ Bar will behave depending on class environment. -- Best regards, Igor Stasenko AKA sig.

1 0

[Pharo-project] Issue 1282: a:=Array new: SmallInteger maxVal. returns methodContext versus memory allocation error (was: [Vm-dev] Array new: SmallInteger maxVal)
by Petr VÃ¡cha Oct. 21, 2009

Oct. 21, 2009

FYI ----- PÅ®VODNÃ ZPRÃVA ----- Od: "David T. Lewis" <lewis(a)mail.msen.com> Komu: "Squeak Virtual Machine Development Discussion" <vm-dev(a)lists.squeakfoundation.org> PÅedmÄt: Re: [Vm-dev] Array new: SmallInteger maxVal Datum: 21.10.2009 - 4:39:21 On Tue, Oct 06, 2009 at 06:58:30PM -0400, David T. Lewis wrote: > > On Tue, Oct 06, 2009 at 10:05:02PM +0200, Nicolas Cellier wrote: > > > > >From http://code.google.com/p/pharo/issues/detail?id=1282 > > Is this known? > > Thanks, it's known now :) > > Also added to Mantis at http://bugs.squeak.org/view.php?id=7405. > > Petr: Yes this is definitely a cool bug. A fix for this is on Mantis 7405 (http://bugs.squeak.org/view.php?id=7405) The VMMaker updates are in SqueakSource in VMMaker-dtl.142. A separate patch is needed for platforms/unix/vm/sqUnixMemory.c (see the Mantis report, patch also sent to Ian). I have not tested Windows or Mac OS, but the basic scenario now is that the VM will limit the size of memory increase requests to 31 bit integer so support code can check for overflows. The requests from the VM are guaranteed (I hope) be valid 31 bit integers. Allocation requests of > 950 MB seem to be possible, although I do not have enough memory on my PC to verify that it actually works. Limiting allocation requests to more reasonable limits would be the responsibility of the image. Dave

1 0

Re: [Pharo-project] scriptloader>>loadComanche
by Dale Henrichs Oct. 20, 2009

Oct. 20, 2009

Johan, Yes there was a recent change to Error handling in Pharo that broke Metacello (Error no longer resumable) that broke Metacello... I ran into that one yesterday on 10487 and updated the Seaside Metacello config (Seaside-Metacello-Configuration-dkh.15) with a fix. For Pharo 10487 you'll need to use Metacello 1.0-beta.6 or later... Naturally as I try to verify that there aren't any other problems I'm running into network problems:) Dale ----- "Johan Brichau" <johan.brichau(a)uclouvain.be> wrote: | On 20 Oct 2009, at 12:00, Torsten Bergmann wrote: | | >> We clearly need a universe like tools so that people can publish | and | >> maintain their add-ons. | > | > Yes, but we should be pragmatic for Seaside since it is the | "flagship" | > until we have the infrastructur set up. | > | > Maybe we should delete it from the core but we can the loading | support | > in the dev images. What do you all think? | | I just loaded metacello and used its seaside configuration to load the | | 3.0-alpha5 of seaside. | | It hits the 'reading a number failed' bug in 10487-DEV | | ...argh... | | | | ---------------------------- | Johan Brichau | johan.brichau(a)uclouvain.be | | | | | | _______________________________________________ | Pharo-project mailing list | Pharo-project(a)lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

3 2

Re: [Pharo-project] scriptloader>>loadComanche
by Ken G. Brown Oct. 20, 2009

Oct. 20, 2009

Here's a video from 4 months ago showing how to use Sake/Packages to load Seaside 3.0. <http://www.vimeo.com/groups/squeak/videos/5434330> Ken G. Brown At 2:37 PM +0200 10/20/09, pharo-project-request(a)lists.gforge.inria.fr apparently wrote: >Date: Tue, 20 Oct 2009 14:14:56 +0200 >From: Lukas Renggli <renggli(a)gmail.com> >Subject: Re: [Pharo-project] scriptloader>>loadComanche >To: Pharo-project(a)lists.gforge.inria.fr >Message-ID: > <67628d690910200514w25dbde7btf9e1533431a50132(a)mail.gmail.com> >Content-Type: text/plain; charset=ISO-8859-1 > >The following snippet loads Seaside 3.0: > >[ Gofer new > squeaksource: 'Seaside30'; > addPackage: 'LoadOrderTests'; > load ] > valueSupplyingAnswers: { > {'Load Seaside'. true}. > {'SqueakSource User Name'. ''}. > {'SqueakSource Password'. ''}. > {'Run tests'. false}. > } > >There are more scripts that I use to build images on the Pharo Wiki ><http://code.google.com/p/pharo/wiki/ImageBuildScripts>. > >Lukas > >2009/10/20 Johan Brichau <johan.brichau(a)uclouvain.be>: >> >> On 20 Oct 2009, at 12:00, Torsten Bergmann wrote: >> >>>> We clearly need a universe like tools so that people can publish and >>>> maintain their add-ons. >>> >>> Yes, but we should be pragmatic for Seaside since it is the "flagship" >>> until we have the infrastructur set up. >>> >>> Maybe we should delete it from the core but we can the loading support >>> in the dev images. What do you all think? >> >> I just loaded metacello and used its seaside configuration to load the >> 3.0-alpha5 of seaside. >> >> It hits the 'reading a number failed' bug in 10487-DEV >> >> ...argh... >> >> >> >> ---------------------------- >> Johan Brichau >> johan.brichau(a)uclouvain.be >> >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > >-- >Lukas Renggli >http://www.lukas-renggli.ch

1 0

[Pharo-project] About TestCase >> assert:
by Mariano Martinez Peck Oct. 20, 2009

Oct. 20, 2009

Hi folks:During this week someone wanted to use SqueakDBX in Squeak 3.8 and at the same time another person (thanks Marcelo Cortez!!!) has ported it to Dolphin. And I found something weird in TestCase >> assert: In Squeak 3.10 TestCase >> assert: aBooleanOrBlock Squeak 3.8, Dolphin and VAST (I don't know others) have: TestCase >> assert: aBoolean So...is there a reason of doing that? Is this expected? cheers mariano

8 24

Re: [Pharo-project] scriptloader>>loadComanche
by Dale Henrichs Oct. 20, 2009

Oct. 20, 2009

I believe that the change is a proper one, so I fixed my code rather than report a bug:) It is related to the the asNumber changes discussion. In Metacello I was using asNumber to parse versionStrings and on an Error I resumed with the string itself instead of the number. In 10470 that technique worked and in 10487 I got an IllegalResumeAttempt ...Looking closer I see that asNumber now raises an Error and it didn't before. So the change was in how asNumber behaves, not in how Errors behave...sorry for the FUD. Dale ----- "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> wrote: | Hi dale | | this is strange because I do not remember us integrating a changes | that would do that. | Can you confirm it? | Stef | | | On Oct 20, 2009, at 7:29 PM, Dale Henrichs wrote: | | > Johan, | > | > Yes there was a recent change to Error handling in Pharo that broke | | > Metacello (Error no longer resumable) that broke Metacello... I ran | | > into that one yesterday on 10487 and updated the Seaside Metacello | | > config (Seaside-Metacello-Configuration-dkh.15) with a fix. | > | > For Pharo 10487 you'll need to use Metacello 1.0-beta.6 or later... | > | > Naturally as I try to verify that there aren't any other problems | > I'm running into network problems:) | > | > Dale | > | > ----- "Johan Brichau" <johan.brichau(a)uclouvain.be> wrote: | > | > | On 20 Oct 2009, at 12:00, Torsten Bergmann wrote: | > | | > | >> We clearly need a universe like tools so that people can | publish | > | and | > | >> maintain their add-ons. | > | > | > | > Yes, but we should be pragmatic for Seaside since it is the | > | "flagship" | > | > until we have the infrastructur set up. | > | > | > | > Maybe we should delete it from the core but we can the loading | > | support | > | > in the dev images. What do you all think? | > | | > | I just loaded metacello and used its seaside configuration to load | | > the | > | | > | 3.0-alpha5 of seaside. | > | | > | It hits the 'reading a number failed' bug in 10487-DEV | > | | > | ...argh... | > | | > | | > | | > | ---------------------------- | > | Johan Brichau | > | johan.brichau(a)uclouvain.be | > | | > | | > | | > | | > | | > | _______________________________________________ | > | 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

3 5