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

Re: [Pharo-dev] Weird issue with removing instance vars from class def: instance vars jumbled

by Marcus Denker

On Oct 1, 2013, at 9:34 AM, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > Still, why does it occur ? Normal ? I experienced that on a class with quite a number of instVars. This seems to be a bug. When you remove / add inst vars, the offset of all those behind need to change (and all in the subclass). This is done by the ClassBuilder by recompiling (there is code somewhere to do it more intelligently, by using bytecode level IR to patch the offsets, but this is not yet active). We need some reproducible case to fix the problemâ¦ because normally the class builder does the right thing, I wonder in which case there is a problem. Marcus

Oct. 1, 2013

Re: [Pharo-dev] Weird issue with removing instance vars from class def: instance vars jumbled

by phil＠highoctane.be

Still, why does it occur ? Normal ? I experienced that on a class with quite a number of instVars.

Oct. 1, 2013

Re: [Pharo-dev] SlotVirus

by Marcus Denker

On Oct 1, 2013, at 9:23 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Oct 1, 2013, at 9:07 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> And we should not forget to do these cleanups: we now have nearly everything double in the system: >> -> Compiler >> -> Inspector >> -> Debugger >> -> ClassBuilder >> -> ClassOrganizer >> -> Browserâ¦. > > -> Rpackage vs PackaInfo vs. SystemCategory > -> Ring vs. PseudeClass&co vs. RBClass > -> AST vs RB AST -> Url vs. ZnUrl -> ZnMimeType vs MimeType -> NewList vs whichever-of-the 30 classes with "List" in its name -> FreeType vs. Bitmap fonts -> TreeInspector vs. ObjectExplorer We should really clean up. Marcus

Oct. 1, 2013

Re: [Pharo-dev] SlotVirus

by Marcus Denker

On Oct 1, 2013, at 9:07 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > And we should not forget to do these cleanups: we now have nearly everything double in the system: > -> Compiler > -> Inspector > -> Debugger > -> ClassBuilder > -> ClassOrganizer > -> Browserâ¦. -> Rpackage vs PackaInfo vs. SystemCategory -> Ring vs. PseudeClass&co vs. RBClass -> AST vs RB AST -> I am sure I am forgetting many othersâ¦ Marcus

Oct. 1, 2013

Re: [Pharo-dev] unexpected lack of Method Version History (due to CI process?)

by Goubier Thierry

Le 30/09/2013 17:51, Marcus Denker a Ã©crit : > > On Sep 30, 2013, at 5:40 PM, btc(a)openinworld.com wrote: > >> In the process of reviewing a fix to an issue [1] that I reported with PharoLauncher, I downloaded the latest CI result and browsed to the method I knew had changed [2]. I wanted to directly observe the change in the version history, but was surprised that there was no version history for the method. My uninformed intuition is this relates to some 'clean up for release' run as part of the build process to strip out old versions to compact the image delivered by the CI process, but does it make sense to do this for every build? >> I can understand not wanting this to grow indefinitely to bloat the image - but perhaps this compaction would be better only for major releases? I guess the downside is that you are then not exercising the 'full release' process every build. However having in image Version History extending a fair way back in time has always seemed to me to be one of the very cool (i.e. useful features of Pharo/Smalltalk). Without this, it feels like 'something' has been lost. The ultimate solution would seem to be linking the method version history to a network resource for the full history only as required per method. Any chance anyone is working on something like that? >> > > Keep in mind that the .changes history and monticello are completely separate. When you load a mc version, you just load *that version*. > > We really need to have the "versions" of the method go and ask the repo. Now the problem is that Monticello is not really nice: it has complete snapshots per commit in a zip file. > Getting version out there of a method is not possibleâ¦ without building infrastructure for it. gitfiletree repositories have that capability, i.e. querying the repo to get all versions of a method (but I didn't write the code which merges both the changes history and the package repo history in the same version browser). Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Oct. 1, 2013

Re: [Pharo-dev] SlotVirus

by Marcus Denker

On Oct 1, 2013, at 9:02 AM, btc(a)openinworld.com wrote: > > I've just bumped into an interesting class named 'SlotVirus'. Thats a cute name, but its not really business friendly. In business some people in power get to be unreasonable about these things. They are the gatekeepers > and unfortunately we don't get to choose that they should be more reasonable. Perhaps something like 'SlotPropagator' or 'SlotPropagation' could be considered. > This is a helper class that introduced meta-objects for instance variables in all classes (that's why "Slot allInstances size" returns you the number of ivars in the systemâ¦). When we remove the old class builder this class is removed, too. And we should not forget to do these cleanups: we now have nearly everything double in the system: -> Compiler -> Inspector -> Debugger -> ClassBuilder -> ClassOrganizer -> Browserâ¦. Marcus

Oct. 1, 2013

Re: [Pharo-dev] Weird issue with removing instance vars from class def: instance vars jumbled

by Marcus Denker

On Oct 1, 2013, at 9:02 AM, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > Can I do that on a given class? Compiler recompileAll would take ages I guess... Yes: Object compileAll (we should make the API consistentâ¦ on CompiledMethod is is #recompile, Compiler has recompileAll, on the whole system (Smalltalk image) it is missingâ¦.) Marcus

Oct. 1, 2013

SlotVirus

by btc＠openinworld.com

I've just bumped into an interesting class named 'SlotVirus'. Thats a cute name, but its not really business friendly. In business some people in power get to be unreasonable about these things. They are the gatekeepers and unfortunately we don't get to choose that they should be more reasonable. Perhaps something like 'SlotPropagator' or 'SlotPropagation' could be considered. cheers -ben

Oct. 1, 2013

Re: [Pharo-dev] Weird issue with removing instance vars from class def: instance vars jumbled

by phil＠highoctane.be

Can I do that on a given class? Compiler recompileAll would take ages I guess...

Oct. 1, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=ma… 1 regressions found. Tests.Release.ReleaseTest.testInstanceSideMethodsWithNilKeyInLastLiteral

Oct. 1, 2013