- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Vm-dev] failing/errors Pharo Tests with CogVM
by Mariano Martinez Peck Sept. 23, 2010

Sept. 23, 2010

Ok....that's to all the responses. The thread is now far away my knoweldege, so I will naively ask: is it worth creating a Pharo 1.1.1 one click with CogVM? Marcus released a PharoCore 1.1.1 with changes for CogVM and some important fixes. I took that core image and I created a new dev. But before releasing, I run the tests and I found them. Seems you all discussed about the Float problems...but what about the others? I remember them and I thing they were fixed in newest versions of VMMaker. So...the question is now....are the failure/error of those tests means that Pharo is "unreleasable" with CogVM? Should we wait for the fix or we should release anyway? Thanks in advance, Mariano On Fri, Sep 17, 2010 at 8:20 PM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: > > > > On Thu, Sep 16, 2010 at 10:54 PM, Andreas Raab <andreas.raab(a)gmx.de>wrote: > >> >> On 9/16/2010 2:44 PM, Eliot Miranda wrote: >> >>> I realise we need to be more precise. Are you talking about NaNs >>> specifically or NaN and Inf? >>> >> >> NaN only. +-Inf are fine as they have a well-defined mathematical >> relationship over the set of numbers. NaN does not. >> >> >> The Squeak VM happily answers Inf from its >>> float primitives. In fact the only guard against a NaN or Inf result >>> being produced by the floating-point primitives is the guard against >>> dividing by zero. But e.g. in the interpreter (1.0e300 / 1.0e-300) >>> isInfinite and there is no failure. So specifically failing for aFloat >>> / 0.0 seems a bit of a fig leaf to me. >>> >>> So what would your ideal semantics be? >>> a) - fail whenever the result is Inf or NaN? >>> b) - fail whenever the result is NaN and allow aFloat / 0.0 to answer Inf >>> c) - fail whenever the result is NaN but fail aFloat / 0.0 >>> d) - the Interpreter status quo, fail only for aFloat / 0.0 >>> e) - never fail and answer Nan and Inf as specified in IEEE 754 >>> >>> The situation with VW before IEEE was that it did a) and we changed it >>> so that the mode switch selected either a) or e), with, IIRC, the >>> current default being e). >>> >> >> f) Fail whenever the result is NaN or when dividing by zero. >> > > OK, to be pedantic that's c) above. But fine. This is a reasonable choice. > > >> My preference for f) is that division by zero should be consistent between >> floating point numbers and integers. It would be strange if "1 / 0" => boom >> but "1.0 / 0" => Inf or "1 / 0.0" => Inf. *However* underflow isn't division >> by zero and may silently result in Inf. In other words: >> >> self should:[1.0 / 0.0] raise: ZeroDivide. >> >> but (#successor produces the smallest float larger than the receiver) >> >> self shouldnt:[1.0 / 0.0 successor] raise: Error. >> self assert: (1.0 / 0.0 successor) = Float infinity. >> >> Cheers, >> - Andreas >> > > >

1 1

Re: [Pharo-project] I am missing userful functionality?
by StÃ©phane Ducasse Sept. 23, 2010

Sept. 23, 2010

Hi igor I cannot help but indeed we need a real brand new classbuilder with a nice MOP for instance migrating too. We will start to work on that probably december/january. Stef On Sep 23, 2010, at 12:03 AM, Igor Stasenko wrote: > Hello, guys > > i want to do a simple thing, which can be expressed by following: > > oldClass replaceWith: newClass migrateInstances: [:inst | > ... ] > > In my case, first, i installing a WeakFinalizationRegistry class, > and then want to replace an old WeakRegistry class with it, > silently and painlessly. > > I end up with following script: > > | old new oldClass newClass | > old := OrderedCollection new. > new := OrderedCollection new. > > > "migrate instances" > WeakRegistry allInstancesDo: [:registry | | newr | > old add: registry. > newr := WeakFinalizationRegistry basicNew initialize. > registry migrateTo: newr. > new add: newr ]. > old asArray elementsForwardIdentityTo: new asArray. > > "replace the class" > > oldClass := WeakRegistry. > newClass := WeakFinalizationRegistry. > > Smalltalk forgetClass: #WeakFinalizationRegistry logged: false. > newClass superclass removeSubclass: newClass. > newClass setName: #WeakRegistry. > oldClass becomeForward: newClass. > > -- > > it looks a bit hackish, and i wonder how to do that in more 'standard' way. > > Initially replacing classes was: > > oldClass removeFromSystem. > newClass rename: #WeakRegistry > > the problem with that, is that all compiled methods , which was > referring to old class through association, > still using it, and to get rid of them i have to recompile them. > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

Re: [Pharo-project] Changes in external packages for Pharo 1.2
by StÃ©phane Ducasse Sept. 23, 2010

Sept. 23, 2010

keep it simple for now. Let us focus on fixing 1.2 > Hi folks. I would like to write now the changes for the development image for Pharo 1.2. > > Right now I have the following: > > - Let (load) NewInspector in the image, but put the old one as the default. Several people were against NewInspector. I like it for example, but anyway, if it is present in the image then I would be able to use it. > - Add Memory Monitor tool from Alexandre Bergel. > - Add AutoTest from Laurent Laffont. > - Add GoferProjectLoader from Esteban Lorenzano, to easily manage Metacello. > > For any package we include, it would be AWESOME to have: > - tests > - a Metacello configuration > > So, questions: > > 1) do you more ore less agree with them??? (we cannot be all agree with ALL items) > 2) for package developers: do you agree we include all of them in PharoDev? will you help maitaining them? are they all MIT? (I think so) Please, confirm us this. > 3) do you think there are more packages/projects we should include? What about, for example: > Keep that for later. > - WorkingSet from Romain Robbes > - Algernon (still doesn't work in 1.1) > - TDDFacilties from Hernan Wilkinson > - SimpleLogger from German Arduino > > I know this is not Dev, but I hope in Pharo1.2 we will have: > - The new method finder from Benjamin that mixes both, and remove the old ones. > - The new RecentSubmisons, and remove the old one. > > Thanks > > Mariano > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

Re: [Pharo-project] Class comment in OB
by StÃ©phane Ducasse Sept. 23, 2010

Sept. 23, 2010

but can you check in latest 1.2 to be sure. On Sep 22, 2010, at 10:34 PM, Schwab,Wilhelm K wrote: > Stef, > > I noticed it in 1.1, so it's probably old news. >

1 0

Re: [Pharo-project] ESUG actions (was: Best Spreading Smalltalk Actions)
by StÃ©phane Ducasse Sept. 23, 2010

Sept. 23, 2010

:) This is fun because one of the board member raised the question just before this remark. We are not sure that rebranding is good but so far I like your slogan. And we welcome any smalltalker. The goals of esug are simple (you can see that in the first talk of esug and also the one of serge about future actions) - create energy in the community (via the conf via new user groups) - support open-source development - support business in Smalltalk - push/help teacher teaching Smalltalk - bring open-source and business together (check my last talk at Barcelona - we need strong vendors and strong open-source) ESUG never took into account geographic perspective, we sent books all over the world in the past. And student volunteers came from everywhere :) Stef > > I think ESUG has been an outstanding success for Smalltalk globally and > therefore deserves to be called The Smalltalk Users Group. TSUG. Such a name > change will also give a better impression to Smalltalk and is not untrue. > > All the best, > Aik-Siong Koh > -- > View this message in context: http://forum.world.st/Best-Spreading-Smalltalk-Actions-tp2542307p2551292.ht… > 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

1 0

[Pharo-project] ESUG actions (was: Best Spreading Smalltalk Actions)
by Noury Bouraqadi Sept. 23, 2010

Sept. 23, 2010

Hi, ESUG is willing to support all actions everywhere. The "E" of ESUG can also be interpreted as "Earth-wide" :-) In places where there are Smalltalk groups we help them (sponsoring). Otherwise we push their creation. If you have a project that might help the Smalltalk community in someway (free software project, writing books, organizing an event, ...), you are eligible to ESUG support. Just submit your proposal to the ESUG board (board(a)esug.org) and you'll get quickly an answer. You can find a list of ESUG actions on-line: http://www.esug.org/Promotion Noury ESUG Treasurer www.esug.org On 21 sept. 2010, at 13:25, GermÃ¡n Arduino wrote: > Hi: > > I agree with Mariano, ESUG is sponsoring me even when I do not live in > Europe and I can not even go to conferences in Europe. > > Also they helped me to present my products in two editions of > Innovation Technology Awards, without being present. > > Thanks ESUG. > > > 2010/9/21 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> >> >> On Fri, Sep 17, 2010 at 7:16 PM, Casey Ransberger <casey.obrien.r(a)gmail.com> >> wrote: >>> >>> As far as sponsoring local user groups: does this apply only in Europe? Or >>> can people outside of Europe also ask for support? >> >> I think they can. We got sponsored twice for SqueakDBX and we were living >> in Argentina. German is now sponsored for RPC project and he also lives >> there. >> >> In addition, FAST (which can be kind of local user group in Argentina) >> received something too. >> >> But maybe I am wrong....I cc'ed esug mailing list. >> >> cheers >> >> mariano >> >>> >>> On Sep 17, 2010, at 12:45 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>> wrote: >>> >>>> Stay tuned :) the new board acted that it will launch a lot of new >>>> actions >>>> Sponsoring local user groups >>>> Conference sponsoring Smalltalk Solutions, Smalltalks >>>> Smalltalk in the cloud >>>> Smalltalk and robots >>>> Smalltalk web Archive >>>> Summertalk Project... >>>> But we will have two ESUG action ambassadors: Alain Plantec and Serge >>>> Stinckwich >>>> >>>> Stef >>>> >>>> >>>> On Sep 17, 2010, at 8:27 AM, Tudor Girba wrote: >>>> >>>>> Congratulations! Your efforts are really appreciated. >>>>> >>>>> Doru >>>>> >>>>> >>>>> On 16 Sep 2010, at 19:41, laurent laffont wrote: >>>>> >>>>>> Thank you !! >>>>>> >>>>>> Laurent >>>>>> >>>>>> On Thu, Sep 16, 2010 at 4:27 PM, Noury Bouraqadi <bouraqadi(a)gmail.com> >>>>>> wrote: >>>>>> Although the technology is important, spreading the word is also of >>>>>> great value to the Smalltalk community. >>>>>> This is why the ESUG board decided to distinguish two people for their >>>>>> actions on this-level: >>>>>> >>>>>> -Damien Cassou >>>>>> for Squeak-dev: an initiative which makes developers life easier by >>>>>> setting a ready to use image including best available tools. >>>>>> >>>>>> -Laurent Laffont >>>>>> for Pharocast: quality screencasts that illustrates various facets of >>>>>> http://pharocasts.blogspot.com/ >>>>>> >>>>>> Congratulations Damien and Laurent! >>>>>> >>>>>> Noury @ ESUG 2010 - Barcelona :-) >>>>>> --- >>>>>> 18th International Smalltalk Joint Conference, September 13 -17 2010 >>>>>> Barcelona, Spain. >>>>>> http://www.esug.org/Conferences/2010 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>> >>>>> -- >>>>> www.tudorgirba.com >>>>> >>>>> "Some battles are better lost than fought." >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>>> >>> >> >> >> >> >> > > > > -- > ================================================= > GermÃ¡n S. Arduino <gsa @ arsol.net> Twitter: garduino > Arduino Software & Web Hosting http://www.arduinosoftware.com > PasswordsPro http://www.passwordspro.com > =================================================

4 3

[Pharo-project] Issue 2744: Renaming the path to the image is not caught in Pharo on OS X
by Mircea Lungu Sept. 23, 2010

Sept. 23, 2010

Hi guys, If I rename any of the directories in the path of a running image I will break the image: I can't save it, I can't close it. I get a debugger at any step. It seems the image is not informed of the path change and it still tries to log the changes in the the changes file which has already moved. I verified this on OS X,. I opened an issue for this: http://code.google.com/p/pharo/issues/detail?id=2744 Mircea.

4 6

[Pharo-project] DoubleArray
by Schwab,Wilhelm K Sept. 22, 2010

Sept. 22, 2010

Squeak, deliberately, does not have a double array class. Is that because there is some horrible reason it can't work, or because it won't work on certain platforms? Put another way, should we add such a class, if only via an external heap or whatever would be needed to make it reliable? Bill

3 4

[Pharo-project] I am missing userful functionality?
by Igor Stasenko Sept. 22, 2010

Sept. 22, 2010

Hello, guys i want to do a simple thing, which can be expressed by following: oldClass replaceWith: newClass migrateInstances: [:inst | ... ] In my case, first, i installing a WeakFinalizationRegistry class, and then want to replace an old WeakRegistry class with it, silently and painlessly. I end up with following script: | old new oldClass newClass | old := OrderedCollection new. new := OrderedCollection new. "migrate instances" WeakRegistry allInstancesDo: [:registry | | newr | old add: registry. newr := WeakFinalizationRegistry basicNew initialize. registry migrateTo: newr. new add: newr ]. old asArray elementsForwardIdentityTo: new asArray. "replace the class" oldClass := WeakRegistry. newClass := WeakFinalizationRegistry. Smalltalk forgetClass: #WeakFinalizationRegistry logged: false. newClass superclass removeSubclass: newClass. newClass setName: #WeakRegistry. oldClass becomeForward: newClass. -- it looks a bit hackish, and i wonder how to do that in more 'standard' way. Initially replacing classes was: oldClass removeFromSystem. newClass rename: #WeakRegistry the problem with that, is that all compiled methods , which was referring to old class through association, still using it, and to get rid of them i have to recompile them. -- Best regards, Igor Stasenko AKA sig.

1 1

[Pharo-project] DemoMode should not change Fonts only sizes?
by Mariano Martinez Peck Sept. 22, 2010

Sept. 22, 2010

Hi Alain, I was trying the DemoMode before my talk at ESUG and I thought that it would be better if this guy only changes the size of the fonts. I am not sure if changing the fonts is good. For example, right now it is using FreeType with DejaVu. Since Pharo1.1 dev doesn't use them, there is no folder "Fonts" with themâ¦..thus they are not found and ugly fonts are rendered. Cheers mariano

5 8