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

Recommendation for password encryption?
by Mariano Martinez Peck Sept. 30, 2022

Sept. 30, 2022

Hi guys. Some time ago I asked about the best way to encrypt a password. Some of the recommendations I got was: 1) Generally for passwords you do not write a decrypt method for security purposes (eg you do not want people to be able to reverse engineer the encrypted password easily) 2) put a little salt 3) There is http://www.squeaksource.com/Cryptography/PasswordHashingFFI 4) I should not decrypt password but instead I should compare both encrypted versions to see if they are equal. My scenario is the following. I need to store database passwords in text files. So I don't want to let them as plain text. And while I understand 4), I think it's a different scenario than mine. I know that some database driver may allow you to directly send the encrypted password. But still...I have another similar scenario in which I have to store a password and then send it (unencrypted)...so I kind of really need a bi-directional encryption. Now..I would try to avoid having an external library + FFI. Any ideas what is the best thing I can do? And how could I solve 1) if I want bidirectional like in my case? Thanks in advance, -- Mariano http://marianopeck.wordpress.com

9 26

Re: [Pharo-project] Parsing and navigating Html
by Paul DeBruicker July 16, 2020

July 16, 2020

On 12/05/2010 06:02 AM, pharo-project-request(a)lists.gforge.inria.fr wrote: > From: St?phane Ducasse<stephane.ducasse(a)inria.fr> > Subject: [Pharo-project] Parsing and navigating Html > To:"Pharo-project(a)lists.gforge.inria.fr Development" > <Pharo-project(a)lists.gforge.inria.fr> > Message-ID:<1C53DFD8-3021-4233-BC83-CE8C1EA8D103(a)inria.fr> > Content-Type: text/plain; charset=us-ascii > > Hi > > I would like extract partial information from HTML pages. > So I started to play and fix HTMLParser. > > Now does anybody know alternatives? > > Second, does anybody develop a lib to query HTML structure as with the XMLSupport package? > > Stef The Soup package on SqueakSource.com works OK.

3 4

Re: [Pharo-dev] [Vm-dev] Image crashing on startup, apparently during GC
by Eliot Miranda June 3, 2019

June 3, 2019

Hi Damien, On Fri, Mar 23, 2018 at 12:38 PM, Damien Pollet <damien.pollet(a)gmail.com> wrote: > > Here are the files (image and various outputs). Running with --leakcheck > does mention a few object leaks (see output.txt); > Indeed the image is corrupt at start-up. See below. > I'm not sure where to get or how to build an assert VM. > When you build a phar. VM under build.macos64x64/pharo.cog.spur using the mvm script (mvm -A) you produce an assert VM in PharoAssert.app. > I also realized the VM I had was from this summer (the one that comes with > a 70 image with zeroconf). The output files I include were produced by the > VM at get.pharo.org/64/vmLatest70 > > https://www.dropbox.com/s/y8yqjuzd9nsvy1u/clap-broken.tar.gz?dl=0 > > On 20 March 2018 at 18:17, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > >> >> Hi Damien, >> >> On Tue, Mar 20, 2018 at 3:12 AM, Damien Pollet <damien.pollet(a)gmail.com> >> wrote: >> >>> >>> Hi, I have a Pharo image that crashes the VM on startup. The crash >>> report below seems to incriminate GC. Should I make it available somewhere >>> online? What's most convenient? >>> >> >> Don't care. Anywhere it can be downloaded from. Also, try running with >> -leakcheck 15, preferably in an assert VM and see if that gets you >> additional information. >> >> >>> >>> Process: Pharo [64892] >>> Path: /Users/USER/*/Pharo.app/Contents/MacOS/Pharo >>> Identifier: org.pharo.Pharo >>> Version: 5.0.201708271955 (5.0.201708271955) >>> >> Right. This VM is prior to the bug fixes in VMMaker.oscog-eem.2320: Spur: Fix a bad bug in SpurPlnningCompactor. unmarkObjectsFromFirstFreeObject, used when the compactor requires more than one pass due to insufficient savedFirstFieldsSpace, expects the corpse of a moved object to be unmarked, but copyAndUnmarkObject:to:bytes:firstField: only unmarked the target. Unmarking the corpse before the copy unmarks both. This fixes a crash with ReleaseBuilder class>>saveAsNewRelease when non-use of cacheDuring: creates lots of files, enough to push the system into the multi-pass regime. Pharo urgently needs to upgrade the VM to one more up to date than 2017 08 27 (in fact more up-to-date than opensmalltalk/vm commit 0fe1e1ea108e53501a0e728736048062c83a66ce, Fri Jan 19 13:17:57 2018 -0800). The bug that VMMaker.oscog-eem.2320 fixes can result in image corruption in large images, and can occur (as it has here) at start-up, causing one's work to be irretrievably lost. > Code Type: X86-64 (Native) >>> Parent Process: ??? [64888] >>> Responsible: Pharo [64892] >>> User ID: 501 >>> >>> Date/Time: 2018-03-19 20:27:03.906 +0100 >>> OS Version: Mac OS X 10.13.3 (17D102) >>> Report Version: 12 >>> Anonymous UUID: 6D022236-78DD-6676-117F-EADA56D5D1BE >>> >>> Sleep/Wake UUID: AC9E4E55-3CDB-4B4F-A6B4-51ACB1177154 >>> >>> Time Awake Since Boot: 28000 seconds >>> Time Since Wake: 6500 seconds >>> >>> System Integrity Protection: enabled >>> >>> Crashed Thread: 0 Dispatch queue: com.apple.main-thread >>> >>> Exception Type: EXC_BAD_ACCESS (SIGABRT) >>> Exception Codes: KERN_INVALID_ADDRESS at 0x000000012b67c0b0 >>> Exception Note: EXC_CORPSE_NOTIFY >>> >>> VM Regions Near 0x12b67c0b0: >>> VM_ALLOCATE 000000011adfc000-00000001259fc000 [172.0M] >>> rw-/rwx SM=PRV >>> --> >>> STACK GUARD 0000700005613000-0000700005614000 [ 4K] >>> ---/rwx SM=NUL stack guard for thread 1 >>> >>> Application Specific Information: >>> abort() called >>> >>> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread >>> 0 libsystem_kernel.dylib 0x00007fff53fbde3e __pthread_kill + 10 >>> 1 libsystem_pthread.dylib 0x00007fff540fc150 pthread_kill + 333 >>> 2 libsystem_c.dylib 0x00007fff53f1a312 abort + 127 >>> 3 org.pharo.Pharo 0x0000000104ed8997 sigsegv + 190 >>> 4 libsystem_platform.dylib 0x00007fff540eff5a _sigtramp + 26 >>> 5 ??? 000000000000000000 0 + 0 >>> 6 org.pharo.Pharo 0x0000000104e73558 markObjects + 464 >>> 7 org.pharo.Pharo 0x0000000104e72d40 fullGC + 72 >>> 8 org.pharo.Pharo 0x0000000104e92dea primitiveFullGC + >>> 45 >>> 9 org.pharo.Pharo 0x0000000104e52425 interpret + 26715 >>> 10 org.pharo.Pharo 0x0000000104e5c7f6 >>> enterSmalltalkExecutiveImplementation + 152 >>> 11 org.pharo.Pharo 0x0000000104e4be6c interpret + 674 >>> 12 org.pharo.Pharo 0x0000000104ed9cc1 >>> -[sqSqueakMainApplication runSqueak] + 394 >>> 13 com.apple.Foundation 0x00007fff2e6d696c >>> __NSFirePerformWithOrder + 360 >>> 14 com.apple.CoreFoundation 0x00007fff2c579127 >>> __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 >>> 15 com.apple.CoreFoundation 0x00007fff2c57904f >>> __CFRunLoopDoObservers + 527 >>> 16 com.apple.CoreFoundation 0x00007fff2c55b6a8 __CFRunLoopRun + >>> 1240 >>> 17 com.apple.CoreFoundation 0x00007fff2c55af43 >>> CFRunLoopRunSpecific + 483 >>> 18 com.apple.HIToolbox 0x00007fff2b872e26 >>> RunCurrentEventLoopInMode + 286 >>> 19 com.apple.HIToolbox 0x00007fff2b872a9f >>> ReceiveNextEventCommon + 366 >>> 20 com.apple.HIToolbox 0x00007fff2b872914 >>> _BlockUntilNextEventMatchingListInModeWithFilter + 64 >>> 21 com.apple.AppKit 0x00007fff29b3df5f _DPSNextEvent + >>> 2085 >>> 22 com.apple.AppKit 0x00007fff2a2d3b4c >>> -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] >>> + 3044 >>> 23 com.apple.AppKit 0x00007fff29b32d6d -[NSApplication >>> run] + 764 >>> 24 com.apple.AppKit 0x00007fff29b01f1a NSApplicationMain >>> + 804 >>> >>> -- >>> Damien Pollet >>> type less, do more [ | ] http://people.untyped.org/damien.pollet >>> >>> >> >> >> -- >> _,,,^..^,,,_ >> best, Eliot >> >> > > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet > > -- _,,,^..^,,,_ best, Eliot

9 26

Recent Pharo 6.1 OSX shows lots of "Error: unsupported compressor 8 on command line"
by Tim Mackinnon April 19, 2019

April 19, 2019

I noticed that recent Pharo 6.1 zero conf downloads show lots of these errors when you run the image in the terminal. Previous versions didnât do this - is this something to do with the latest vm upgrade? ./pharo-ui PagerDuty.image /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Common/ChunkCompression.cpp:50: Error: unsupported compressor 8 /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Libraries/CompressData/CompressData.c:353: Error: Unknown compression scheme encountered for file '/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/Exceptions.plist' /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Common/ChunkCompression.cpp:50: Error: unsupported compressor 8 /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Libraries/CompressData/CompressData.c:353: Error: Unknown compression scheme encountered for file '/System/Library/CoreServices/CoreTypes.bundle/Contents/Library/AppExceptions.bundle/Exceptions.plist' Tim

6 6

Pharo Downloads are sluggish
by Esteban Maringolo March 13, 2019

March 13, 2019

Is there a reason why the latest version of the builds linked from the website are not hosted in some CDN, Amazon S3 or similar? Maybe in Europe the speed is fast, but where I am (Argentina) it is really slow, the screenshot shows 3.5KB/s, it averages 10KB/s, with peaks of 40KB/s. This is an pitiful boarding experience, that will make many cancel it even before getting to open the downloaded launcher. [image: node-pharo.png] The screenshot shows that is not a problem with my home connection, which isn't the fastest but is "normal" for my use cases. Regards, Esteban A. Maringolo ps: When I finished writing this email, this was the progress... [image: image.png]

4 15

Pharo 7 RC - Changing to larger font breaks scrolling in code browsers
by Sven Van Caekenberghe Jan. 24, 2019

Jan. 24, 2019

Hi, Here is an annoying usability bug that I am experiencing and that sometimes drives me nuts. It has been there a while. Take a stock Pharo 7 RC image and don't change any setting. Browse the method #testAsDateAndTime as implemented by DateAndTimeTest. This is a (too) long (test) method. Any long method will do. You can scroll it fine in both the implementors and well as in the full browser. Now switch to 'Medium' sized 'predefined style' Standard Fonts using the Settings Browser. It is now close to impossible to scroll in the implementors or the full browser: not using the scroll bar arrows, not dragging the scroll bar, not clicking above/below the scroll bar, not using the scroll gesture (track pad, mouse pad, wheel), not using cursor keys inside the editor. Scrolling seems to happen automatically and goes on until the top or bottom. Can anyone replicate this ? Sven

2 2

Better management of encoding of environment variables
by Guillermo Polito Jan. 22, 2019

Jan. 22, 2019

Hi all, following the meeting we had here @Inria headquarters, I'll be backporting some of the improvements we did in the launcher this last month regarding the encoding of environment variables. I've opened for this issue https://pharo.fogbugz.com/f/cases/22658/ We have already studied possible alternatives with Pablo and Christophe and we have some conclusions and we propose some changes: API Proposal for OSEnvironment ========================= - *at: aVariableName * Gets the String value of an environment variable called `aVariableName` It is the system reponsibility to manage the encoding. Rationale: A common denominator for all platforms providing an already decoded string, because windows does not (compared to *nix systems) provide a encoded byte representation of the value. Windows has instead its own wide string representation. - *[optionally] rawAt: anEncodedVariableName* Gets the Byte value of an environment variable called `anEncodedVariableName`. It is the user responsibility to encode and decode argument and return values in the encoding of this preference. Rationale: Some systems may want to have the liberty to use different encodings, or even to put binary data in the variables. - *[optionally] at: aVariableName encoding: anEncoding* Gets the value of an environment variable called `aVariableName` using `anEncoding` to encode/decode arguments and return values. Rationale: *xes could potentially use different encodings for their environment variables or even use different encodings in different parts of their file system. Other Implementation details ========================= - VM primitives returning paths Strings should be carefuly managed to decode them, since they are actually C strings (so byte arrays) disguised as ByteStrings. - Windows requires calling the right *Wide version of the functions from C, plus the correct encoding routine. This could be implemented as an FFI call or by modifying the VM to do it properly instead of calling the Ascii version

9 23

Minheadless trial
by Ben Coman Dec. 5, 2018

Dec. 5, 2018

wow time flies, its been 18 months since Ronie announced his Minheadless VM branch... [1] http://forum.world.st/Minheadless-VM-flavour-status-update-td4928091.html I've been meaning this whole time to try it out. Recently in my meandering thoughts on FreeRTOS port, I guessed Minheadless might make a good starting basis to experiment with. So a quick test on Ubuntu16.04.3(Windows10-WSL)... Long ago I'd already done... git clone git@github.com:OpenSmalltalk/opensmalltalk-vm.git so I now did... cd opensmalltalk-vm git remote add ronie git@github.com:ronsaldo/opensmalltalk-vm.git git fetch ronie git checkout MinimalisticHeadless ./scripts/updateSCCSVersions cd build.minheadless.cmake/x64/pharo.stack.spur/ ./mvm VM=`pwd`/release/dist/pharo ls $VM ==> confirmed it exists cd ~/pharo wget http://files.pharo.org/image/70/latest-minimal-64.zip unzip latest-minimal-64.zip sudo $VM Pharo7.0-metacello-64bit-65cff7b.image eval "19 + 23" ==> 42 yay Particularly interesting from [1] is "using the same CMake scripts for building on the three platforms: Windows, Linux and OS X." So I thought I'd also give it a try under Windows10-VisualStudio2017. I hardly used VS before, so I'll detail what I did as a reminder for myself (and also in case someone might be able to help if I get stuck). Under a windows cmd.exe prompt (having installed git and cloned opensmalltalk-vm a long time ago) cd opensmalltalk-vm git remote add ronie git@github.com:ronsaldo/opensmalltalk-vm.git git fetch ronie git checkout -b MinimalisticHeadless ronie/MinimalisticHeadless I watched video [2] about CMake integration with Visual Studio 10. and checked the VS workloads configuration specified [2@1:13] using [3]. There is a CMakeLists.txt file in the git root folder, so.. started VS > File > Open > Folder... C:\Repos\OpenSmalltalk\opensmalltalk-vm The CMake command run ([2]@2:13) was... C:\...\cmake.exe -G "Ninja" -DCMAKE_INSTALL_PREFIX:PATH="C:\Users\Ben\CMakeBuilds\...\x86-Debug" -DCMAKE_CXX_COMPILER="C:/.../MSVC/14.14.26428/bin/HostX86/x86/cl.exe" -DCMAKE_C_COMPILER="C:/.../MSVC/14.14.26428/bin/HostX86/x86/cl.exe" -DCMAKE_BUILD_TYPE="Debug" -DCMAKE_MAKE_PROGRAM="C:\...\CMAKE\Ninja\ninja.exe" "C:\Repos\OpenSmalltalk\opensmalltalk-vm" I changed the cmake configuration [2@2:27] to "x64-Debug". For debug target [2@3:00] I chose "pharo.exe" Hey, thats pretty cool [2@4:05] that switching between targets changes the highlighting of #ifdef code. I had a moment when I was missing the "Debug and Launch Settings" menu item [2@4:40-4:55] and mentioned at [4], but maybe there was some clash with previously experimenting with git cloning opensmalltalk-vm from inside VS. After closing VS and reopening my cmd.exe git'd opensmalltalk-vm it showed up, but I didn't change any settings there. Then (with x64-Debug & pharo.exe selected) I went Cmake > Build All ==> 10 Errors, 9 Warnings, which I'll discuss in a followup post. cheers -ben [2] https://blogs.msdn.microsoft.com/vcblog/2016/10/05/cmake-support-in-visual-… [3] https://docs.microsoft.com/en-us/visualstudio/install/modify-visual-studio [4] https://blogs.msdn.microsoft.com/vcblog/2016/12/20/cmake-support-in-visual-… [5] https://developercommunity.visualstudio.com/content/problem/234808/cmake-de…

6 22

InterruptedContext vs suspendedContext
by Thomas Dupriez Dec. 4, 2018

Dec. 4, 2018

Hello, Instances of DebugSession have an "interruptedContext" and an "interruptedProcess" instance variable. Instances of Process have a "suspendedContext" instance variable. Does someone know if there is a relation between the interruptedContext of a DebugSession and the suspendedContext of its interruptedProcess? At first glance it seems like these two variables are redundant and store the same Context. Thomas Dupriez

3 3

Version control of Playground scripts
by Christopher Fuhrman Dec. 2, 2018

Dec. 2, 2018

Hello, In Pharo 6.1 I have got Iceberg working and love the interface to GitHub. Thanks to the Rmod folks for all the patient answers to my newbie questions. However, most of my development remains in playground scripts, and as far I understand, it's not possible to put them under version control with Iceberg. My scripts *could* be turned into classes eventually (some already have been and are under Iceberg). But it feels frustrating to rush it, just to get the versioning. I know how to save Playground files to the web, which is useful, but of course not version control per se. Knowing Playground files are saved on local disk, I got to thinking... What would be the risk(s) of using git outside Pharo, on the Playground files' directory? Has anyone tried that before? Cheers, Christopher

5 6

[Pharo 7.0-dev] Build #1429: 22679-Metacello-attributes-should-be-based-on-SystemVersion-instead-of-hardcoding
by ci-pharo-ci-jenkins2＠inria.fr Nov. 30, 2018

Nov. 30, 2018

There is a new Pharo build available! The status of the build #1429 was: FAILURE. The Pull Request #1999 was integrated: "22679-Metacello-attributes-should-be-based-on-SystemVersion-instead-of-hardcoding" Pull request url: https://github.com/pharo-project/pharo/pull/1999 Issue Url: https://pharo.fogbugz.com/f/cases/22679 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1428: 22679-Metacello-attributes-should-be-based-on-SystemVersion-instead-of-hardcoding
by ci-pharo-ci-jenkins2＠inria.fr Nov. 30, 2018

Nov. 30, 2018

There is a new Pharo build available! The status of the build #1428 was: FAILURE. The Pull Request #1999 was integrated: "22679-Metacello-attributes-should-be-based-on-SystemVersion-instead-of-hardcoding" Pull request url: https://github.com/pharo-project/pharo/pull/1999 Issue Url: https://pharo.fogbugz.com/f/cases/22679 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1427: 19927-scanFor-should-not-elide-extended-byte-codes
by ci-pharo-ci-jenkins2＠inria.fr Nov. 30, 2018

Nov. 30, 2018

There is a new Pharo build available! The status of the build #1427 was: SUCCESS. The Pull Request #1872 was integrated: "19927-scanFor-should-not-elide-extended-byte-codes" Pull request url: https://github.com/pharo-project/pharo/pull/1872 Issue Url: https://pharo.fogbugz.com/f/cases/19927 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1426: Fix the layout of Glamour tabulator rows and columns in the presence â¦
by ci-pharo-ci-jenkins2＠inria.fr Nov. 30, 2018

Nov. 30, 2018

There is a new Pharo build available! The status of the build #1426 was: SUCCESS. The Pull Request #2004 was integrated: "Fix the layout of Glamour tabulator rows and columns in the presence â¦" Pull request url: https://github.com/pharo-project/pharo/pull/2004 Issue Url: https://pharo.fogbugz.com/f/cases/fixLayout Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1425: 22712-speed-up-mustBeBooleanDeOptimizeIn-by-a-factor-of-200-by-caching
by ci-pharo-ci-jenkins2＠inria.fr Nov. 30, 2018

Nov. 30, 2018

There is a new Pharo build available! The status of the build #1425 was: SUCCESS. The Pull Request #2026 was integrated: "22712-speed-up-mustBeBooleanDeOptimizeIn-by-a-factor-of-200-by-caching" Pull request url: https://github.com/pharo-project/pharo/pull/2026 Issue Url: https://pharo.fogbugz.com/f/cases/22712 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] [Pharo-users] [Ann] TaskIt v1.0
by Santiago Bragagnolo Nov. 29, 2018

Nov. 29, 2018

Hi Norbert! We don't have yet implemented any nor all combinations. I will add it to the list of things to do for next release. Looks like a simple and useful thing to have. (Or if you have already something I wouldn't mind to integrate it) Thanks. Santiago El jue., 29 de nov. de 2018 17:36, Norbert Hartl via Pharo-users < pharo-users(a)lists.pharo.org> escribiÃ³: > Great, thanks! > > Does TaskIt include implementations for combining futures such as the ALL > and the ANY futures which resolve either when all or one future resolves? > From the documentation it looks that rather not. > > Norbert > > > Am 29.11.2018 um 15:29 schrieb Santiago Bragagnolo < > santiagobragagnolo(a)gmail.com>: > > Hi everybody :). > > I am happy to announce TaskIt v1.0. > > In this version we add some new features, passed over the red tests and > clean up some dead code. And did a pass in the documentation > > A bit from the DOC > Downloading > > Current stable version of taskit can be downloaded using metacello as > follows: > > Metacello new > baseline: 'TaskIt'; > repository: 'github://sbragagnolo/taskit'; > load. > > If you want a specific release such as v1.0, you can load the associated > tag as follows > > Metacello new > baseline: 'TaskIt'; > repository: 'github://sbragagnolo/taskit:v1.0'; > load. > > Otherwise, if you want the latest development version, take a look at the > development branchs and load the latest: > > Metacello new > baseline: 'TaskIt'; > repository: 'github://sbragagnolo/taskit:dev-1.1'; > load. > > > <https://github.com/sbragagnolo/taskit/blob/master/README.md#major-features>Major > Features > > - Actors (ActIt) > - Configuration Profiles > - Service > > > Check specially the configuration profiles. The default profile usage is > #development, which sets up the environment for debugging exceptions in a > process. > > I want to thank a lot to the contributors, Guillermo Polito Max Leske > and Daniel Sasu. > I want as well to thanks the users, specially to those that bring me > feedback (blames and ideas) in person (Esteban, Pablo) or through the > different channels (Holger Freyther, Juraj Kubelka, Philippe Back). > > > I want also to apologise the delay of my responses on the issue board :) > (Really, sorry). I am constantly using TaskIt in other projects, but much > times I cannot do it my priority. > > > thanks a lot, > > Santiago Bragagnolo. > > > > > > > > > > >

2 2

[Ann] TaskIt v1.0
by Santiago Bragagnolo Nov. 29, 2018

Nov. 29, 2018

Hi everybody :). I am happy to announce TaskIt v1.0. In this version we add some new features, passed over the red tests and clean up some dead code. And did a pass in the documentation A bit from the DOC Downloading Current stable version of taskit can be downloaded using metacello as follows: Metacello new baseline: 'TaskIt'; repository: 'github://sbragagnolo/taskit'; load. If you want a specific release such as v1.0, you can load the associated tag as follows Metacello new baseline: 'TaskIt'; repository: 'github://sbragagnolo/taskit:v1.0'; load. Otherwise, if you want the latest development version, take a look at the development branchs and load the latest: Metacello new baseline: 'TaskIt'; repository: 'github://sbragagnolo/taskit:dev-1.1'; load. <https://github.com/sbragagnolo/taskit/blob/master/README.md#major-features>Major Features - Actors (ActIt) - Configuration Profiles - Service Check specially the configuration profiles. The default profile usage is #development, which sets up the environment for debugging exceptions in a process. I want to thank a lot to the contributors, Guillermo Polito Max Leske and Daniel Sasu. I want as well to thanks the users, specially to those that bring me feedback (blames and ideas) in person (Esteban, Pablo) or through the different channels (Holger Freyther, Juraj Kubelka, Philippe Back). I want also to apologise the delay of my responses on the issue board :) (Really, sorry). I am constantly using TaskIt in other projects, but much times I cannot do it my priority. thanks a lot, Santiago Bragagnolo.

2 1

[Pharo 7.0-dev] Build #1424: 22711-Improve-Cursor-class-comment
by ci-pharo-ci-jenkins2＠inria.fr Nov. 29, 2018

Nov. 29, 2018

There is a new Pharo build available! The status of the build #1424 was: FAILURE. The Pull Request #2024 was integrated: "22711-Improve-Cursor-class-comment" Pull request url: https://github.com/pharo-project/pharo/pull/2024 Issue Url: https://pharo.fogbugz.com/f/cases/22711 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1423: 22568-ContextcompleteCallee-is-dead-code-new-pr
by ci-pharo-ci-jenkins2＠inria.fr Nov. 29, 2018

Nov. 29, 2018

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

1 0

[Pharo 7.0-dev] Build #1422: 22708 Tag ManifestRingChunkImporter and related classes
by ci-pharo-ci-jenkins2＠inria.fr Nov. 29, 2018

Nov. 29, 2018

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

1 0

[Pharo 7.0-dev] Build #1421: 22709 Tag ManifestRingCoreContainers and related classes
by ci-pharo-ci-jenkins2＠inria.fr Nov. 29, 2018

Nov. 29, 2018

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

1 0

[Pharo 7.0-dev] Build #1420: 22710 Tag ManifestDeprecatedFileStream and related classes
by ci-pharo-ci-jenkins2＠inria.fr Nov. 29, 2018

Nov. 29, 2018

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

1 0

Excel export with Tabular
by Hans-Martin Nov. 28, 2018

Nov. 28, 2018

Hello folks, I have a need for creating excel files with more than 3 worksheets, so I took the Tabular code and beefed up the exporter a little. It does handle more worksheets now, uses XMLWriter to create all the ZIP members, and is properly named now (the class was called TabularXSLXExport, note swapped S and L). Some tests have been added, there are a number of items that I plan to to as time allows: - Add (possibly limited) support for styles and formulas which I specifically need for the project I'm working on so I could write files with the desired layout and functionality. - Add support for reading more aspects of XLSX files, preferrably as much as needed to be able to read and write most files without loss. - Add rendering, maybe at the basic morphic level, maybe using something else as I'm not really up-to-date regarding the developments in Pharo. - Add formula evaluation. - Add editing capabilites to have a fully functional spreadsheet (really far off). Cheers, Hans-Martin -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

7 6

Preparing the 7.0 release (and 8.0 open), we will need to rename "development" branch to "dev-7.0"
by Esteban Lorenzano Nov. 28, 2018

Nov. 28, 2018

Hi list, Well, subject says pretty much all. We are planning to release Pharo 7.0 very soon now, and while preparing the release process, we came to the conclusion that we will need a branch for version to develop, and because of that we will need to rename what is not âdevelopmentâ to âdev-7.0â. Then, it will be a âdev-8.0â and so onâ¦ So, be prepared to submit your PRs to dev-7.0 instead development :) Cheers, Esteban

4 11

[Pharo 7.0-dev] Build #1419: 22702-support-before-after-intead-on-RBCascadeNode
by ci-pharo-ci-jenkins2＠inria.fr Nov. 28, 2018

Nov. 28, 2018

There is a new Pharo build available! The status of the build #1419 was: SUCCESS. The Pull Request #2018 was integrated: "22702-support-before-after-intead-on-RBCascadeNode" Pull request url: https://github.com/pharo-project/pharo/pull/2018 Issue Url: https://pharo.fogbugz.com/f/cases/22702 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1418: 22700-add-value-and-operation-for-Blocks
by ci-pharo-ci-jenkins2＠inria.fr Nov. 27, 2018

Nov. 27, 2018

There is a new Pharo build available! The status of the build #1418 was: SUCCESS. The Pull Request #2017 was integrated: "22700-add-value-and-operation-for-Blocks" Pull request url: https://github.com/pharo-project/pharo/pull/2017 Issue Url: https://pharo.fogbugz.com/f/cases/22700 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1417: 22697-remove-oldvalue-reification
by ci-pharo-ci-jenkins2＠inria.fr Nov. 27, 2018

Nov. 27, 2018

There is a new Pharo build available! The status of the build #1417 was: FAILURE. The Pull Request #2014 was integrated: "22697-remove-oldvalue-reification" Pull request url: https://github.com/pharo-project/pharo/pull/2014 Issue Url: https://pharo.fogbugz.com/f/cases/22697 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1416: 22640-Sending-links-to-an-AST-should-not-return-nil-if-there-is-no-link
by ci-pharo-ci-jenkins2＠inria.fr Nov. 27, 2018

Nov. 27, 2018

There is a new Pharo build available! The status of the build #1416 was: FAILURE. The Pull Request #2013 was integrated: "22640-Sending-links-to-an-AST-should-not-return-nil-if-there-is-no-link" Pull request url: https://github.com/pharo-project/pharo/pull/2013 Issue Url: https://pharo.fogbugz.com/f/cases/22640 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1415: 22695-Make-value-for-work-method-after
by ci-pharo-ci-jenkins2＠inria.fr Nov. 27, 2018

Nov. 27, 2018

There is a new Pharo build available! The status of the build #1415 was: FAILURE. The Pull Request #2012 was integrated: "22695-Make-value-for-work-method-after" Pull request url: https://github.com/pharo-project/pharo/pull/2012 Issue Url: https://pharo.fogbugz.com/f/cases/22695 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

halos
by Stephan Eggermont Nov. 26, 2018

Nov. 26, 2018

What happened with halos in Pharo 7? They donât show up anymore Stephan

2 4

Fuel update for UTCDateAndTime
by David T. Lewis Nov. 26, 2018

Nov. 26, 2018

The Fuel serializer is loadable in Squeak 5.2 from the SqueakMap loader, and is supported for Pharo, Squeak, and Cuis (great kudos to the maintainers for doing this). In order to change DateAndTime to a simpler UTC-based implementation in Squeak, with two instance variables rather than four, an update will be needed for Fuel to understand the new format. The attached change set provides the necessary support, while maintaining compatibility with the traditional DateAndTime and interoperability between images that support either format. For example, an image can serialize a traditional DateAndTime with Fuel, and another image with UTC DateAndTime can materialize it in the new UTC format. I am not yet sure how to submit this to the Fuel maintainers, so I'm posting it here as a change set for now. Dave

2 1

[Pharo 7.0-dev] Build #1414: 22690-32-vs-64-bits-and-large-integer-hash
by ci-pharo-ci-jenkins2＠inria.fr Nov. 26, 2018

Nov. 26, 2018

There is a new Pharo build available! The status of the build #1414 was: FAILURE. The Pull Request #2009 was integrated: "22690-32-vs-64-bits-and-large-integer-hash" Pull request url: https://github.com/pharo-project/pharo/pull/2009 Issue Url: https://pharo.fogbugz.com/f/cases/22690 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Esteban's ChangeLog week of 19 November 2018
by estebanlm＠gmail.com Nov. 26, 2018

Nov. 26, 2018

Hello! This is my weekly ChangeLog, from 19 November 2018 to 25 November 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=19/11/2018&to=25/11/2018 ChangeLog ========= 22 November 2018: ----------------- * I made a change in the VM to modify [freetype version to 2.9.1](https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/307). We have the suspicion that some bugs we are finding in our use of freetype fonts may be already fixed on newer versions of freetype library (we were using 2.6.5). And well, if that is not the case, at least we will be up-to-date :) 19 November 2018: ----------------- * I made a [PR](https://github.com/pharo-project/pharo/pull/2002) to improve the logic in callbacks. They were not returning in case of error, and that was leading to a system crash almost inevitably. cheers! Esteban

1 0

Re: [Pharo-dev] [squeak-dev] 32 vs 64 bits and large integer hash
by Eliot Miranda Nov. 25, 2018

Nov. 25, 2018

On Sat, Nov 24, 2018 at 7:40 AM Luciano Notarfrancesco <luchiano(a)gmail.com> wrote: > On Fri, Nov 23, 2018 at 12:36 AM Chris Muller <asqueaker(a)gmail.com> wrote: > >> > >> I'm a bit puzzled. I thought (small)Integers being their own hash >> is a good thing? >> >> I was wondering exactly the same thing! >> >> > > I would call it simple but not necessarily good. >> > > The problem with it is that consecutive numbers generate long chains >> in HashedCollections: >> > > >> > > a := (1 to: 1000) asArray. >> > > s := Set withAll: a. >> > > [ 1 to: 1000000 do: [ :each | s includes: each ] ] timeToRun. >> > > "==> 7014" >> > > >> > > The solution in Squeak is to use PluggableSet instead of Set, because >> it applies #hashMultiply on the hash value: >> > > >> > > ps := PluggableSet integerSet. >> > > ps addAll: a. >> > > [ 1 to: 1000000 do: [ :each | ps includes: each ] ] timeToRun. >> > > "==> 95" >> > > >> > > IIRC in Pharo SmallInteger's hash is based on #hashMultiply to avoid >> the long chains. That was probably the main reason for the push to make >> #hashMultply a numbered primitive. >> > > >> > >> > Interesting! >> >> Indeed! When making a #hash methods, one always focuses on hash >> distribution and finding the elements, but its easy to forget about >> performance of NOT finding an element. >> >> > Yes! I had this problem blow in my face a couple of years ago, and Juan > agreed to include the change in Cuis to make SmallIntegers NOT their own > hash. > This seems to be a basic error. The idea of a hash function is to produce a well-distributed set of integers for some set of values. Since the SmallIntegers are themselves perfectly distributed (each unique SmallInteger is a unique value), it is impossible to produce a better distributed hash function than the integers themselves. For some application it may indeed be possible to produce a better distributed set of hashes for the integers; for example an application which considers only powers of two could use the log base 2 to produce a smaller and better distributed set fo values modulo N than the integers themselves. But in general the integers are definitionally well-distributed. In fact, unless one has a perfect hash function one is in danger of producing a less well-distributed set of values from a hash function than the SmallIntegers themselves. This argument doesn't apply as integers grow beyond the SmallInteger, but not because we want better distribution of values than the large integers themselves, but b because we want to avoid large integer arithmetic. > I think it is a good idea in general when programming a hash method in > Smalltalk to make it somewhat random. > As I've indicated, I think this is impossible in general. It is only in specific applications, using specific subsets of the SmallIn tigers for which a better hash function could be derived, but this would be specific to that application. For purposes such as these we have PluggableDictionary et al which can exploit an application-specific hash. But in general the SmallIntegers are ideal values for their own hashes. > It will never be perfect for every use case, and it doesn't need to be > cryptographically secure, but there shouldn't be simple use cases (e.g., > consecutive integers) that produce hashes that are not uniformly > distributed. This can be achieved with minimal performance impact (and > potentially big performance gains in hashed collections) quite simply by > sending some hashMultiply message in your hash method. > > Regards, > Luciano > _,,,^..^,,,_ best, Eliot

2 1

[ANN] Live type information for Smalltalk
by Hernan Wilkinson Nov. 24, 2018

Nov. 24, 2018

Hi all!, I wanted to let you know that I have implemented a "feature" to have type information "live". Currently it is implemented on Cuis but the idea is to port it to Pharo and Squeak as well. This feature is based on a few changes on the VM that collects the class of the object assigned to a variable, a parameter or when returning from a method. That information is available from the image and allows to improve the tools radically, like the autocompletion on the browser, looking for senders/implementors and even "scoping" the refactorings based on the type info. I presented it at the last Smalltalks (the argentinean smalltalk conference) and I'm happy to announce its alpha version (1/1000) asFloat :-) Here is a link to the repo that has the VM and a Cuis image to play with it: https://github.com/hernanwilkinson/Cuis-Smalltalk-DynamicTypeInformation It also has the source of the VM's changes if you want to see how it is implemented. Currently it is implemented only in the stack VM and the VMs I compiled and uploaded to the repo are 64 bits for MacOs and Linux. (I don't have a Windows machine to compile it :-) ) Here is a link to a video that shows how it is implemented and how to use it: https://t.co/n8FQuo7pKZ If you want to see the slides of the presentation, here is the link: https://www.slideshare.net/hernanwilkinson/dynamic-type-information I would love for you to try it and get feedback, ideas, etc. I really believe it is a "killer feature", something that could take Smalltalk one step further and show the way to other dynamically typed languages. Cheers! Hernan -- *HernÃ¡n WilkinsonAgile Software Development, Teaching & Coaching* *Phone: +54 - 011 - *6091 - 3125 *Mobile: +54 - 911 - 4470 - 7207email: hernan.wilkinson(a)10Pines.comsite: http://www.10Pines.com <http://www.10pines.com/>* Address: Alem 693, Floor 5 B, Buenos Aires, Argentina

1 0

[Pharo 7.0-dev] Build #1413: 22686-Open-browser-fails-without-sources-file-
by ci-pharo-ci-jenkins2＠inria.fr Nov. 23, 2018

Nov. 23, 2018

There is a new Pharo build available! The status of the build #1413 was: SUCCESS. The Pull Request #2008 was integrated: "22686-Open-browser-fails-without-sources-file-" Pull request url: https://github.com/pharo-project/pharo/pull/2008 Issue Url: https://pharo.fogbugz.com/f/cases/22686 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1412: 22692-Improve-after-operation-for-Array
by ci-pharo-ci-jenkins2＠inria.fr Nov. 23, 2018

Nov. 23, 2018

There is a new Pharo build available! The status of the build #1412 was: FAILURE. The Pull Request #2011 was integrated: "22692-Improve-after-operation-for-Array" Pull request url: https://github.com/pharo-project/pharo/pull/2011 Issue Url: https://pharo.fogbugz.com/f/cases/22692 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Next Pharo Sprint: Nov 30
by Marcus Denker Nov. 23, 2018

Nov. 23, 2018

We will organize a Pharo sprint / Moose dojo Nov 30, starting at 10:00am. (Local Time Paris). Goals of this sprint: â¢ Pharo 7 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 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 https://association.pharo.org/event-2973626

1 0

Re: [Pharo-dev] [squeakland] strategies and tools for a comeback of Smalltalk using Scratch as entrance
by Bernhard HÃ¶fner Nov. 23, 2018

Nov. 23, 2018

Hello Tim and the group thank you for your reply. It is very good to hear, that it is effort in the Smalltalk Scratch, especially when it has such good results. By the way: can I see it as the new Smalltalk Scratch version also for other platforms than Raspberry Pi? I ask, because also other Smalltalk based implementations could profit from it, for example the ipad-version Pyonkee or the Version with Smalltalk-code-view Phratch. Speed would be a matter when programming serious Apps for tablets or smartphones. By using all its sensors children could make nice tools with it and they experiment not only with Software but with the real world objects (which also brings them closer to Smalltalks object orientation). But this detaches me from my real concern: how is it possible to bundle all the initiatives and power to have realized such a continuous Scratch / Smalltalk tool, that I tried to describe with my Topic. Unfortunately nobody answered on my question if such a tool is welcome. Maybe I am the only one with that vision. Best Regards, Bernhard I just replied in the squeak-list, that I shift the discussion to pharo list. I wrote there: â...Because there is no discussion started about my underlying question, I try to continue it on pharo list. I think, many of the participants in squeak list are also participants there. Further I think, that scratch could be a good starting point Tobias mentioned the https://programmieren.wdrmaus.de <https://programmieren.wdrmaus.de/> project which again shows that Scratch is spread and willingly used. Maybe it is not such important, which porting is used as long the "project" code is interchangeable, which means that the Smalltalk-based implementation should be maintained and always be up to date. I dont know if someone takes care about that." > Am 03.11.2018 um 04:27 schrieb tim Rowledge <tim(a)rowledge.org>: > > > >> On 2018-11-02, at 3:22 PM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> >> Hi Tim >> >> I think you do not read the Pharo list. > > This is true. Only so much time in one life... > >> >> Below post from somebody who is not aware that you ported Scratch to >> the freshly release Squeak 5.2 easily loadable through SqueakMap.... > > Hi Bernhard - I spent some time working for the Raspberry Pi Foundation to significantly rewrite the original Scratch/Squeak implementation so it would perform well on the Pi (back then of course the original Pi with the single core 700MHz cpu) and I was able to make it really quite a lot faster. I also made it possible to run on a modern version of Squeak and indeed it currently runs on Squeak 5.2 - which makes it *very* nice on a Pi3B+. > > You can find it on SqueakMap as 'nuscratch' along with the gpio server and gpio driver libraries I developed. You might also be interested in the 'Whiskers' project by someone I only know as 'NoMod'; google is your friend in this case. They developed some further extensions to read .sb2 files, change the UI to closely match that of Scratch 2 (which as you likely know was a rewrite by MIT in *Flash*, of all horrible things) and add some new blocks. > > > tim > -- > tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim > Strange OpCodes: CBA: Compare if Biorhythms Amenable > >

1 0

Zinc HTTP Components version 3.0.1
by Sven Van Caekenberghe Nov. 22, 2018

Nov. 22, 2018

I finally merged and synced all Zinc HTTP Components repos and did a full release on Pharo versions 3 to 7. https://github.com/svenvc/zinc/releases/tag/v3.0.1 Main README was updated https://github.com/svenvc/zinc Green build for Pharo 7 RC1 (linux 64-bit) using BaselineOfZincHTTPComponents https://travis-ci.org/svenvc/zinc Green builds for Pharo 3, 4, 5 and 6 using ConfigurationOfZincHTTPComponents (#stable 3.0.1) https://ci.inria.fr/pharo-contribution/job/ZincHTTPComponents/ If there are any problems or issues, don't hesitate to ask. Sven

2 1

32 vs 64 bits and large integer hash
by Eliot Miranda Nov. 22, 2018

Nov. 22, 2018

Hi All, right now we have the following definition of Large(Positive)Integer>>hash: hash ^ByteArray hashBytes: self startingWith: self species hash which means that for all integers outside of the 32-bit SmallInteger range (-2 ^ 30 to 2 ^ 30 - 1), the 32-bit system and the 64-bit system answer different values for hash. e.g. in 64 bits: (2 raisedTo: 30) hash 1073741824 but in 32 bits: (2 raisedTo: 30) hash 230045764 This is unsatisfactory. I propose changing Large(Positive)Integer>>hash to hash ^self digitLength <= 8 ifTrue: [self] ifFalse: [ByteArray hashBytes: self startingWith: self species hash] P.S. Note that this will not break Float hash, which is defined as Float>>hash "Hash is reimplemented because = is implemented. Both words of the float are used. (The bitShift:'s ensure that the intermediate results do not become a large integer.) Care is taken to answer same hash as an equal Integer." (self isFinite and: [self fractionPart = 0.0]) ifTrue: [^self truncated hash]. ^ ((self basicAt: 1) bitShift: -4) + ((self basicAt: 2) bitShift: -4) P.P.S. I *think* that "(self isFinite and: [self fractionPart = 0.0])" is equivalent to "self - self = self fractionPart" ;-) _,,,^..^,,,_ best, Eliot

2 2

ZnCharacterReadWriteStream is missing #tab
by Torsten Bergmann Nov. 22, 2018

Nov. 22, 2018

Hi Sven, in latest P7 I get an error when loading my Bootstrap 4 project: https://github.com/astares/Seaside-Bootstrap4 about MessageNotUnderstood: ZnCharacterReadWriteStream>>tab This is sent from STONWriter>>newlineIndent. To reproduce please use the following load expression: Metacello new baseline:'Bootstrap4'; repository: 'github://astares/Seaside-Bootstrap4:master/src'; load If the missing method in ZnCharacterReadWriteStream is implemented like tab writeStream tab it works. As I'm constantly unclear about how Zinc (and some other externally maintained packages) are managed now I would kindly ask you to integrate it. Thanks in advance! Bye T.

2 1

Re: [Pharo-dev] [squeak-dev] Message>>#= & Message>>#hash
by Chris Muller Nov. 22, 2018

Nov. 22, 2018

> That's "one should not rename classes and expect things to work", isn't > it? Not really, since that is already true anyway. If you rename a class, all references to that class will be broken.

1 0

Re: [Pharo-dev] [squeak-dev] Message>>#= & Message>>#hash
by Chris Muller Nov. 22, 2018

Nov. 22, 2018

Hi Levente, > >> My questions related to this: > >> - why does Behavior >> #hash rely on the name instead of identity? > > > > If you mean #identityHash, then its because involving an unstable > > value in a #hash calculation is never a good idea. #identityHash can > > be different for the same class between two different images, or if > > the class was ever becomed or reloaded into a new image, etc. > > Is there an actual user of that feature? Several actually. If your primary motivation is improving performance then we could cache the hash value, possibly even straight in the CompiledMethod itself (hard-coded). But we _must not_ destroy stable and deterministic hashes. It would be a huge blow to existing users and even future potential possibilities of future implementations of things. Anything that would try to share #hash calculations between images... Possibly Croquet. It's easy to imagine some things! MagmaDictionary is just a Dictionary except the internal array grows on disk providing size scalability while sparing RAM. The #hash of the objects put into it are calculated by the clients -- it must be consistent between users. source.squeak.org uses a MagmaDictionary for the revision history. It was the best way to introduce the capability without invading Monticello's code at all. > Bob found out that #hash had been changed during the developement of > Squeak 3.9. Therefore this issue is not present in Cuis (forked from 3.7). > And I just checked Pharo and found that Behavior >> #hash had been removed > from there. I think that's a big mistake. There's no need for us to cross the line of a stable hash to a volatile one. We can cache it.

1 0

Fwd: 32 vs 64 bits and large integer hash
by Sean P. DeNigris Nov. 22, 2018

Nov. 22, 2018

>From Squeak-Dev, seems to be an issue on Pharo as well... Eliot Miranda-2 wrote > Hi All, > > right now we have the following definition of > Large(Positive)Integer>>hash: > > hash > ^ByteArray hashBytes: self startingWith: self species hash > > which means that for all integers outside of the 32-bit SmallInteger range > (-2 ^ 30 to 2 ^ 30 - 1), the 32-bit system and the 64-bit system answer > different values for hash. > > e.g. in 64 bits: (2 raisedTo: 30) hash 1073741824 > but in 32 bits: (2 raisedTo: 30) hash 230045764 > > This is unsatisfactory. I propose changing Large(Positive)Integer>>hash > to > > hash > ^self digitLength <= 8 > ifTrue: [self] > ifFalse: [ByteArray hashBytes: self startingWith: self species hash] > > > P.S. Note that this will not break Float hash, which is defined as > > Float>>hash > "Hash is reimplemented because = is implemented. Both words of the float > are used. (The bitShift:'s ensure that the intermediate results do not > become a large integer.) Care is taken to answer same hash as an equal > Integer." > > (self isFinite and: [self fractionPart = 0.0]) ifTrue: [^self truncated > hash]. > ^ ((self basicAt: 1) bitShift: -4) + > ((self basicAt: 2) bitShift: -4) > > P.P.S. I *think* that "(self isFinite and: [self fractionPart = 0.0])" is > equivalent to "self - self = self fractionPart" ;-) > > _,,,^..^,,,_ > best, Eliot ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

1 0

[Pharo 7.0-dev] Build #1411: 22689-support-reification-value-and-operation-on-LiteralArray
by ci-pharo-ci-jenkins2＠inria.fr Nov. 21, 2018

Nov. 21, 2018

There is a new Pharo build available! The status of the build #1411 was: SUCCESS. The Pull Request #2007 was integrated: "22689-support-reification-value-and-operation-on-LiteralArray" Pull request url: https://github.com/pharo-project/pharo/pull/2007 Issue Url: https://pharo.fogbugz.com/f/cases/22689 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1410: 22678-Update-calypso-to-v0130
by ci-pharo-ci-jenkins2＠inria.fr Nov. 21, 2018

Nov. 21, 2018

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

1 0

glamorous toolkit alpha.3
by Tudor Girba Nov. 21, 2018

Nov. 21, 2018

Hi, Another month has swooshed and now itâs time for Glamorous Toolkit alpha.3: https://feenk.com/gt The key things that changed are as follows: - We rewrote Documenter. This was challenge, but the results are more than worth it. One visible thing is that now the previews get cached, and as a consequence we can actually work inside the document. But, perhaps the more impactful thing is that we can now toggle the visibility of Pillar markup. We think it significantly improves the experience and consequently, the value of the live documents. - We advanced the work on the method Coder. To explore the boundaries, we reimagined the extract method refactoring. Thatâs : https://twitter.com/feenkcom/status/1064823381407748096 - We enhanced the navigation in Playground / Inspector: https://twitter.com/feenkcom/status/1064823381407748096 A more complete list of issues we addressed is found here: https://github.com/feenkcom/gtoolkit/milestone/1?closed=1 Have fun, The feenk team -- www.feenk.com âHow do you feenk today?"

3 2

Re: [Pharo-dev] [squeak-dev] Message>>#= & Message>>#hash
by Chris Muller Nov. 21, 2018

Nov. 21, 2018

> To make things more clear, the current implementation of Behavior >> #hash > has two negative side effects: > - behaviors stored in collections relying on the hash value (e.g. Set, > Dictionary) will have to be rehashed whenever a behavior is renamed > - objects using Behavior >> #hash to implement their own #hash, like what > Eliot just did to Message will suffer from the same issue. So Sets and > Dictionaries holding those kind of objects will have to be rehashed as > well upon the rename of the behavior. > > My questions related to this: > - why does Behavior >> #hash rely on the name instead of identity? If you mean #identityHash, then its because involving an unstable value in a #hash calculation is never a good idea. #identityHash can be different for the same class between two different images, or if the class was ever becomed or reloaded into a new image, etc. > - do we want to fix those issues mentioned above or do we just say that > one should not rename classes and expect things to work? Neither. We just say that when one renames a class to rehash all relevant HashedCollections. - Chris

1 0

Re: [Pharo-dev] [Cuis-dev] Message>>#= & Message>>#hash
by Eliot Miranda Nov. 20, 2018

Nov. 20, 2018

Hi Juan, On Tue, Nov 20, 2018 at 8:00 AM Juan Vuletich <juan(a)jvuletich.org> wrote: > Hi Eliot, > > (below) > On 19/11/2018 02:32 p.m., Eliot Miranda via Cuis-dev wrote: > > Hi All, > > In VisualWorks Message implements #= & #hash naturally; two messages > whose selectors and arguments are #= are also equal. But in Cuis, Squeak > and Pharo Message inherits #= and #hash from Object, i.e. uses identity > comparison. This is, to say the least, annoying. Any objections to > implementing comparing in Message to match VisualWorks? > > _,,,^..^,,,_ > best, Eliot > > > Just added these implementations to Cuis: > > = aMessage > "Any object is equal to itself" > self == aMessage ifTrue: [ ^ true ]. > self class == aMessage class ifFalse: [ ^false ]. > selector = aMessage selector ifFalse: [ ^false ]. > lookupClass = aMessage lookupClass ifFalse: [ ^false ]. > ^args = aMessage arguments > this last line should be ^args literalEqual: aMessage arguments and this is very important :-) > > hash > "Hash is reimplemented because = is implemented." > ^selector hash bitXor: args hash > > Do they look ok? (I considered lookupClass for #=, but not for hash, as > collisions because of that seem unlikely, and in any case, grouping them > that way could be useful). > > Cheers, > > -- > Juan Vuletichwww.cuis-smalltalk.orghttps://github.com/Cuis-Smalltalk/Cuis-Smallt… > @JuanVuletich > > -- _,,,^..^,,,_ best, Eliot

1 0