March 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] strange array instance

by Eliot Miranda

> On Mar 8, 2016, at 2:13 AM, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > > >> Le 8 mars 2016 Ã 10:57, Guille Polito <guillermopolito(a)gmail.com> a Ã©crit : >> >> It smells like the first page of the class table, yes, but it shouldn't be visible from the image side (as far as I understood) > > Yes, it is the first page of the Spur class table. > It means than #allInstances is able to reach this instance but not #garbageCollect. Eliot is it the desired behavior or does #allInstances need to be updated to hide the class table pages? Ugh, that's a bug. The class table pages should not be visible. Objects in Sour contain class indices, not class pointers. One can arrange that a class is in the class table at more than one index. allInstances searches for objects with a particular class index. So the class table pages should use a "false index" (I call these "class puns"), and hence not show up in allInstances (or allObjects). I'll investigate.

March 8, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50632 Home: https://github.com/pharo-project/pharo-core

March 8, 2016

[pharo-project/pharo-core] ec187b: 50632

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: ec187b5b9722b87bb9cf893a00ce2d9c95b5b9ea https://github.com/pharo-project/pharo-core/commit/ec187b5b9722b87bb9cf893a… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-03-08 (Tue, 08 Mar 2016) Changed paths: R Collections-Sequenceable.package/Array.class/instance/private/refersToLiteral_.st R Kernel.package/AdditionalMethodState.class/instance/testing/refersToLiteral_.st R Kernel.package/Behavior.class/instance/testing/isEphemeronClass.st R Kernel.package/Behavior.class/instance/testing/isImmediateClass.st M Kernel.package/CompiledMethod.class/instance/literals/refersToLiteral_.st R Kernel.package/Object.class/instance/pointing to/refersToLiteral_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50631.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50632.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50631.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50632.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50632 16368 refersToLiteral: should (for now) just call hasLiteralThorough: https://pharo.fogbugz.com/f/cases/16368 17768 remove again isEphemeronClass and isImmediateClass https://pharo.fogbugz.com/f/cases/17768 http://files.pharo.org/image/50/50632.zip

March 8, 2016

Re: [Pharo-dev] [Pharo-users] [Moose-dev] Re: Call for action for Roassal

by Johan Fabry

Excellent, thanks a lot! I will take a look at that tomorrow. > On Mar 7, 2016, at 11:34, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Hi Johan, > > I've just commited RTAnchorConstraint to latest Roassal, see class-side example there. > > I've been using it for my class diagrams where it works quite well, however class diagrams are usually orthogonal-ish, which makes it a bit nicer. > <uml.png> > > The Anchor will avoid intersecting it's own line, and one of the end shapes (it should both but apparently I have a bug there...). > It doesn't look at other lines, however you can specify on which side it should be. > > (You can also put the node label inside the circle with `el @ (RTLabelled new center)` but you probably know that.) > <anchor.png> > â > I have also a global edge labeling layout which produces good placementâ¦ but it's slow as hellâ¦ I need to write a fast flow alogrithmâ¦ > > Also the Anchor currently doesn't work with self-edges. On the other hand Roassal doesn't have self-edges yet so it shouldn't be a problem. :) > > Peter > > > On Mon, Mar 7, 2016 at 2:34 PM, Johan Fabry <jfabry(a)dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>> wrote: > > Better late than never :-) (working on the holidays backlog) > > I only have one request: better positioning on labels of nodes and edges. For example see the image: three of the four labels are badly positioned because the bounding box of their text is intersected by one or more edges. > > <Screen Shot 2016-03-07 at 10.31.24.png> > I know that to solve this generally is hard, but for simple cases like this it should be possible. > > Ah, and it should work well with animations and dragging of course ;-) > >> On Feb 24, 2016, at 05:51, Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >> >> Dear community, >> >> As you may have seen, Roassal has entered a stabilization phase. The book AgileVisualization.com <http://agilevisualization.com/> will soon be released. After its release, Roassal will go over a new development phase. In order to prepare it, I am asking this question: >> >> What are the 3 aspects you would like to see improved in Roassal? >> >> You can answer publicly or by sending private messages. >> >> Kind regards, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch <mailto:Moose-dev@list.inf.unibe.ch> >> https://www.list.inf.unibe.ch/listinfo/moose-dev <https://www.list.inf.unibe.ch/listinfo/moose-dev> >> > > > > ---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <--- > > Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/~jfabry> > PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch <mailto:Moose-dev@list.inf.unibe.ch> > https://www.list.inf.unibe.ch/listinfo/moose-dev <https://www.list.inf.unibe.ch/listinfo/moose-dev> > > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

March 8, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50631 Home: https://github.com/pharo-project/pharo-core

March 8, 2016

[pharo-project/pharo-core] e8b5c6: 50631

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: e8b5c6249e646b6a982b6eda9d21a2d744b49c07 https://github.com/pharo-project/pharo-core/commit/e8b5c6249e646b6a982b6eda… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-03-08 (Tue, 08 Mar 2016) Changed paths: R Graphics-Fonts-Tests.package/StandardSystemFontsTest.class/README.md R Graphics-Fonts-Tests.package/StandardSystemFontsTest.class/definition.st R Graphics-Fonts-Tests.package/StandardSystemFontsTest.class/instance/utilities/assert_familyName_pointSize_.st R Graphics-Fonts-Tests.package/StandardSystemFontsTest.class/instance/utilities/saveStandardSystemFontsDuring_.st M Graphics-Tests.package/PointTest.class/instance/tests-converting/testAsFloatPoint.st M Graphics-Tests.package/PointTest.class/instance/tests-converting/testAsIntegerPoint.st A Graphics-Tests.package/PointTest.class/instance/tests-truncation and roundoff/testIsFloatPoint.st A Kernel.package/Behavior.class/instance/testing/isEphemeronClass.st A Kernel.package/Behavior.class/instance/testing/isImmediateClass.st M Kernel.package/Point.class/instance/converting/asFloatPoint.st M Kernel.package/Point.class/instance/converting/asIntegerPoint.st A Kernel.package/Point.class/instance/testing/isFloatPoint.st M Kernel.package/Point.class/instance/testing/isIntegerPoint.st M Kernel.package/Rectangle.class/instance/rectangle functions/areasOutside_.st M Kernel.package/Rectangle.class/instance/transforming/centeredBeneath_.st M Kernel.package/Rectangle.class/instance/truncation and roundoff/ceiling.st M Kernel.package/Rectangle.class/instance/truncation and roundoff/floor.st M Kernel.package/Rectangle.class/instance/truncation and roundoff/isIntegerRectangle.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50630.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50631.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50630.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50631.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-SessionManager.package/StartupUIManager.class/instance/error handling/handleError_log_.st Log Message: ----------- 50631 17766 StandardSystemFontsTest is either unfinised or obsolete https://pharo.fogbugz.com/f/cases/17766 17736 Growl raise debugger instead of a popup at startup https://pharo.fogbugz.com/f/cases/17736 17758 Rectangle>>#areasOutside: inconsistent return value https://pharo.fogbugz.com/f/cases/17758 17752 Point>>#asFloatPoint and Point>>#asIntegerPoint should not create new instances all the time. Add Point>>#isFloatPoint https://pharo.fogbugz.com/f/cases/17752 http://files.pharo.org/image/50/50631.zip

March 8, 2016

Re: [Pharo-dev] strange array instance

by Guille Polito

But of course it should not be collected :) it is the class table. And the VM uses it as root for the GC AFAIK (check setHiddenRoot:). -------- Original Message -------- >> Le 8 mars 2016 Ã 10:57, Guille Polito <guillermopolito(a)gmail.com> a Ã©crit : >> >> It smells like the first page of the class table, yes, but it shouldn't be visible from the image side (as far as I understood) > Yes, it is the first page of the Spur class table. > It means than #allInstances is able to reach this instance but not #garbageCollect. Eliot is it the desired behavior or does #allInstances need to be updated to hide the class table pages? > >

March 8, 2016

Re: [Pharo-dev] strange array instance

by Christophe Demarey

> Le 8 mars 2016 Ã 10:57, Guille Polito <guillermopolito(a)gmail.com> a Ã©crit : > > It smells like the first page of the class table, yes, but it shouldn't be visible from the image side (as far as I understood) Yes, it is the first page of the Spur class table. It means than #allInstances is able to reach this instance but not #garbageCollect. Eliot is it the desired behavior or does #allInstances need to be updated to hide the class table pages?

March 8, 2016

Re: [Pharo-dev] strange array instance

by Guille Polito

It smells like the first page of the class table, yes, but it shouldn't be visible from the image side (as far as I understood)

March 8, 2016

Re: [Pharo-dev] strange array instance

by Pavel Krivanek

Is it a Spur VM class table? 2016-03-08 10:40 GMT+01:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: > Hi, > > there is a strange array of size 1024 in the Pharo image that is not eaten > by garbage collector even if no object points to it. I guess it is related > to Spur. > > ((Array allInstances select: [ :i | i size = 1024 ]) > select: [ :a | a second = SmallInteger ]) pointersTo > > What is it and is it accessible somehow? > > Cheers, > -- Pavel > >

March 8, 2016