November 2018 - Pharo-users

[Ann] TaskIt v1.0

by Santiago Bragagnolo

Hi everybody :). I am happy to announce TaskIt v1.0. In this version we add some new features, passed over the red tests and clean up some dead code. And did a pass in the documentation A bit from the DOC Downloading Current stable version of taskit can be downloaded using metacello as follows: Metacello new baseline: 'TaskIt'; repository: 'github://sbragagnolo/taskit'; load. If you want a specific release such as v1.0, you can load the associated tag as follows Metacello new baseline: 'TaskIt'; repository: 'github://sbragagnolo/taskit:v1.0'; load. Otherwise, if you want the latest development version, take a look at the development branchs and load the latest: Metacello new baseline: 'TaskIt'; repository: 'github://sbragagnolo/taskit:dev-1.1'; load. <https://github.com/sbragagnolo/taskit/blob/master/README.md#major-features>Major Features - Actors (ActIt) - Configuration Profiles - Service Check specially the configuration profiles. The default profile usage is #development, which sets up the environment for debugging exceptions in a process. I want to thank a lot to the contributors, Guillermo Polito Max Leske and Daniel Sasu. I want as well to thanks the users, specially to those that bring me feedback (blames and ideas) in person (Esteban, Pablo) or through the different channels (Holger Freyther, Juraj Kubelka, Philippe Back). I want also to apologise the delay of my responses on the issue board :) (Really, sorry). I am constantly using TaskIt in other projects, but much times I cannot do it my priority. thanks a lot, Santiago Bragagnolo.

Nov. 29, 2018

Re: [Pharo-users] Reify RBLiteralNode and RBBlockNode args/return with MetaLink?

by Thierry Goubier

Le jeu. 29 nov. 2018 Ã 11:15, Marcus Denker <marcus.denker(a)inria.fr> a Ã©crit : > > > > > On 29 Nov 2018, at 10:45, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > > Hi Manuel, > > > > would that extend to testing what happens if you add many, many > > metalinks in a method? > > > > yes, it would be nice to test that. > > > > I tried to rewrite the automated code tracer I had to use metalinks, > > and I gave up once I discovered that going over a certain number of > > metalinks in a method would stop working. > > > > > If you add a lot of code, you need to use the new byte code set as the old one is extremely limited for everything (number of temps, jump offsetâ¦) Well, it failed before that limit; once the context was complex enough, it would fail in various ways, such as being unable to bind to the proper temporary, writing incorrect byte sequences, and so on As anyway, it was injecting the same code that my tracer was already doing, but in a less debuggable way, so I sort of gave up and kept MetaLink use to simpler things, such as a type checker that inject type checks on arguments based on the type inferred from arguments names. Now, when I see how you're improving metalinks in this thread, I'd be interested in a higher view (source-level) of the transformations you're doing for implementing metalinks: I think they then could be reused in different contexts (i.e. refactorings, for example), or generalised outside Smalltalk itself. It may probably already been expressed that way, but I haven't looked into the metalink code itself. Thierry > > Marcus

Nov. 29, 2018

Uncle Bob's package design metrics

by Rafael Luque

Hi, Recently I've reread the chapter about "Package Design Principles" from the Robert C. Martin's "Agile Software Development" book and immediately find myself playing within the reflective and moldable Pharo's environment. I've built an small library DMMetrics that you can find at GitHub: https://github.com/osoco/dm-metrics This is a still very rough and work-in-progress, but I hope to be able to use it in my own projects to get some insights about my package design. Besides my unknowns about Roassal or Renraku, I've also found more conceptual difficulties trying to adapt some metrics as were originally defined by Robert Martin to Pharo's idiosyncrasies. For instance, for measuring the abstraction level of a package, the "Abstractness" metric is defined as Na/Nc; where Na is the number of classes in the package and Nc represents the number of abstract classes in the package. In a language like Java Nc refers to the number of interfaces and classes with at least one abstract method. In Pharo I'm counting the number of classes with methods sending "self subclassResponsibility", but I suspect that this way of measuring is resulting in abstractness values lower than it should be. Maybe I should take into account other Smalltalkish idioms that also contribute to the class abstraction level. Any idea in this way would be of great help. Thank you!

Nov. 29, 2018

Re: [Pharo-users] VPS difficulties

by Pierce Ng

On Wed, Nov 21, 2018 at 07:06:08PM -0500, Richard Kenneth Eng wrote: > I'm creating the competition website using Pharo and Teapot. For > encryption, I'm using Pierce Ng's PasswordCrypt, which requires a 32-bit C > library. This means I must run 32-bit Pharo. PasswordCrypt can be built as a 64-bit library. (Was away on vacation. Just saw this.) Pierce

Nov. 29, 2018

Re: [Pharo-users] Reify RBLiteralNode and RBBlockNode args/return with MetaLink?

by Marcus Denker

> On 29 Nov 2018, at 10:45, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Hi Manuel, > > would that extend to testing what happens if you add many, many > metalinks in a method? > yes, it would be nice to test that. > I tried to rewrite the automated code tracer I had to use metalinks, > and I gave up once I discovered that going over a certain number of > metalinks in a method would stop working. > If you add a lot of code, you need to use the new byte code set as the old one is extremely limited for everything (number of temps, jump offsetâ¦) Marcus

Nov. 29, 2018

Re: [Pharo-users] Reify RBLiteralNode and RBBlockNode args/return with MetaLink?

by Thierry Goubier

Hi Manuel, would that extend to testing what happens if you add many, many metalinks in a method? I tried to rewrite the automated code tracer I had to use metalinks, and I gave up once I discovered that going over a certain number of metalinks in a method would stop working. Thierry Le jeu. 29 nov. 2018 Ã 09:03, Marcus Denker <marcus.denker(a)inria.fr> a Ã©crit : > > > > > On 28 Nov 2018, at 21:37, Manuel Leuenberger <leuenberger(a)inf.unibe.ch> wrote: > > > > Awesome, thanks for the effort Marcus! > > > > I was wondering if it would be useful to use matrix-testing for MetaLinks. I imagine having example methods which employ all features of the Smalltalk syntax (syntax on a postcard?), for which all intermediate results of expressions are known, then apply MetaLinks in all possible combinations (arguments x control) and check the reifications and side-effects against the oracle. Then the tests would generate a matrix of which combinations work and which don't. This should cover most of the possible executions. > > > > Yes, that would be nice. > > Marcus > >

Nov. 29, 2018

Re: [Pharo-users] Reify RBLiteralNode and RBBlockNode args/return with MetaLink?

by Marcus Denker

> On 28 Nov 2018, at 21:37, Manuel Leuenberger <leuenberger(a)inf.unibe.ch> wrote: > > Awesome, thanks for the effort Marcus! > > I was wondering if it would be useful to use matrix-testing for MetaLinks. I imagine having example methods which employ all features of the Smalltalk syntax (syntax on a postcard?), for which all intermediate results of expressions are known, then apply MetaLinks in all possible combinations (arguments x control) and check the reifications and side-effects against the oracle. Then the tests would generate a matrix of which combinations work and which don't. This should cover most of the possible executions. > Yes, that would be nice. Marcus

Nov. 29, 2018

Re: [Pharo-users] [ANN] Teapot was moved to GitHub

by Attila Magyar

Esteban A. Maringolo wrote > Excellent material. > I also liked that you not only provided instructions for installation, > but also to set Teapot as a dependency. > > Please add the `pharo` tag to the repository, so it gets listed in the > topics section [1] and also helps bumping Pharo topic to the home of > the Topics page. > > [1] https://github.com/topics/pharo?o=desc&s=updated > > Esteban A. Maringolo Yeah, many of these were added by a contributor @fortizpenaloza, so big thanks to him. Sure, I added the tags. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 28, 2018

Re: [Pharo-users] [ANN] Teapot was moved to GitHub

by Attila Magyar

Esteban A. Maringolo wrote > Excellent material. > I also liked that you not only provided instructions for installation, > but also to set Teapot as a dependency. > > Please add the `pharo` tag to the repository, so it gets listed in the > topics section [1] and also helps bumping Pharo topic to the home of > the Topics page. Yeah, many of these were added by a contributor @fortizpenaloza, so big thanks to him. Sure, I added the tags. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 28, 2018

Re: [Pharo-users] Reify RBLiteralNode and RBBlockNode args/return with MetaLink?

by Manuel Leuenberger

Awesome, thanks for the effort Marcus! I was wondering if it would be useful to use matrix-testing for MetaLinks. I imagine having example methods which employ all features of the Smalltalk syntax (syntax on a postcard?), for which all intermediate results of expressions are known, then apply MetaLinks in all possible combinations (arguments x control) and check the reifications and side-effects against the oracle. Then the tests would generate a matrix of which combinations work and which don't. This should cover most of the possible executions. Cheers, Manuel > On 28 Nov 2018, at 11:55, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> >>>> iii) How are cascaded message sends reified? Am I supposed to instrument the cascade node or the individual message sends? >>>> >> >> https://pharo.fogbugz.com/f/cases/22702/support-before-after-intead-on-RBCa… <https://pharo.fogbugz.com/f/cases/22702/support-before-after-intead-on-RBCa…> >> >> It turns out this is just not implemented. Single message sends *inside* should work (as it calls the same code as a normal send to emit code). >> But even that needs tests. >> >> Cascade itself needs some code for links, then it will be easy to add reifications for #receiver and #value (and #operation). >> > > Done: > > https://github.com/pharo-project/pharo/pull/2018 <https://github.com/pharo-project/pharo/pull/2018> > > > Marcus

Nov. 28, 2018