- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #1199: 22373-LinkedListreject-is-slow
by ci-pharo-ci-jenkins2＠inria.fr Aug. 30, 2018

Aug. 30, 2018

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

1 0

[Pharo 7.0-dev] Build #1198: 22366-TabMorph-should-use-displayScaleFactor
by ci-pharo-ci-jenkins2＠inria.fr Aug. 29, 2018

Aug. 29, 2018

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

1 0

[Pharo 7.0-dev] Build #1197: 21989-TPrintOnSequencedTesttestStoreOn-contains-commented-code
by ci-pharo-ci-jenkins2＠inria.fr Aug. 29, 2018

Aug. 29, 2018

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

1 0

[Pharo 7.0-dev] Build #1196: 22370-RF-tests-related-to-level
by ci-pharo-ci-jenkins2＠inria.fr Aug. 29, 2018

Aug. 29, 2018

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

1 0

[Pharo 7.0-dev] Build #1195: 21504-StringromanNumber-should-be-symmetric-to-IntegerprintStringRoman
by ci-pharo-ci-jenkins2＠inria.fr Aug. 29, 2018

Aug. 29, 2018

There is a new Pharo build available! The status of the build #1195 was: SUCCESS. The Pull Request #1619 was integrated: "21504-StringromanNumber-should-be-symmetric-to-IntegerprintStringRoman" Pull request url: https://github.com/pharo-project/pharo/pull/1619 Issue Url: https://pharo.fogbugz.com/f/cases/21504 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

ZnCharacterEncoder default instances
by Alistair Grant Aug. 28, 2018

Aug. 28, 2018

Hi Sven and Everyone, Instantiation of character encoders is relatively expensive, as can be seen by the following code snippet: | count str ba enc new old | count := 10000. str := 'test-Ã¤Ã¶Ã¼'. new := [ count timesRepeat: [ (ZnCharacterEncoder newForEncoding: 'utf8') encodeString: str ] ] timeToRunWithoutGC. enc := ZnCharacterEncoder newForEncoding: 'utf8'. old := [ count timesRepeat: [ enc encodeString: str ] ] timeToRunWithoutGC. { old. new. } " #(14 122)" What do you think of the idea of caching default instances of encoders? My idea was to have a dictionary in ZnCharacterEncoder and add a class method #forEncoding:. This would lazily create an instance, store it in the dictionary, and then re-use the instance whenever that encoder is requested. If people really want their own instance (not sure why, there aren't any instance variables, and so there's no state), they can use the existing #newForEncoding:. For example, sending #exists to a file reference currently instantiates two encoders. This was actually previously fixed by #20273[1], but seems to have been lost with the refactoring of FilePluginPrims to File. From memory, Cyril's application saved 12 seconds by caching the encoder. But in that case the instance was private to the file plugin primitives. This would be a more general solution. [1] https://pharo.fogbugz.com/f/cases/20273/FilePluginPrims-could-save-an-encod… Thanks, Alistair

2 3

Debugging FFI Calls
by Eliot Miranda Aug. 27, 2018

Aug. 27, 2018

Hi All, the latest VMs support a new facility which catches and reports exceptions during FFI calls as primitive failures. That means that if you have the relevant support code loaded (described below) and depending on dialect, you write your FFI interface method to contain an error code, or you're using the UnifiedFFI which uses invokeWithArguments:, then any exception that occurs during the FFI call will be caught and reported to use with the error code bound to an instance of ExceptionInFFICall, which contains a platform-specific error code and the pc at which it occurred. To use this facility you'll need to download a VM built yesterday or later (it should be derived from VMMaker.oscog-eem.2435 or later), or build your own from the tip of the Cog branch in opensmalltalk/vm. You'll then need to update the image code to install ExceptionInFFICall appropriately: in Pharo6 load SLICE 22367 in Squeak load the latest FFI code from source.squeak.org/FFI and update your image from trunk in Cuis, you'll need to adapt these changes to Cuis (sorry!!) There are two command-line flags to override the default behavior. [-]-failonffiexception causes the handling to be applied to all FFI calls, so if a method doesn't contain an error, you'll just see a primitive failure, and if ExceptionInFFICall is not installed you'll see only an error number in the call's error code. [-]-nofailonffiexception ignores exceptions during FFI calls, hence defaulting to the old behavior of crashing the VM (which may be useful if one is using a low-level debugger to debug the VM and/or external code). HTH _,,,^..^,,,_ best, Eliot

1 0

In Pharo6 what has happened to package scripts?
by Eliot Miranda Aug. 27, 2018

Aug. 27, 2018

Hi All, I'm trying to submit a SLICE for Pharo6 that contains chains related to FFI error handling. This SLICE needs a package script to recreate the specialObjectsArray. But I see no accessor for editing package scripts in the Pharo6 Monticello Browser. Have package scripts become unsupported? If so, what is the alternative? If not, how does one edit them? _,,,^..^,,,_ best, Eliot

1 0

[Pharo 7.0-dev] Build #1194: 22172-Some-test-in-MustBeBooleanTests-are-rotten
by ci-pharo-ci-jenkins2＠inria.fr Aug. 27, 2018

Aug. 27, 2018

There is a new Pharo build available! The status of the build #1194 was: FAILURE. The Pull Request #1720 was integrated: "22172-Some-test-in-MustBeBooleanTests-are-rotten" Pull request url: https://github.com/pharo-project/pharo/pull/1720 Issue Url: https://pharo.fogbugz.com/f/cases/22172 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Submit your Project to the ESUG Awards
by N. Bouraqadi Aug. 27, 2018

Aug. 27, 2018

Hi everyone! This is a reminder to submit your projects to the ESUG Innovation Technology Awards. It will be held on september the 10th as part of the ESUG conference in Sardinia (https://esug.github.io/2018-Conference/conf2018.html) Any Pharo Smalltalk-related project is eligible. All you need to do is provide me with few info and give a short demo during the awards session. I hope to hear from you soon, Noury

2 1