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

Re: [Pharo-project] Issue 1292: Code Critics RBCollectionCopyEmptyRule has incorrect selector

by Lukas Renggli

Thank you. I fixed and closed this issue. Lukas 2009/10/9 Stan Shepherd <stan.shepherd414(a)gmail.com>: > > This rule is checking for method copyEmpty: instead of copyEmpty > > Revised version at > http://code.google.com/p/pharo/issues/detail?id=1292&sort=-id&colspec=ID%20… > > ...Stan > > -- > View this message in context: http://n2.nabble.com/Issue-1292-Code-Critics-RBCollectionCopyEmptyRule-has-… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > 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

Oct. 12, 2009

[Pharo-project] ODBC

by Carlos Crosetti

How is the ODBC port to Pharo going on? -----Mensaje original----- De: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr]En nombre de Schwab,Wilhelm K Enviado el: Martes, 01 de Septiembre de 2009 05:15 p.m. Para: Pharo-project(a)lists.gforge.inria.fr Asunto: [Pharo-project] ODBCWarning The porting continues... It is getting closer to doing something. It just raised an ODBCWarning about the server changing the language to us_english. Any ideas? Either I do not care or should set it up front?? One thing really surprised me, and note that I might have brought this on myself (though I think that is unlikely) by messing with startup and shutdown: the ODBCLibrary was stubbornly clinging to the Linux library from my home machine. I finally used ODBCLibrary default initialize. which seemed to put an end to the separation anxiety. Is there a better fix? I suppose I should try this in a clean image to see if there is really a problem therein, but that will be a little hard to do without a lot of my code, almost any of which either depends on changes I have made or could have caused the problem. Maybe I should ask whether some of you use ODBC on Windows and Linux and have no problems moving between the machines. Bill _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Internal Virus Database is out-of-date. Checked by AVG. Version: 7.5.560 / Virus Database: 269.21.6/1323 - Release Date: 10/03/2008 11:07 a.m.

Oct. 12, 2009

[Pharo-project] Debugger (Array does not understand: #empty)

by Ramiro Diaz Trepat

Using the latests Pharo image, I get the exception on the subject when clicking on any part of the stack.Is this a known issue?

Oct. 11, 2009

Re: [Pharo-project] PackageOrganizer vs Package class side

by Schwab,Wilhelm K

Stef, I'm not sure I'm following what you mean by a single class. I would probably go for a singleton manager and a package class with instances for each package. Loosely related , it would be _really_ nice to be able to assign multiple categories to methods. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse Sent: Sunday, October 11, 2009 2:36 PM To: Pharo Development Subject: [Pharo-project] PackageOrganizer vs Package class side Hi all I coded a bit with david today on the package support and I would like to know what you think about having Package class side methods for register, named: ...... vs having and explicit separate class. I'm tend towards having one single class. Right now in Pharo packageInfo and PackageOrganizer responsibility are not that clear. Stef _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 11, 2009

Re: [Pharo-project] [Seaside] Komanche ?

by Ramiro Diaz Trepat

Hi Adrian, I did open both images with the same VM. I am sure this must be the problem then. As I said in one of the mails, the problem in my case went away when I bounced all the images. It only happens in the Mac VM then? Do we need to report this bug somewhere or is it already reported? Cheers r On Sun, Oct 11, 2009 at 8:56 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Did you open another image with the same VM? There is a wired behavior of > the Mac VM that makes the second image listen on the same ports as the > already running image. This may (or may not) be related. > > See > http://lists.squeakfoundation.org/pipermail/vm-dev/2009-June/002726.html > > Adrian > > > On Oct 11, 2009, at 17:18 , Ramiro Diaz Trepat wrote: > > Robert, can you see your port still listening with this command ? >> >> sudo lsof -i -P | grep -i listen >> >> >> >> >> On Sun, Oct 11, 2009 at 3:53 PM, Ramiro Diaz Trepat >> <ramiro(a)diaztrepat.name>wrote: >> >> Ah, if Robert still has an image with the issue and if he does not mind >>> giving it away for autopsy, maybe someone could look at it :)May be John >>> Macintosh can help us. >>> >>> >>> >>> On Sun, Oct 11, 2009 at 3:49 PM, Robert Sirois <watchlala(a)hotmail.com >>> >wrote: >>> >>> I'm running the latest mac vm as well. I believe I attempted the same >>>> things to no avail. >>>> >>>> RS >>>> >>>> Date: Sun, 11 Oct 2009 16:39:37 +0200 >>>>> >>>> >>>> Subject: Re: [Seaside] Komanche ? >>>>> From: renggli(a)gmail.com >>>>> To: seaside(a)lists.squeakfoundation.org >>>>> >>>>> I use the same configuration with the 4.1.1beta2U VM. >>>>> >>>>> Lukas >>>>> >>>>> 2009/10/11 Ramiro Diaz Trepat <ramiro(a)diaztrepat.name>: >>>>> >>>>>> Correlation does not mean causality, I know. But in my case this >>>>>> >>>>> happened >>>> >>>>> right after saving my image, although I had saved it many times before >>>>>> without issues. >>>>>> Cheers >>>>>> >>>>>> >>>>>> On Sun, Oct 11, 2009 at 3:01 PM, Ramiro Diaz Trepat < >>>>>> >>>>> ramiro(a)diaztrepat.name> >>>> >>>>> wrote: >>>>>> >>>>>>> >>>>>>> Hi Lukas, >>>>>>> I am using the latest Pharo, and I have loaded Seaside with >>>>>>> >>>>>> ScriptLoader >>>> >>>>> loadSeaside30. I am using it on a Mac with Leopard. >>>>>>> I have managed to reuse that port, with random tests and I do not >>>>>>> >>>>>> believe >>>> >>>>> there may be causality here, but I will tell you anyway what I did. >>>>>>> When this happens, I removed the problematic adaptor from the Seaside >>>>>>> Control Panel and created a new one (on the same port), then I tried >>>>>>> >>>>>> closing >>>> >>>>> the image and restarting and it did not fix the problem. Although >>>>>>> >>>>>> when I >>>> >>>>> closed another non Seaside image I was running and then restarted the >>>>>>> problematic image it worked. >>>>>>> I wonder now if it is not a mac vm issue or socket issue. Robert, >>>>>>> >>>>>> are you >>>> >>>>> also running on a mac? >>>>>>> In spite I got the image working again, it is quite worring because >>>>>>> >>>>>> we >>>> >>>>> don't know the cause when an image stops answering requests (although >>>>>>> >>>>>> the >>>> >>>>> image itself was not hanged at all and kept working fine), and, most >>>>>>> >>>>>> weird >>>> >>>>> of all, there is no exception or trace of a fault happening. This is >>>>>>> >>>>>> really >>>> >>>>> what is making me wonder if it is not a low level socket issue that >>>>>>> >>>>>> never >>>> >>>>> gets to the image for it to throw an exception or anything at all. >>>>>>> Cheers >>>>>>> >>>>>>> r >>>>>>> >>>>>>> ps: I'm cross posting to Pharo because I believe this is not a >>>>>>> >>>>>> Seaside >>>> >>>>> issue. >>>>>>> >>>>>>> On Sun, Oct 11, 2009 at 12:13 PM, Robert Sirois < >>>>>>> >>>>>> watchlala(a)hotmail.com> >>>> >>>>> wrote: >>>>>>> >>>>>>>> >>>>>>>> I'm using Pharo 1.0.10419, but I'm not sure how to check the other >>>>>>>> >>>>>>> two. I >>>> >>>>> think I'm still running 2.9 in the image I checked. >>>>>>>> >>>>>>>> RS >>>>>>>> >>>>>>>> Date: Sun, 11 Oct 2009 12:30:37 +0200 >>>>>>>>> Subject: Re: [Seaside] Komanche ? >>>>>>>>> From: renggli(a)gmail.com >>>>>>>>> To: seaside(a)lists.squeakfoundation.org >>>>>>>>> >>>>>>>>> I've never seen this problem before. >>>>>>>>> >>>>>>>>> What version of Pharo? Kom? Seaside? >>>>>>>>> >>>>>>>>> Lukas >>>>>>>>> >>>>>>>>> 2009/10/11 Robert Sirois <watchlala(a)hotmail.com>: >>>>>>>>> >>>>>>>>>> I've also had this problem for quite a while now and have not >>>>>>>>>> >>>>>>>>> found >>>> >>>>> any way to fix the problem either. >>>>>>>>>> >>>>>>>>>> RS >>>>>>>>>> >>>>>>>>>> Ramiro Diaz Trepat <ramiro(a)diaztrepat.name> wrote: >>>>>>>>>> >>>>>>>>>> Something really strange happened to me more than once now.In a >>>>>>>>>>> simple dev >>>>>>>>>>> image (Pharo + Seaside3 + Kom on a Mac) after saving the image >>>>>>>>>>> >>>>>>>>>> at >>>> >>>>> some >>>>>>>>>>> point, Komanche stops answering anything at all, althought the >>>>>>>>>>> >>>>>>>>>> port >>>> >>>>> keeps >>>>>>>>>>> listening (as listed on a terminal). >>>>>>>>>>> No errors are displayed anywere but the port becomes unusable >>>>>>>>>>> >>>>>>>>>> from >>>> >>>>> that >>>>>>>>>>> point on. >>>>>>>>>>> If I wish to continue using the same image I have to add another >>>>>>>>>>> adaptor in >>>>>>>>>>> the Seaside Control Panel and start again. >>>>>>>>>>> The "dead" ports never become usable again, not even stopping >>>>>>>>>>> >>>>>>>>>> and >>>> >>>>> removing >>>>>>>>>>> the adaptor and adding a new one. >>>>>>>>>>> I am not even sure that this is a Komanche issue, as I said no >>>>>>>>>>> >>>>>>>>>> error >>>> >>>>> of >>>>>>>>>>> anykind is visible. >>>>>>>>>>> Has anyone come across this before? >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> seaside mailing list >>>>>>>>>>> seaside(a)lists.squeakfoundation.org >>>>>>>>>>> >>>>>>>>>>> >>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>> >>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> seaside mailing list >>>>>>>>>> seaside(a)lists.squeakfoundation.org >>>>>>>>>> >>>>>>>>>> >>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>> >>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Lukas Renggli >>>>>>>>> http://www.lukas-renggli.ch >>>>>>>>> _______________________________________________ >>>>>>>>> seaside mailing list >>>>>>>>> seaside(a)lists.squeakfoundation.org >>>>>>>>> >>>>>>>>> >>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>> >>>>> >>>>>>>> ________________________________ >>>>>>>> Your E-mail and More On-the-Go. Get Windows Live Hotmail Free. Sign >>>>>>>> >>>>>>> up >>>> >>>>> now. >>>>>>>> _______________________________________________ >>>>>>>> seaside mailing list >>>>>>>> seaside(a)lists.squeakfoundation.org >>>>>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> seaside mailing list >>>>>> seaside(a)lists.squeakfoundation.org >>>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Lukas Renggli >>>>> http://www.lukas-renggli.ch >>>>> _______________________________________________ >>>>> seaside mailing list >>>>> seaside(a)lists.squeakfoundation.org >>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>> >>>> >>>> ------------------------------ >>>> Hotmail: Trusted email with Microsoftâs powerful SPAM protection. Sign >>>> up >>>> now. <http://clk.atdmt.com/GBL/go/177141664/direct/01/> >>>> >>>> _______________________________________________ >>>> seaside mailing list >>>> seaside(a)lists.squeakfoundation.org >>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>> >>>> >>>> >>> _______________________________________________ >> seaside mailing list >> seaside(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >

Oct. 11, 2009

Re: [Pharo-project] [Seaside] Komanche ?

by Adrian Lienhard

Did you open another image with the same VM? There is a wired behavior of the Mac VM that makes the second image listen on the same ports as the already running image. This may (or may not) be related. See http://lists.squeakfoundation.org/pipermail/vm-dev/2009-June/002726.html Adrian On Oct 11, 2009, at 17:18 , Ramiro Diaz Trepat wrote: > Robert, can you see your port still listening with this command ? > > sudo lsof -i -P | grep -i listen > > > > > On Sun, Oct 11, 2009 at 3:53 PM, Ramiro Diaz Trepat > <ramiro(a)diaztrepat.name>wrote: > >> Ah, if Robert still has an image with the issue and if he does not >> mind >> giving it away for autopsy, maybe someone could look at it :)May be >> John >> Macintosh can help us. >> >> >> >> On Sun, Oct 11, 2009 at 3:49 PM, Robert Sirois >> <watchlala(a)hotmail.com>wrote: >> >>> I'm running the latest mac vm as well. I believe I attempted the >>> same >>> things to no avail. >>> >>> RS >>> >>>> Date: Sun, 11 Oct 2009 16:39:37 +0200 >>> >>>> Subject: Re: [Seaside] Komanche ? >>>> From: renggli(a)gmail.com >>>> To: seaside(a)lists.squeakfoundation.org >>>> >>>> I use the same configuration with the 4.1.1beta2U VM. >>>> >>>> Lukas >>>> >>>> 2009/10/11 Ramiro Diaz Trepat <ramiro(a)diaztrepat.name>: >>>>> Correlation does not mean causality, I know. But in my case this >>> happened >>>>> right after saving my image, although I had saved it many times >>>>> before >>>>> without issues. >>>>> Cheers >>>>> >>>>> >>>>> On Sun, Oct 11, 2009 at 3:01 PM, Ramiro Diaz Trepat < >>> ramiro(a)diaztrepat.name> >>>>> wrote: >>>>>> >>>>>> Hi Lukas, >>>>>> I am using the latest Pharo, and I have loaded Seaside with >>> ScriptLoader >>>>>> loadSeaside30. I am using it on a Mac with Leopard. >>>>>> I have managed to reuse that port, with random tests and I do not >>> believe >>>>>> there may be causality here, but I will tell you anyway what I >>>>>> did. >>>>>> When this happens, I removed the problematic adaptor from the >>>>>> Seaside >>>>>> Control Panel and created a new one (on the same port), then I >>>>>> tried >>> closing >>>>>> the image and restarting and it did not fix the problem. >>>>>> Although >>> when I >>>>>> closed another non Seaside image I was running and then >>>>>> restarted the >>>>>> problematic image it worked. >>>>>> I wonder now if it is not a mac vm issue or socket issue. >>>>>> Robert, >>> are you >>>>>> also running on a mac? >>>>>> In spite I got the image working again, it is quite worring >>>>>> because >>> we >>>>>> don't know the cause when an image stops answering requests >>>>>> (although >>> the >>>>>> image itself was not hanged at all and kept working fine), and, >>>>>> most >>> weird >>>>>> of all, there is no exception or trace of a fault happening. >>>>>> This is >>> really >>>>>> what is making me wonder if it is not a low level socket issue >>>>>> that >>> never >>>>>> gets to the image for it to throw an exception or anything at >>>>>> all. >>>>>> Cheers >>>>>> >>>>>> r >>>>>> >>>>>> ps: I'm cross posting to Pharo because I believe this is not a >>> Seaside >>>>>> issue. >>>>>> >>>>>> On Sun, Oct 11, 2009 at 12:13 PM, Robert Sirois < >>> watchlala(a)hotmail.com> >>>>>> wrote: >>>>>>> >>>>>>> I'm using Pharo 1.0.10419, but I'm not sure how to check the >>>>>>> other >>> two. I >>>>>>> think I'm still running 2.9 in the image I checked. >>>>>>> >>>>>>> RS >>>>>>> >>>>>>>> Date: Sun, 11 Oct 2009 12:30:37 +0200 >>>>>>>> Subject: Re: [Seaside] Komanche ? >>>>>>>> From: renggli(a)gmail.com >>>>>>>> To: seaside(a)lists.squeakfoundation.org >>>>>>>> >>>>>>>> I've never seen this problem before. >>>>>>>> >>>>>>>> What version of Pharo? Kom? Seaside? >>>>>>>> >>>>>>>> Lukas >>>>>>>> >>>>>>>> 2009/10/11 Robert Sirois <watchlala(a)hotmail.com>: >>>>>>>>> I've also had this problem for quite a while now and have not >>> found >>>>>>>>> any way to fix the problem either. >>>>>>>>> >>>>>>>>> RS >>>>>>>>> >>>>>>>>> Ramiro Diaz Trepat <ramiro(a)diaztrepat.name> wrote: >>>>>>>>> >>>>>>>>>> Something really strange happened to me more than once >>>>>>>>>> now.In a >>>>>>>>>> simple dev >>>>>>>>>> image (Pharo + Seaside3 + Kom on a Mac) after saving the >>>>>>>>>> image >>> at >>>>>>>>>> some >>>>>>>>>> point, Komanche stops answering anything at all, althought >>>>>>>>>> the >>> port >>>>>>>>>> keeps >>>>>>>>>> listening (as listed on a terminal). >>>>>>>>>> No errors are displayed anywere but the port becomes unusable >>> from >>>>>>>>>> that >>>>>>>>>> point on. >>>>>>>>>> If I wish to continue using the same image I have to add >>>>>>>>>> another >>>>>>>>>> adaptor in >>>>>>>>>> the Seaside Control Panel and start again. >>>>>>>>>> The "dead" ports never become usable again, not even stopping >>> and >>>>>>>>>> removing >>>>>>>>>> the adaptor and adding a new one. >>>>>>>>>> I am not even sure that this is a Komanche issue, as I said >>>>>>>>>> no >>> error >>>>>>>>>> of >>>>>>>>>> anykind is visible. >>>>>>>>>> Has anyone come across this before? >>>>>>>>>> _______________________________________________ >>>>>>>>>> seaside mailing list >>>>>>>>>> seaside(a)lists.squeakfoundation.org >>>>>>>>>> >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> seaside mailing list >>>>>>>>> seaside(a)lists.squeakfoundation.org >>>>>>>>> >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Lukas Renggli >>>>>>>> http://www.lukas-renggli.ch >>>>>>>> _______________________________________________ >>>>>>>> seaside mailing list >>>>>>>> seaside(a)lists.squeakfoundation.org >>>>>>>> >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>>>> >>>>>>> ________________________________ >>>>>>> Your E-mail and More On-the-Go. Get Windows Live Hotmail Free. >>>>>>> Sign >>> up >>>>>>> now. >>>>>>> _______________________________________________ >>>>>>> seaside mailing list >>>>>>> seaside(a)lists.squeakfoundation.org >>>>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>>>> >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> seaside mailing list >>>>> seaside(a)lists.squeakfoundation.org >>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> Lukas Renggli >>>> http://www.lukas-renggli.ch >>>> _______________________________________________ >>>> seaside mailing list >>>> seaside(a)lists.squeakfoundation.org >>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>> >>> ------------------------------ >>> Hotmail: Trusted email with Microsoftâs powerful SPAM protection. >>> Sign up >>> now. <http://clk.atdmt.com/GBL/go/177141664/direct/01/> >>> >>> _______________________________________________ >>> seaside mailing list >>> seaside(a)lists.squeakfoundation.org >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>> >>> >> > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Oct. 11, 2009

[Pharo-project] Fwd: [squeak-dev] The Trunk: KernelTests-mha.100.mcz

by StÃ©phane Ducasse

Begin forwarded message: > From: commits(a)source.squeak.org > Date: October 11, 2009 8:22:52 PM GMT+02:00 > To: squeak-dev(a)lists.squeakfoundation.org > Subject: [squeak-dev] The Trunk: KernelTests-mha.100.mcz > Reply-To: squeak-dev(a)lists.squeakfoundation.org > > Michael Haupt uploaded a new version of KernelTests to project The > Trunk: > http://source.squeak.org/trunk/KernelTests-mha.100.mcz > > ==================== Summary ==================== > > Name: KernelTests-mha.100 > Author: mha > Time: 11 October 2009, 8:23:14 am > UUID: 2bceeeb6-b3e3-7a4e-9436-3010f8f730e7 > Ancestors: KernelTests-nice.99 > > made MethodPropertiesTest pass > > MethodPropertiesTest >> #propertyDictionaryFor: would ask the passed > AdditionalMethodState instance to answer its instance variable named > 'properties', which does not exist due to AdditionalMethodState's > being implemented as a variable subclass of Object, and hence > storing properties in immediate fields. > > Also, the tests did not honour the AdditionalMethodState protocol in > that they expected AdditionalMethodState >> #properties to return > nil in case there were no properties; however, it returns an empty > dictionary in these cases. The corresponding checks were changed > from #isNil to #isEmpty. > > =============== Diff against KernelTests-nice.99 =============== > > Item was changed: > ----- Method: MethodPropertiesTest>>testAt (in category 'testing') > ----- > testAt > self should: [ method properties at: #zork ] raise: Error. > + self assert: (self propertyDictionaryFor: method) isEmpty. > - self assert: (self propertyDictionaryFor: method) isNil. > method properties at: #zork put: 'hello'. > self assert: (method properties at: #zork) = 'hello'.! > > Item was changed: > ----- Method: MethodPropertiesTest>>testRemoveKey (in category > 'testing') ----- > testRemoveKey > method properties at: #zork put: 'hello'. > self should: [ method properties removeKey: #halt ] raise: Error. > self assert: (method properties removeKey: #zork) = 'hello'. > + self assert: (self propertyDictionaryFor: method) isEmpty. > - self assert: (self propertyDictionaryFor: method) isNil. > self should: [ method properties removeKey: #zork ] raise: Error. > + self assert: (self propertyDictionaryFor: method) isEmpty.! > - self assert: (self propertyDictionaryFor: method) isNil.! > > Item was changed: > ----- Method: MethodPropertiesTest>>testAtIfAbsent (in category > 'testing') ----- > testAtIfAbsent > self assert: (method properties at: #zork ifAbsent: [ 'hello' ]) = > 'hello'. > + self assert: (self propertyDictionaryFor: method) isEmpty. > - self assert: (self propertyDictionaryFor: method) isNil. > method properties at: #zork put: 'hi'. > self assert: (method properties at: #zork ifAbsent: [ 'hello' ]) = > 'hi'.! > > Item was changed: > ----- Method: MethodPropertiesTest>>testIncludesKey (in category > 'testing') ----- > testIncludesKey > self deny: (method properties includesKey: #zork). > + self assert: (self propertyDictionaryFor: method) isEmpty. > - self assert: (self propertyDictionaryFor: method) isNil. > method properties at: #zork put: 123. > self assert: (method properties includesKey: #zork).! > > Item was changed: > ----- Method: MethodPropertiesTest>>testRemoveKeyifAbsent (in > category 'testing') ----- > testRemoveKeyifAbsent > method properties at: #zork put: 'hello'. > self assert: (method properties removeKey: #halt ifAbsent: > [ 'hi' ]) = 'hi'. > self assert: (method properties removeKey: #zork ifAbsent: > [ 'hi' ]) = 'hello'. > + self assert: (self propertyDictionaryFor: method) isEmpty. > - self assert: (self propertyDictionaryFor: method) isNil. > self should: (method properties removeKey: #zork ifAbsent: > [ 'hi' ]) = 'hi'. > + self assert: (self propertyDictionaryFor: method) isEmpty.! > - self assert: (self propertyDictionaryFor: method) isNil.! > > Item was changed: > ----- Method: MethodPropertiesTest>>propertyDictionaryFor: (in > category 'private') ----- > propertyDictionaryFor: aMethod > + ^ aMethod properties properties! > - ^ aMethod properties instVarNamed: 'properties'.! > >

Oct. 11, 2009

[Pharo-project] PackageOrganizer vs Package class side

by StÃ©phane Ducasse

Hi all I coded a bit with david today on the package support and I would like to know what you think about having Package class side methods for register, named: ...... vs having and explicit separate class. I'm tend towards having one single class. Right now in Pharo packageInfo and PackageOrganizer responsibility are not that clear. Stef

Oct. 11, 2009

Re: [Pharo-project] Pretty print doesn't work on Traits with OB Package Browser

by StÃ©phane Ducasse

It should be fixed with the latest dev. Can somebody confirm? Stef On Oct 11, 2009, at 6:06 PM, Marcus Denker wrote: > > On 09.10.2009, at 11:41, Mariano Martinez Peck wrote: > >> This bug is present again :( >> >> http://code.google.com/p/pharo/issues/detail?id=1076 >> > I have un-closed the bug-report. > > Marcus > >> >> >> On Fri, Aug 21, 2009 at 2:42 PM, Mariano Martinez Peck <marianopeck(a)gmail.com >>> wrote: >> Yep. It is already fixed now. See http://code.google.com/p/pharo/issues/detail?id=1076 >> >> No need to integrate as it is in AST package (it will be integrated >> in next Pharo image I guess). >> >> Best, >> >> Mariano >> >> >> On Fri, Aug 21, 2009 at 3:40 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr >>> wrote: >> Do you have the solution to this problem? >> >> Stef >> >> On Aug 20, 2009, at 8:10 PM, Alexandre Bergel wrote: >> >>> Well spotted. I think the Traits package should be updated. No >> need of >>> class extension for this. >>> >>> Cheers, >>> Alexandre >>> >>> >>> On 19 Aug 2009, at 14:23, Mariano Martinez Peck wrote: >>> >>>> Hi! I opened this ticket: http://code.google.com/p/pharo/issues/detail?id=1076 >>>> >>>> This happens when using the OB Package Browser. I am using 10414. >>>> To reproduce: >>>> >>>> 1) Browse any Trait, for example TBehaviorCategorization >>>> 2) Select a method, right button, pretty print >>>> 3) You will get a Trait DNU #formatterClass >>>> >>>> The fix is easy: >>>> >>>> Crate in Trait a instance side method: >>>> >>>> formatterClass >>>> >>>> ^self class formatterClass >>>> >>>> >>>> The thing is that I don't know in which package should this be >>>> commited. AST? >>>> >>>> Best, >>>> >>>> Mariano >>>> >>>> ps: the bug report and fix is thanks to Marcelo Cortez >>>> >>>> >>>> _______________________________________________ >>>> 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 >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> 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 >> >> >> _______________________________________________ >> 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

Oct. 11, 2009

Re: [Pharo-project] Compiler question

by Marcus Denker

> > I am starting to port some code generating code of mine, and ran > into something that (on Dolphin) uses Compiler class>>compile:in:, > and the comment suggests that it creates a compiled method object > without adding it to the class' method dictionary. Similar methods > in Behavior do the same thing and then add the method to the > dictionary. > > Are similar things happening in Pharo? In principle, yes. In this case: -> it's not on the Class side of Compiler, but intance -> the selector is compile:in:notifying:ifFail: (with a nice do-your own exception handling) > It looks that way to me, but an expert confirmation or warning would > be appreciated. > Hello Bill, I don't exactly understand what you are asking. > However, if you want to know if there is methods to compile a source > without adding the resulting CompiledMethod to the any class > dictionary, the answer is yes, you can. You can do that, for > example, by sending the message > #compile:classified:notifying:trailer:ifFail:on:do: to any class. Yes. But if you use the short form available for this in Behavior, e.g. compile: compile:notifying: it *does* install the method. not good. > You can also send messages to compile and add to the > methodDictionary, you can browse the class Behavior to find what you > want. And rememeber to read the code... Marcus -- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile

Oct. 11, 2009