- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #747: 21668-Mark-deprecated-classes-as-deprecated
by ci-pharo-ci-jenkins2＠inria.fr March 31, 2018

March 31, 2018

There is a new Pharo build available! The status of the build #747 was: SUCCESS. The Pull Request #1169 was integrated: "21668-Mark-deprecated-classes-as-deprecated" Pull request url: https://github.com/pharo-project/pharo/pull/1169 Issue Url: https://pharo.fogbugz.com/f/cases/21668 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Pavel's ChangeLog week of 2018-03-19
by Pavel Krivanek March 31, 2018

March 31, 2018

Hi, I did some serious Ring 2 refactorings that I wanted to have finished before the integration into Pharo. Because Pharo now starts to support the stateful traits, it needs to be supported by the metamodel too. However, we need to be able to model the images with the old traits as well and from the internal point of view, they are quite different. Moreover, if you load a code into the Ring model, you sometimes do not know if the behavior, where you load a method, is a class or you later will realize that it is a trait. The Ring 2 used for this a complex machinery that was able to switch the behavior kind using the #becomeForward: message. Some time ago I decided to solve both problems by introducing of the behavior strategies. That means that every behavior is a composition of an instance of the RGBehavior class and a behavior strategy (e.g. RGClassStrategy). Then changing of the behavior kind is then only a matter of swapping of the strategy (which has a state so it not so straightforward but still easy). The classes like RGClass or RGTrait are still present but now they are only the factories that produce the behaviors and they have no real instances. The next big thing I decided to do in Ring is renaming of the entities. From the beginning, I used the prefix "RG2" to avoid the collisions with the old Ring implementation but I supposed that before the final release it will be renamed because, from the user perspective, the Ring 2 should be a replacement for the old Ring and not completely separate project. The attempts to replace the old Ring with the new one showed me, that it is possible, but the old Ring is so deeply used in the system that it leads to a huge amount of instabilities. So I decided to rename the Ring 2 classes and some methods to do not make collisions with the old implementation. While the old Ring class was named RGClassDefinition and in Ring 2 it was RG2ClassDefinition, now it is renamed simply to RGClass. RG2Definition was renamed to RGObject. The only ugly exception is RG2Package which is now named RGPackageDefinition because the old Ring does not follow the naming convention and uses the name "RGPackage". The old Ring packages will get suffix "Deprecated" into their names. The old Ring and the Ring2 can coexist in one image and it is still possible to load the new Ring into the Pharo 6. Then I started to work on the changes metamodel for Ring with the goal to be able to record, reproduce and revert (almost) all changes that the user does in the model. The main goal of it is to be able to get comparisons of two models and compute loading order of the changes so it will be more easy to replace the Monticello metamodel and the metamodel for code differences with a single solid solution based on Ring. Cheers, -- Pavel

5 7

Why is FileSystem's Path class private ?
by Damien Pollet March 31, 2018

March 31, 2018

The class Path from FileSystem is documented as privateâ¦ but it should be public, shouldn't it? First hint is that it's named with a public name: (Path not FileSystemPath). Then, consider the following use-case : if you have a file name in some config file (.ini, .tomlâ¦) then that's really a Path, not a resolved FileReference. I'm not talking about RelativePath and AbsolutePath, those can be hidden away since Path provides the factory and DSL methods. IMHO they should still be renamed to a more private name. -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

4 7

Migrator: to help you migrating to latest version of Pharo :)
by Stephane Ducasse March 31, 2018

March 31, 2018

Hi Today during the Pharo sprint I went over all the deprecated methods in Pharo 70 and Pharo 60 and I checked if I could convert the deprecated ones into deprecated:transformWith: so that the conversion is done automatically to help people migrating from one version to the other. I also collected all the deprecated methods as well as the new deprecated:transformWith: methods into a Package called Migrator (should still merge the Pharo 60 and Pharo 70 version). I plan to do the same for Pharo 50, 40, 30, 20. If you want to help feel free. At the end we will have one package containing all the deprecated methods of all the past versions. The way we will be able to support a smoother conversion to more recent version. Stef

4 5

[Pharo 7.0-dev] Build #746: 21664-introduce-class-deprecation-refactoring
by ci-pharo-ci-jenkins2＠inria.fr March 31, 2018

March 31, 2018

There is a new Pharo build available! The status of the build #746 was: FAILURE. The Pull Request #1167 was integrated: "21664-introduce-class-deprecation-refactoring" Pull request url: https://github.com/pharo-project/pharo/pull/1167 Issue Url: https://pharo.fogbugz.com/f/cases/21664 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #745: 21661-Should-add-a-test-and-rescue-Point--scaleTo-
by ci-pharo-ci-jenkins2＠inria.fr March 30, 2018

March 30, 2018

There is a new Pharo build available! The status of the build #745 was: SUCCESS. The Pull Request #1166 was integrated: "21661-Should-add-a-test-and-rescue-Point--scaleTo-" Pull request url: https://github.com/pharo-project/pharo/pull/1166 Issue Url: https://pharo.fogbugz.com/f/cases/21661 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #744: 21653 - ShiftClassInstaller gives error when changing superclass to new one with variables
by ci-pharo-ci-jenkins2＠inria.fr March 30, 2018

March 30, 2018

There is a new Pharo build available! The status of the build #744 was: SUCCESS. The Pull Request #1165 was integrated: "21653 - ShiftClassInstaller gives error when changing superclass to new one with variables" Pull request url: https://github.com/pharo-project/pharo/pull/1165 Issue Url: https://pharo.fogbugz.com/f/cases/21653 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #743: 21438-There-is-code-in-_UnpackagedPackage-in-Pharo-7
by ci-pharo-ci-jenkins2＠inria.fr March 30, 2018

March 30, 2018

There is a new Pharo build available! The status of the build #743 was: SUCCESS. The Pull Request #1164 was integrated: "21438-There-is-code-in-_UnpackagedPackage-in-Pharo-7" Pull request url: https://github.com/pharo-project/pharo/pull/1164 Issue Url: https://pharo.fogbugz.com/f/cases/21438 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Testers Required] New FreeType implementation using FFI
by tesonep＠gmail.com March 30, 2018

March 30, 2018

I have implemented the backend of FreeType using only FFI calls. So the whole implementation is in the image side, the current plugin has a lot of problems handling the release of the pointers. The new implementation is using the mechanism that is already present in UFFI to release the Heap pointers, so it should be more stable and easier to modify if there is an issue. The FT2Plugin is not used anymore in this version. I have tested it in the different platforms, but beside OSX I have only made a smoke test. I need some users to try it, so I ask you if you can test in different installations. The image can be downloaded from the CI 32 bits: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… 64 bits: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… Thanks to all!! Cheers. -- Pablo Tesone. tesonep(a)gmail.com

3 4

Strange deprecation of SystemVersion
by Stephane Ducasse March 30, 2018

March 30, 2018

Hi I do not really understand why fromShortVErsionString: and friends have been deprecated (that part I can understand) but why do they depend on an extension packaged in tests. Stef

1 0