- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #777: Add-copy-title-command-to-windows
by ci-pharo-ci-jenkins2＠inria.fr Sept. 24, 2019

Sept. 24, 2019

There is a new Pharo build available! The status of the build #777 was: FAILURE. The Pull Request #4711 was integrated: "Add-copy-title-command-to-windows" Pull request url: https://github.com/pharo-project/pharo/pull/4711 Issue Url: https://github.com/pharo-project/pharo/issues/Add Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #776: 2174-withoutDuplicates
by ci-pharo-ci-jenkins2＠inria.fr Sept. 24, 2019

Sept. 24, 2019

There is a new Pharo build available! The status of the build #776 was: SUCCESS. The Pull Request #4699 was integrated: "2174-withoutDuplicates" Pull request url: https://github.com/pharo-project/pharo/pull/4699 Issue Url: https://github.com/pharo-project/pharo/issues/2174 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #775: 4686-code-completion-not-working-properly-on-inspectors
by ci-pharo-ci-jenkins2＠inria.fr Sept. 24, 2019

Sept. 24, 2019

There is a new Pharo build available! The status of the build #775 was: FAILURE. The Pull Request #4689 was integrated: "4686-code-completion-not-working-properly-on-inspectors" Pull request url: https://github.com/pharo-project/pharo/pull/4689 Issue Url: https://github.com/pharo-project/pharo/issues/4686 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #774: 4654-Add-comment-to-RBProgramNodeisFaulty
by ci-pharo-ci-jenkins2＠inria.fr Sept. 24, 2019

Sept. 24, 2019

There is a new Pharo build available! The status of the build #774 was: FAILURE. The Pull Request #4692 was integrated: "4654-Add-comment-to-RBProgramNodeisFaulty" Pull request url: https://github.com/pharo-project/pharo/pull/4692 Issue Url: https://github.com/pharo-project/pharo/issues/4654 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #773: 4677-simplify-lookupSymbol
by ci-pharo-ci-jenkins2＠inria.fr Sept. 23, 2019

Sept. 23, 2019

There is a new Pharo build available! The status of the build #773 was: FAILURE. The Pull Request #4688 was integrated: "4677-simplify-lookupSymbol" Pull request url: https://github.com/pharo-project/pharo/pull/4688 Issue Url: https://github.com/pharo-project/pharo/issues/4677 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #772: 3434-Random--nextInt-should-fail-early-when-argument-is-FloatInfinity
by ci-pharo-ci-jenkins2＠inria.fr Sept. 23, 2019

Sept. 23, 2019

There is a new Pharo build available! The status of the build #772 was: FAILURE. The Pull Request #4690 was integrated: "3434-Random--nextInt-should-fail-early-when-argument-is-FloatInfinity" Pull request url: https://github.com/pharo-project/pharo/pull/4690 Issue Url: https://github.com/pharo-project/pharo/issues/3434 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #771: Context tempNamed: use Debuggermap directly
by ci-pharo-ci-jenkins2＠inria.fr Sept. 23, 2019

Sept. 23, 2019

There is a new Pharo build available! The status of the build #771 was: FAILURE. The Pull Request #4691 was integrated: "Context tempNamed: use Debuggermap directly" Pull request url: https://github.com/pharo-project/pharo/pull/4691 Issue Url: https://github.com/pharo-project/pharo/issues/ContextTempAt Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Next Pharo Sprint: Sept 27
by Marcus Denker Sept. 23, 2019

Sept. 23, 2019

We will organize a Pharo sprint / Moose dojo Sept 27, starting at 10:00am. (Local Time Paris). Goals of this sprint: - Pharo 8: Fix issues from tracker https://github.com/pharo-project/pharo/issues Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events We have added a Board to coordinate the work: https://github.com/orgs/pharo-project/projects/9 Known Local Sprint meetings - Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come A list of all Pharo Event of the year an be found here: https://association.pharo.org/events

1 0

Re: [Pharo-dev] [Pharo-users] FFI beginner question
by Guillermo Polito Sept. 23, 2019

Sept. 23, 2019

See https://github.com/pharo-project/pharo/issues/4693 <https://github.com/pharo-project/pharo/issues/4693> https://github.com/pharo-project/pharo/issues/4694 <https://github.com/pharo-project/pharo/issues/4694> https://github.com/pharo-project/pharo/issues/4695 <https://github.com/pharo-project/pharo/issues/4695> Of course, if somebody wants to help, youâre welcome to :) Guille > El 23 sept 2019, a las 13:59, Guillermo Polito <guillermopolito(a)gmail.com> escribiÃ³: > > Just more detail into it: > > - the source code of the booklet, written in Pillar, resides in here: > https://github.com/SquareBracketAssociates/Booklet-uFFI <https://github.com/SquareBracketAssociates/Booklet-uFFI> > > - Iâve been in the last weeks doing a pass on it (see branch version2 https://github.com/SquareBracketAssociates/Booklet-uFFI/tree/version2 <https://github.com/SquareBracketAssociates/Booklet-uFFI/tree/version2>) > I started adding examples, and enhancing the explanations. > I got particularly blocked when explaining marshalling where I saw several issues to address / features to add before continuing documenting > > I have some issues written down to fix in FFI soon: > 1 - unify vocabulary: module and library in the API (see #ffiCall:module: #macModuleName #ffiLibraryName, #ffiLibraryâ¦) > 2 - some of the names above are misleading (#ffiLibraryName returning a library object and not a name for example) > 3 - extend literal object support to floats > 4 - add a strict (but safe) mode where types for literals are mandatory (otherwise marshalling can go wrong :)) > > Iâll create issues for these in the next hours ^^. > >> El 23 sept 2019, a las 13:38, Richard O'Keefe <raoknz(a)gmail.com <mailto:raoknz@gmail.com>> escribiÃ³: >> >> how do I >> connect C numeric >> types introduced by the library to FFI? > > Hi Richard, what do you mean? Do you have an example? Whatâs the signature of your C function look like? > > Guille

1 0

[Pharo 8.0] Build #770: 4684-BeaconSignal-printOneLineString
by ci-pharo-ci-jenkins2＠inria.fr Sept. 23, 2019

Sept. 23, 2019

There is a new Pharo build available! The status of the build #770 was: SUCCESS. The Pull Request #4685 was integrated: "4684-BeaconSignal-printOneLineString" Pull request url: https://github.com/pharo-project/pharo/pull/4685 Issue Url: https://github.com/pharo-project/pharo/issues/4684 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0