- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Do we remove EyeInspector from Pharo 70?

by Stephane Ducasse

Thanks for your information. I do not know but indeed then we will should have a look. On Sun, Feb 11, 2018 at 9:40 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > I sometimes use the Eye Pointer Inspector to find memory leaks ... is there > a replacement for that? > > Peter > > On Sun, Feb 11, 2018 at 9:29 PM, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: >> >> I would vote for. >> >> Stef >> >

Feb. 14, 2018

[ANN] Remember tomorrow 15/02 16hUTC tech talk "contributing to Pharo 7"

by Esteban Lorenzano

Hi, Subject says all. Iâm a bit sick but I will do my best to handle the session :D See you all tomorrow!

Feb. 14, 2018

Re: [Pharo-dev] Pavel's ChangeLog week of 2018-02-05

by Stephane Ducasse

Thanks Pavel this looks quite fast :). Do you have a scenario in mind that could take advantage of this? Stef On Mon, Feb 12, 2018 at 10:33 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hi, > > among other less interesting things, I spent some time on existing > PosixSharedMemory project. It is a UFFI binding for the LibC methods > that provide support for the memory allocation between several > separate processes. I significantly improved the performance by > implementing the block access. Writing of 10MB byte array takes about > 1 millisecond, reading of it from other image took me about 4 > milliseconds. While serialization with Fuel is very fast, it opens > interesting possibilities. > To have a shared memory without synchronization tools is not very > useful so I wrote a basic UFFI interface for the POSIX named > semaphores. They are quite easy to use and work nicely with Pharo. The > VM can all wait on the semaphore or it can check the status of it > periodically in an image thread. It has two small disadvantages. It > requires to dynamically link the next library (pthread) and they must > be cleaned manually. I plan to look at System V alternative in future. > Now we should write a nice framework for inter-image communication on > top of it or/and adopt Seamless for it ;-) > > Cheers, > -- Pavel >

Feb. 14, 2018

Re: [Pharo-dev] Ficus question

by Stephane Ducasse

It was a kind of model for epicea. Stef On Wed, Feb 14, 2018 at 8:50 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > What is Ficus? > > Norbert > >> Am 13.02.2018 um 18:23 schrieb Stephane Ducasse <stepharo.self(a)gmail.com>: >> >> Hi martin >> >> I would like to know what is the API Ficus uses from TClass. >> Do you have an idea? >> >> >> Stef >

Feb. 14, 2018

Re: [Pharo-dev] Iceberg 0.6.8 backported to 6.1

by Sean P. DeNigris

Sean P. DeNigris wrote >> I backported iceberg 0.6.8 to Pharo 6.1 FYI #60530 is supposed to have Iceberg 0.6.8, but there is something amiss. For example, the IceGithubRepositoryType>>#mcRepository in the image is not the one in 0.6.8 (https://github.com/pharo-vcs/iceberg/blob/20eaebcfdb3ba94cd55e9ed48c2cbf300…) Esteban is aware. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Feb. 14, 2018

[Pharo 7.0-dev] Build #546: 21338-localMetaclassMethod

by ci-pharo-ci-jenkins2＠inria.fr

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

Feb. 14, 2018

[Pharo 7.0-dev] Build #545: 21180-Compiling-DoIts-should-not-embed-source-code

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #545 was: SUCCESS. The Pull Request #880 was integrated: "21180-Compiling-DoIts-should-not-embed-source-code" Pull request url: https://github.com/pharo-project/pharo/pull/880 Issue Url: https://pharo.fogbugz.com/f/cases/21180 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 14, 2018

[Pharo 7.0-dev] Build #544: 21245-SmalltalkImage current imageDirectory should give a fileReference instead of a path

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #544 was: SUCCESS. The Pull Request #805 was integrated: "21245-SmalltalkImage current imageDirectory should give a fileReference instead of a path" Pull request url: https://github.com/pharo-project/pharo/pull/805 Issue Url: https://pharo.fogbugz.com/f/cases/21245 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 14, 2018

Re: [Pharo-dev] Ficus question

by Norbert Hartl

What is Ficus? Norbert > Am 13.02.2018 um 18:23 schrieb Stephane Ducasse <stepharo.self(a)gmail.com>: > > Hi martin > > I would like to know what is the API Ficus uses from TClass. > Do you have an idea? > > > Stef

Feb. 14, 2018

Re: [Pharo-dev] [ANN] Pharo Consortium New Platinum Member: ENSTA Bretagne

by Tudor Girba

Very cool, indeed! Doru > On Feb 13, 2018, at 8:58 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > We are super happy! > > > On Tue, Feb 13, 2018 at 7:55 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> The Pharo Consortium is very happy to announce that ENSTA Bretagne >> has joined the Consortium as a Platinum Member. >> >> About >> - ENSTA Bretagne: http://www.ensta-bretagne.fr >> - Pharo Consortium: http://consortium.pharo.org >> >> The goal of the Pharo Consortium is to allow companies and institutions to >> support the ongoing development and future of Pharo. >> >> Individuals can support Pharo via the Pharo Association: >> >> - http://association.pharo.org >> > -- www.tudorgirba.com www.feenk.com "Problem solving efficiency grows with the abstractness level of problem understanding."

Feb. 13, 2018