- Pharo-dev - lists.pharo.org

Pharo 7 crash on Mac
by Bernhard Pieber Jan. 2, 2018

Jan. 2, 2018

Hi, I wanted to set up a new Pharo 7 image for contributing. I used the description from here: https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo After I had successfully cloned the pharo repository Pharo crashed. I am afraid I cannot remember the last thing I did before the crash. Nevertheless, maybe the crash dump is of some use for someone being able to interpret its content. I am on macOS Sierra 10.12.6. ./pharo --version 5.0 5.0.201708271955 Mac OS X built on Aug 27 2017 20:27:09 UTC Compiler: 4.2.1 Compatible Apple LLVM 6.1.0 (clang-602.0.53) [Production Spur VM] CoInterpreter VMMaker.oscog-eem.2265 uuid: 76b62109-629a-4c39-9641-67b53321df9a Aug 27 2017 StackToRegisterMappingCogit VMMaker.oscog-eem.2262 uuid: 8b531242-de02-48aa-b418-8d2dde0bec6c Aug 27 2017 VM: 201708271955 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Sun Aug 27 21:55:26 2017 +0200 $ Plugins: 201708271955 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Happy New Year! Bernhard

4 6

[Pharo 7.0-dev] Build #400: 20891-Changesorter-should-prompt-with-a-file-dialog
by ci-pharo-ci-jenkins2＠inria.fr Jan. 2, 2018

Jan. 2, 2018

There is a new Pharo build available! The status of the build #400 was: SUCCESS. The Pull Request #628 was integrated: "20891-Changesorter-should-prompt-with-a-file-dialog" Pull request url: https://github.com/pharo-project/pharo/pull/628 Issue Url: https://pharo.fogbugz.com/f/cases/20891 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #399: 20899-Add-comments-to-Color-methods
by ci-pharo-ci-jenkins2＠inria.fr Jan. 2, 2018

Jan. 2, 2018

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

1 0

upToAll: for ZnCharacterReadStream
by Bernhard Pieber Jan. 1, 2018

Jan. 1, 2018

I have created another pull request with an implementation for #upToAll: for ZnCharacterReadStream: https://github.com/pharo-project/pharo/pull/634 Here is the case: https://pharo.fogbugz.com/f/cases/20905 CI checks are in progress. Does that make it the first contribution in 2018? ;-) Let me know what you think. Happy New Year Bernhard

1 0

Best wishes for 2018
by Torsten Bergmann Jan. 1, 2018

Jan. 1, 2018

Only a few days left for 2017. Thanks to all who helped shaping Pharos future. May the lighthouse be with you in 2018 as well: World backgroundImage: (ZnEasy getJpeg: 'https://spotlight.it-notes.ru/wp-content/uploads/2017/08/02c48424be88ee36d5…') layout: #scaled Have fun! Bye T.

9 12

Streaming over a UTF-8 encoded file using upToAll:
by Bernhard Pieber Dec. 31, 2017

Dec. 31, 2017

Hi all, I want to stream over a file which is encoded in UTF-8 and have a problem with upToAll: answering more than it should. Here is a minimal test: 'Ãe' readStream upToAll: 'e'. This answers 'Ã' as expected. I wrote those two characters to a file: FileStream forceNewFileNamed: 'test' do: [ :stream | stream nextPutAll: 'Ãe' ]. I opened it using a text editor to verify the encoding. It is UTF-8 as expected. Now if I do the following... 'test' asFileReference readStreamDo: [ :stream | stream upToAll: 'e' ]. ... I get 'Ãe' instead of just 'Ã'. I tried explicitly setting a UTF8TextConverter: 'test' asFileReference readStreamDo: [ :stream | stream converter: UTF8TextConverter new; upToAll: 'e' ]. However, the result is still 'Ãe'. If I read the entire file first using #contentsOfEntireFile first it works: ('test' asFileReference readStreamDo: [ :stream | stream contentsOfEntireFile ]) readStream upToAll: 'e' However, that defies the purpose of streaming. Can someone tell me what I am doing wrong? I am on Pharo 6.1 on a Mac. Bernhard

3 8

FreeCell resurrection
by Pavel Krivanek Dec. 31, 2017

Dec. 31, 2017

Hi, I fixed the old FreeCell code from Squeak to be able to run on Pharo 6 and 7. Repository: https://github.com/pavel-krivanek/FreeCell How to load: Metacello new baseline: 'FreeCell'; repository: 'github://pavel-krivanek/FreeCell/src'; load. How to run: FreeCell open. Cheers, -- Pavel

1 0

an error in ZnResourceMetaUtils>>queryKeyValueSafeSet ?
by Esteban Lorenzano Dec. 31, 2017

Dec. 31, 2017

Hi all, Sven Iâm doing some experiments with twitter and posting and I found that twitter does not accept a post with $? in the status string (it throws an error). Now, if I change ZnResourceMetaUtils>>queryKeyValueSafeSet removing $? from the safe set it works correctly. the question is: this is a twitter error or a ZnResourceMetaUtils>>queryKeyValueSafeSet error and the $? shouldnât be considered safe (and then it should be percent encoded?) cheers, Esteban

2 3

Calendrical capabilities
by publius789＠gmail.com Dec. 30, 2017

Dec. 30, 2017

I am new to the Pharo world and looking at capabilities for potential applications. One of the first things I am interested in is Calendar processing capabilities. I haven't had a chance to look at the code yet, but specifically how much does Pharo's Date/Calendar capabilities match that in the java.util package for Java 9? Additionally, is there any way to give the number of business days between two dates for a particular local calendar? If so, what's the format for a local calendar? I'm going to take a look at the code shortly, but if anyone can shed a general light what currently exists it would be greatly appreciated. Regards, Jim

4 7

PR: Compressed sources inside the object memory
by Pavel Krivanek Dec. 30, 2017

Dec. 30, 2017

Hi, when the Pharo 7 image is being built on top of the bootstrapped image, all loaded code is placed in the changes file so this process ends with an empty sources file, huge changes file and the image. We condense the sources file for every build so we distribute the Pharo 7 as three files - image, huge sources (over 30 MB) and almost empty changes file. As consequence every build has own sources file that can be shared between images based on the same build - so when we will release the Pharo 7, the sources file can be shared as it was for previous releases, but as soon as some fixing version of Pharo 7 will be released, it will require a new specific sources file. As one possible solution I tried to create a pull request that resurrects from oblivion an old code made for Squeak 3.7 that introduced option of compressed sources files. Such files use segments that are stored in compressed form so it is not so small as one single zip file but still good enough. From original uncompressed file of size 30.8 MB it generates 7.1 MB file while single zip has 6.1 MB. Of course the image file is bigger but: - the amount of new objects is low so it should not make much more stress on GC - we already used to have big images because the condenser was not working and it was not a big issue - the amount of distributed files will be the same as in case of Pharo 6 (image+changes) so it means less troubles - the sources file can be easily restored, deleted from the object memory and used the same way as before - we are not using the nice concept of the image well enough. All data that are not really shared between images or serve as backup information should be stored inside image Please review this PR. As a side effect it makes the sources file mechanism (but not changes file) independent on the FileStream classes that are deprecated. PR: https://github.com/pharo-project/pharo/pull/631 The pre-built image: https://ci.inria.fr/pharo-ci -jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/PR-631/ lastSuccessfulBuild/artifact/bootstrap-cache/Pharo7.0-32bit-57ddc75.zip Cheers, -- Pavel

4 13