- Pharo-users - lists.pharo.org

Re: [Pharo-users] Is RBClassNotReferencedRule ~200x slower in Pharo 4 vs Pharo 3 ?

by stepharo

Hi marcus do you get an idea why we got this slowdown? Stef Le 30/7/15 14:08, Marcus Denker a Ã©crit : > I added an issue: > > https://pharo.fogbugz.com/f/cases/16074/Is-RBClassNotReferencedRule-200x-sl… > > i think we need to put in some cashingâ¦ here if we would could all > *used* classes once for an enviromentâ¦. > >> On 29 Jul 2015, at 17:33, Paul DeBruicker <pdebruic(a)gmail.com >> <mailto:pdebruic@gmail.com>> wrote: >> >> Paul DeBruicker wrote >>> Hi Stef, >>> >>> The slowdown is dependent upon the # of classes in the package. If you >>> use Fuel then you should see a slowdown of 20x. I just have a lot of >>> classes in this package. The source of the slowdown is in the >>> changes to >>> RBSmallLintChecker>>#checkClass: and >>> RBClassNotReferencedRule>>#checkClass: . The old versions use the >>> linter >>> to check if the literal is used anywhere and the new one uses >>> #allCallsOn. >>> >>> >>> Hope this helps >>> >>> Paul >> >> >> and by "use Fuel" I mean: >> >> rule:=RBClassNotReferencedRule new. >> environment:=RBBrowserEnvironment new forPackageNames: #('Fuel'). >> >> >> AndreasSystemProfiler spyOn:[RBSmalllintChecker runRule: rule >> onEnvironment: >> environment] >> >> >> >> >> >> >> >> -- >> View this message in context: >> http://forum.world.st/Is-RBClassNotReferencedRule-200x-slower-in-Pharo-4-vs… >> Sent from the Pharo Smalltalk Users mailing list archive at >> Nabble.com <http://Nabble.com>. >> >

Aug. 18, 2015

Re: [Pharo-users] [ANN] Magma 1.5

by Pablo R. Digonzelli

I can colaborate. I do not know if i have the time and technical skills to do it alone, but for shure i can colaborate. I think magma will be a very interesting option for object persistence in pharo. I am currently working with garage and glorp and i suffers the innecesary complexity and other bad things thet persistence layer introduce in developing pharo apps. Pharo Ing. Pablo Digonzelli Software Solutions IP-Solutiones SRL Metrotec SRL 25 de Mayo 521 San Miguel de TucumÃ¡n Email: pdigonzelli(a)softsargentina.com pdigonzelli(a)gmail.com Cel: 5493815982714 ----- Mensaje original ----- De: "Torsten Bergmann" <astares(a)gmx.de> Para: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> CC: stephan(a)stack.nl, stepharo(a)free.fr, hilaire(a)drgeo.eu, "Pablo Digonzelli" <pdigonzelli(a)gmail.com> Enviados: Martes, 18 de Agosto 2015 10:26:44 Asunto: Fwd: [ANN] Magma 1.5 Stephan Eggermont wrote: >It is possible, and it needs someone who can deal with low-level >details. Magma has its own mailing list. Chris has repeatedly said he'd >be willing to help out, but is not willing to be the Pharo port maintainer. I asked Chris directly and you can find his answer here on the magma list: http://lists.squeakfoundation.org/pipermail/magma/2015-August/001955.html As ever it requires someone to move this forward to make it happen. But as there was an initiative with Magma 1.3 for Pharo 1.3 already it does not seem impossible. Also - as Stef already pointed out - community services like CI could be used to maintain it once an initial up to date port was done. Bye T.

Aug. 18, 2015

Re: [Pharo-users] ClassCategoryReader and ClassCommentReader

by stepharo

indeed I'm puzzled. It hshould be dead code. I checked and I came to the same conclusion thant you. S. Le 17/8/15 15:31, Guillermo Polito a Ã©crit : > These two classes seem to be unused. They implement the #scanFor: > method but the only senders of #scanFor: send it explicitly to > RunArray, like: > > RunArray scanFor: ... > > Does anybody use it? Because it looks like an old class that could be > removed. > > Guille

Aug. 18, 2015

Fwd: [ANN] Magma 1.5

by Torsten Bergmann

Stephan Eggermont wrote: >It is possible, and it needs someone who can deal with low-level >details. Magma has its own mailing list. Chris has repeatedly said he'd >be willing to help out, but is not willing to be the Pharo port maintainer. I asked Chris directly and you can find his answer here on the magma list: http://lists.squeakfoundation.org/pipermail/magma/2015-August/001955.html As ever it requires someone to move this forward to make it happen. But as there was an initiative with Magma 1.3 for Pharo 1.3 already it does not seem impossible. Also - as Stef already pointed out - community services like CI could be used to maintain it once an initial up to date port was done. Bye T.

Aug. 18, 2015