February 2018 - Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #575: 21292-Remove-unnecessary-self-run-in-RPackageWithDoTest
by ci-pharo-ci-jenkins2＠inria.fr Feb. 19, 2018

Feb. 19, 2018

There is a new Pharo build available! The status of the build #575 was: SUCCESS. The Pull Request #911 was integrated: "21292-Remove-unnecessary-self-run-in-RPackageWithDoTest" Pull request url: https://github.com/pharo-project/pharo/pull/911 Issue Url: https://pharo.fogbugz.com/f/cases/21292 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[JOB][Research] 3 Year Advanced Research Position
by Marcus Denker Feb. 19, 2018

Feb. 19, 2018

Inria opended a call for experienced researchers. This is a three year contract, with in total 8 research positions. REQUIREMENTS - Have a French doctorate or an equivalent international degree - Be able to prove at least eight years of research and/or post-doctoral academic or industrial experience; - No age or nationality conditions. - Deadline: April 3rd, 2018 Before writing their research program, the applicants are strongly encouraged to contact the teams or project(s)-teams leaders concerned by their applications. More information on the official website: https://www.inria.fr/en/institute/recruitment/offers/advanced-research-posi… MISSION Join one of our two lines of research: Tools for Software Maintenance or New Programming Language Constructs for Software Evolution. THE REGION Lille is strategically located in Northern Europe with train connections to Paris (1h), London (1h30) and Brussels (30 min.) The Nord Pas de Calais region is a dynamic area in both industry and research for computer science with companies that are european leaders in their branch. Lille, the capital of northern France is an attractive metropolis of over 1 million inhabitants. Cost of living in Lille is lower than that of very big cities such as Paris and London. THE TEAM RMoD is an Inria research project team. It consists of 5 permant researchers (Inria CR and DR, as well as University Assistant Professors) and Engineers, postdocs and students (Master and PhD). RMoD is an international team with more than 20 members from six countries. LINKS: RMoD: http://rmod.lille.inria.fr INRIA Lille: http://www.inria.fr/lille/ INRIA in General: http://www.inria.fr Lille: http://en.wikipedia.org/wiki/Lille http://wikitravel.org/en/Lille Please contact the head of the research team: Stephane.Ducasse(a)inria.fr or one of the following group members: Nicolas.Anquetil(a)inria.fr, Marcus.Denker(a)inria.fr Permanent Link: https://rmod.inria.fr/web/blog/2018-02-17

1 0

Problem to save packages
by Roca Vincent Feb. 19, 2018

Feb. 19, 2018

Hi, I'm a new Pharo user (Pharo 5.0). I have created a package and now I just want to save it in the package-cache folder. But, when I try to do this using the Monticello Browser, I get an exception telling me the file I'm trying to save does not exist. I already managed to save some packages but I can't anymore. Thanks in advance for your help.

5 7

VirtualMachine vs. Platform and Bootstrap
by Torsten Bergmann Feb. 19, 2018

Feb. 19, 2018

Hi, 1. We can query for the VIRTUAL MACHINE and ask if it is 32 or 64 bit (internally depending on wordSize): Smalltalk vm is32Bit Anything OK on that side. 2. We can also query for the OPERATING SYSTEM we are running on using: Smalltalk os and there are subclasses for OSPlatform like Win32Platform, Win64Platform as well as Unix32Platform, unix64Platform, ... But when I evaluate "Smalltalk os" in Pharo 7 Build #70552 2a) I receive a Win32Platform instance which means 32 bit although I'm running on a Win 64 system 2b) I receive a Unix32Platform instance which means 32 bit although I'm running on a Ubuntu 64 system I see this as a clear bug and very confusing The reason for this behavior is simple: because I run with the 32 bit VM/image on these two 64 bit operating systems and in Pharo: for 2a) the#isActivePlatform method ask the VM (???)for the platform name (which is Win32 then) for 2b) the#isActivePlatform method also considers the word size from the VM (???) But to me the "os" should give me infos about the underlying operating system and is currently returning a wrong instance (because it falls back to querying about the running VM, not the real platform) This would be easy to fix with some UFFI calls (for instance piping from "uname -i" on Unix or "ver" on Windows). With UFFI I would also be able to give more and better infos in the platform hierarchy about the underlying OS. But doing this would introduce a dependency from the "Systems-Platforms" package to "UFFI" (and currently my understanding is that UFFI comes later) >From what I understood from the comment in getPwdViaFFI:with we also would like to focus on a minimal dependency for bootstrap ... and only depend on FFI and not UFFI. Any comments how we could deal with that best? Thx T.

4 3

[Pharo 7.0-dev] Build #573: 21363-coreMethodsForClass-send-but-not-implemented
by ci-pharo-ci-jenkins2＠inria.fr Feb. 18, 2018

Feb. 18, 2018

There is a new Pharo build available! The status of the build #573 was: SUCCESS. The Pull Request #913 was integrated: "21363-coreMethodsForClass-send-but-not-implemented" Pull request url: https://github.com/pharo-project/pharo/pull/913 Issue Url: https://pharo.fogbugz.com/f/cases/21363 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #572: 17913-LegacyWeakSubscription-should-be-merged-with-WeakAnnouncementSubscription
by ci-pharo-ci-jenkins2＠inria.fr Feb. 18, 2018

Feb. 18, 2018

There is a new Pharo build available! The status of the build #572 was: SUCCESS. The Pull Request #879 was integrated: "17913-LegacyWeakSubscription-should-be-merged-with-WeakAnnouncementSubscription" Pull request url: https://github.com/pharo-project/pharo/pull/879 Issue Url: https://pharo.fogbugz.com/f/cases/17913 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #571: 21366-Add-a-good-printOn-method-to-SHRange
by ci-pharo-ci-jenkins2＠inria.fr Feb. 17, 2018

Feb. 17, 2018

There is a new Pharo build available! The status of the build #571 was: SUCCESS. The Pull Request #910 was integrated: "21366-Add-a-good-printOn-method-to-SHRange" Pull request url: https://github.com/pharo-project/pharo/pull/910 Issue Url: https://pharo.fogbugz.com/f/cases/21366 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

we should include ReferenceFinder as part of Pharo
by Esteban Lorenzano Feb. 17, 2018

Feb. 17, 2018

Hi, Recently I was hunting a leak and I found that what we have now (pointers explorer) is not very good, so I dug into ReferenceFinder (in catalog) and everything became a lot easier. So, I wonder: Shouldnât we include it as part of the standard distribution? (also, taking into account we want to remove EyeInspector and related tools and pointer explored is based on it?) cheers, Esteban

2 1

About UFFI documentation deprecation.
by Stephane Ducasse Feb. 17, 2018

Feb. 17, 2018

About https://github.com/SquareBracketAssociates/Booklet-uFFI Dear (poor) reader, since years I tried to convince people understanding FFI to finish this documentation. But I failed. Apparently documenting FFI is not important enough. So I stopped to try and in the future I will remove simply this booklet because there is nothing as bad as a half done unfinished documentation. If within 6 months this documentation stays in this bad format, I will remove it from this repository. 15 of Febrary 2018. By 15 of August if nothing changed I will remove this project and all the associated infrastructure. S. Ducasse - ''Even jedi cannot move mountain.''

3 4

[Pharo 7.0-dev] Build #570: 21341-deprecate-theNonMetaclass
by ci-pharo-ci-jenkins2＠inria.fr Feb. 17, 2018

Feb. 17, 2018

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

1 0