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

Re: [Pharo-project] Collect all references to AnObsoleteFoo

by Fernando Olivero

Ciao Roberto, Whenever you remove a class that is still referenced in the system, an ObsoleteClass takes the place of the removed class. In the late-bound spirit of Smalltalk, the system allows removing the classes and dealing with the current references later. If i may question the source of your problem: "a Dictionary (containing receivers of method calls, i.e., classes) that I need to serialize in a file (i.e., using Fuel)", are you sure you need to serialize the actual classes? or just the names? or even a description of the class within Ring? Think about what you are modeling with a Dictionary that holds <messages,set of receivers>, and maybe try to reify that concept. Fernando On Mon, Apr 1, 2013 at 9:58 PM, Max Leske <maxleske(a)gmail.com> wrote: > I've had the same problem just recently but am stuck in a bit of work right now. I hope to elaborate at length tomorrow. > > Quick fix: if you *need* to serialize those classes, simply change the code so that fuel serializes them. To fix obsolete classes you need to remove all references to it, be it in a dictionary or in a compiled method where you used the class name. > Can you post the list of classes that are obsolete? > > Cheers, > Max > > > > On 01.04.2013, at 16:51, roberto.minelli(a)usi.ch wrote: > >> Hi, >> >> I'm getting crazy about obsolete behaviors and any help here is really appreciated. >> >> In a nutshell, I have a Dictionary (containing receivers of method calls, i.e., classes) that I need to serialize in a file (i.e., using Fuel). >> >> Fuel returns an error in FLGlobalClassCluster>>#serializeGlobalClass:on: complaining that I'm trying to serialize an obsolete class. >> >> Now my question is, apart from executing this small piece of code... >> >> SmalltalkImage current fixObsoleteReferences. >> SystemNavigation new obsoleteBehaviors size > 0 >> ifTrue: [ SystemNavigation new obsoleteBehaviors inspect.] >> >> â¦in which I discovered to have many obsolete references, how can I "browse" and eventually kill such references? >> >> For me the entire "behavior" of obsolete classes is obscure and I don't know how those classes are originated. >> More important, I also don't know how to eliminate them. >> >> Thanks in advance, >> Roberto >> >> > >

April 1, 2013

Re: [Pharo-project] [3.0] CI build is broken

by Tudor Girba

No stress. In the worst case you can fix it tomorrow during the tutorial :). Doru On Apr 1, 2013, at 10:26 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-04-01, at 22:09, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > >> Tudor Girba-2 wrote >>> Could it have something to do with the latest optimizations of Camillo? >> >> Probably... Cami breaks everything :-P > > dammit, I wanted to silently add the new zeroconf scripts > obviously something went horribly wrong there, sorry guys.. working on it! > -- www.tudorgirba.com "What is more important: To be happy, or to make happy?"

April 1, 2013

[Pharo-project] [ANN] Dr. Geo 13.04 for workstations and Android

by Hilaire Fernandes

We are proud to announce you release 13.04. http://drgeo.eu/news/drgeo1304 Hilaire -- Dr. Geo http://drgeo.eu

April 1, 2013

Re: [Pharo-project] [3.0] CI build is broken

by Camillo Bruni

On 2013-04-01, at 22:09, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > Tudor Girba-2 wrote >> Could it have something to do with the latest optimizations of Camillo? > > Probably... Cami breaks everything :-P dammit, I wanted to silently add the new zeroconf scripts obviously something went horribly wrong there, sorry guys.. working on it!

April 1, 2013

Re: [Pharo-project] [3.0] CI build is broken

by Sean P. DeNigris

Tudor Girba-2 wrote > Could it have something to do with the latest optimizations of Camillo? Probably... Cami breaks everything :-P ----- Cheers, Sean -- View this message in context: http://forum.world.st/3-0-CI-build-is-broken-tp4679211p4679220.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 1, 2013

Re: [Pharo-project] Pharo Vision is becoming reality

by Sean P. DeNigris

On Apr 1, 2013, at 3:35 PM, "Igor Stasenko [via Smalltalk]" <ml-node+s1294792n4679212h60(a)n4.nabble.com> wrote: > And as for ephemerons, > the implementation exists, and actually it's in our VMs. So right now, are blocks held weakly by announcers? That was my major use case. Also, do we still have to send #weak or is weak now the default? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-Vision-is-becoming-reality-tp4679202p4679219.ht… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 1, 2013

Re: [Pharo-project] [3.0] CI build is broken

by Tudor Girba

So is the Moose build (Pharo 2.0). Could it have something to do with the latest optimizations of Camillo? Doru On Apr 1, 2013, at 9:25 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-1-Tracker/82/console > > 2013-04-01 20:54:16 (6.41 MB/s) - `updates30.staged' saved [28/28] > > + bash > + wget --quiet -O - http://files.pharo.org/script/ciPharo30PharoVM.sh > Downloading the latest 30 Image: > http://files.pharo.org/image/30/latest.zip > image.3YiB0/Pharo-30019.image > bash: line 70: syntax error near unexpected token `newline' > Build step 'Execute shell' marked build as failure > Archiving artifacts > Finished: FAILURE > > > -- www.tudorgirba.com "No matter how many recipes we know, we still value a chef."

April 1, 2013

Re: [Pharo-project] Collect all references to AnObsoleteFoo

by Max Leske

I've had the same problem just recently but am stuck in a bit of work right now. I hope to elaborate at length tomorrow. Quick fix: if you *need* to serialize those classes, simply change the code so that fuel serializes them. To fix obsolete classes you need to remove all references to it, be it in a dictionary or in a compiled method where you used the class name. Can you post the list of classes that are obsolete? Cheers, Max On 01.04.2013, at 16:51, roberto.minelli(a)usi.ch wrote: > Hi, > > I'm getting crazy about obsolete behaviors and any help here is really appreciated. > > In a nutshell, I have a Dictionary (containing receivers of method calls, i.e., classes) that I need to serialize in a file (i.e., using Fuel). > > Fuel returns an error in FLGlobalClassCluster>>#serializeGlobalClass:on: complaining that I'm trying to serialize an obsolete class. > > Now my question is, apart from executing this small piece of code... > > SmalltalkImage current fixObsoleteReferences. > SystemNavigation new obsoleteBehaviors size > 0 > ifTrue: [ SystemNavigation new obsoleteBehaviors inspect.] > > â¦in which I discovered to have many obsolete references, how can I "browse" and eventually kill such references? > > For me the entire "behavior" of obsolete classes is obscure and I don't know how those classes are originated. > More important, I also don't know how to eliminate them. > > Thanks in advance, > Roberto > >

April 1, 2013

Re: [Pharo-project] Pharo Vision is becoming reality

by Igor Stasenko

And as for ephemerons, the implementation exists, and actually it's in our VMs. But after discussing with Eliot, it needs some work to use separate object format for it. On 1 April 2013 17:57, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-04-01, at 17:54, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > >> Out of the 14 action items laid out in the 5 year vision, /over half now >> exist one year later/ in the 2.0 release! >> >> Here's the current progress (corrections/updates welcome): >> >> In 2.0: >> 2a Rewrite of Filesystem >> 7 Packages as real objects (RPackage) >> 8 Package Meta-Data (manifest classes) >> 9 Less Model Clutter and Duplication (Ring) >> 10 Building and Reusing UI Logic (Spec) >> 11 New Network Layer (Zinc/Zodiac) >> 12 Serializers (Fuel) >> 13 System Change Notifier replacement (SystemAnnouncer) >> >> For 3.0 [1]: >> 6 Fully parametrized compiler tool chain (this means Opal, right?) >> 1 A Robust and Extensible System Events (guessing this is event model from >> [1]) >> 2b Rewrite of Streams >> 4 UI Canvas for Zoomable Interfaces (I'm assuming this is part of Athens?) >> >> In progress (deadline unclear) >> 3 Announcements and Ephemerons >> 5 Bootstrap of the Core > > that is done as well I would say :) => Hazelnut > >> 14 Cleaning Morphic >> >> [1] http://forum.world.st/Pharo-3-td4677109.html >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: http://forum.world.st/Pharo-Vision-is-becoming-reality-tp4679202.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > > -- Best regards, Igor Stasenko.

April 1, 2013

[Pharo-project] [3.0] CI build is broken

by Marcus Denker

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-1-Tracker/82/console 2013-04-01 20:54:16 (6.41 MB/s) - `updates30.staged' saved [28/28] + bash + wget --quiet -O - http://files.pharo.org/script/ciPharo30PharoVM.sh Downloading the latest 30 Image: http://files.pharo.org/image/30/latest.zip image.3YiB0/Pharo-30019.image bash: line 70: syntax error near unexpected token `newline' Build step 'Execute shell' marked build as failure Archiving artifacts Finished: FAILURE

April 1, 2013