April 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Why no collect:ifNone: ?
by Tim Mackinnon May 2, 2018

May 2, 2018

Yep - as I was reading the replies from you and Esteban - I was thinking there was something odd, and its correct, Iâve been careless - the problematic code had a trailing #sum to it, which is actually where the problem wasâ¦. total := schedule ifEmpty: [ 0 ] ifNotEmpty: [ :c | (c collect: [ :r | ((DateAndTime fromString: r end) - (DateAndTime fromString: r start)) asHours ]) sum ]. So you are both correct - it should have used inject. total := schedule inject: 0 into: [ :result :item | result + ((DateAndTime fromString: item end) - (DateAndTime fromString: item start)) asHours ]. Oops - thanks for being my sound board. Tim > On 30 Apr 2018, at 22:02, Francisco Garau <francisco.garau(a)gmail.com> wrote: > > > Have you tried #inject:into: ? Looks like what are needing here > > - Francisco > > >> On 30 Apr 2018, at 19:37, Tim Mackinnon <tim(a)testit.works> wrote: >> >> >> Hi - I hit a small bug in my lunch experiments with Willow where I wanted to sum up a collection of support hours. >> >> I was collect: in the hours worked and hadnât accounted for an empty collection. >> >> When I went to do it I was surprised there isnât a concept of #collect:ifNone: that mirrors something like at:ifAbsent: or the nicely readable collect:thenXxx: methods. >> >> Why is this? >> >> Iâm curious about style - and the elegance of my workaround : >> >> result ifEmpty: [ 0 ] ifNotEmpty:[ :r | r collect: [:I | i hours ]] >> >> which is ok, but seems a mouthful? >> >> Am I missing a trick? >> >> Tim >> >> Sent from my iPhone >>

1 1

Why no collect:ifNone: ?
by Tim Mackinnon April 30, 2018

April 30, 2018

Hi - I hit a small bug in my lunch experiments with Willow where I wanted to sum up a collection of support hours. I was collect: in the hours worked and hadnât accounted for an empty collection. When I went to do it I was surprised there isnât a concept of #collect:ifNone: that mirrors something like at:ifAbsent: or the nicely readable collect:thenXxx: methods. Why is this? Iâm curious about style - and the elegance of my workaround : result ifEmpty: [ 0 ] ifNotEmpty:[ :r | r collect: [:I | i hours ]] which is ok, but seems a mouthful? Am I missing a trick? Tim Sent from my iPhone

2 1

Smalltalk-76 Demo
by Bernardo Ezequiel Contreras April 29, 2018

April 29, 2018

https://youtu.be/NqKyHEJe9_w -- Bernardo E.C. Sent from a cheap desktop computer in South America.

2 1

Re: [Pharo-users] Literals (Richard Sargent)
by Debiller 777 April 29, 2018

April 29, 2018

Well, set idea was just a small proposal, which had to help me in solving a harder problem. I wanted to add something like extensionable literal. The idea is that when compiler sees some special literal, it reads it, turns into an object and sends #parse message to it. After that literal answers something which compiler uses and considers as a result of this literal. Example: `#{1 2 3}` So compiler sees that literal initializes with it and object. Then object receives #parse message. It easily defines that its contents is set ctration and after parsing returns set object. This idea is my original intention. I hope its better than previous.

1 0

Literals
by Debiller 777 April 29, 2018

April 29, 2018

You know, literals are quite useful in case when you want to shorten some object initialization. For example #() and {} for arrays and $[]for byte arrays. However, if there is a way to add custom literals, for example for sets (something like #{} I guess)? how to do it? and can some special kind of objects for creating literals easily be added to Pharo?

10 15

Re: [Pharo-users] Literals (Richard O'Keefe)
by Debiller 777 April 28, 2018

April 28, 2018

Can you please tell more about ##() thing?

1 0

[Ann] Iceberg 0.7.4
by Guillermo Polito April 28, 2018

April 28, 2018

Hi all, Time for the weekly Iceberg update. The next pharo build will include Iceberg 0.7.4, with many improvements done during this last week. Documentation wise, all documentation/workflow valid for 0.7.3 is still valid for 0.7.4. Thanks to all brave users, issue reporters and contributors :). Key changes: - Several improvements in merging (mostly UI) - Optimize Pharo workflow (less fetches and unnecessary diffs) - Lots of new automated tests to cover merging, reverting and some git interactions that are difficult to capture manually Infrastructure changes: - Since 0.7.2 was released, we made the resolution of making an enhancement in the infrastructure per release - In 0.7.3 we fixed travis CI so builds are run on every commit and on pull requests - In this relese (0.7.4) we introduced in the build tests againt pharo 6.1 and 64 bits * The idea is to prepare the field for a future backport to Pharo 6.1 * And have good 64 bit support * https://travis-ci.org/pharo-vcs/iceberg/builds/372408795 In the next version our idea is to put the focus on enhancing - metacello integration - Pharo6.1 compatibility working smoothly - add a couple of more videos on scenarios like: * how to upgrade and contribute to iceberg * how to review a pharo fix * how to reuse your image for other fixes * handling merges * how to update a fork Here is the detailed changelog with all closed issues during this week: #729 Update .travis.yml to test Pharo 6 and 64 bits #689 Creating a repository in an existing location shows a debugger UI enhancement #556 Removed packages are not removed from git Model bug #727 Adapt properties reading of Tonel projects for Pharo 6.1. #728 Ask confirmation on fetch all action #543 In merge window removed methods are not taken into account Model bug #695 Specifying that Clone GitHub repository only deals with ssh mode Github plugin UI #690 Revert all does not behave correctly in detached working copy Model bug important #720 Commit panel should be selected by default when opening the commit window UI enhancement #724 Change focus order of commit window UI enhancement #719 Typing just after entering commit windows throw an error UI bug #721 Repository creation error not handled Github plugin bug #722 Typo in email git properties Libgit bug #716 "#pathString was sent to nil" if Pharo repository is not resolved Metacello Integration bug important #709 Cannot see the arrow in merge view #701 Merge view shows extra things UI enhancement merge #710 Merge does not apply changes right bug merge #711 The merge lose some changes bug merge #694 Extra diffs happen Model enhancement important #705 Clone repair action does extra actions Model enhancement #647 Following script for Pharo6.1 leads to unusable Iceberg (>>#binaryWriteStream) Pharo6-backport bug important Enjoy, Guille

1 0

[Voyage] Possible to save an OrderedCollection?
by sergio ruiz April 27, 2018

April 27, 2018

For some reason, I am not able to do this: Object subclass: #TestBox instanceVariableNames: 'origin corner pointList' classVariableNames: '' poolDictionaries: '' category: 'PrintBot-Modelsâ! initialize pointList := OrderedCollection new. If i do something like below, I donât see the list of points ever show up in mongo.. Ideas? b := TestBox new. b save. p1 := Point x:0 y:0. p1 save. p2 := Point x:12 y:343. p2 save. b origin: p1. b corner: p2. b save. b pointList add: p1. b save. b pointList add: p2. b save. ---- peace, sergio photographer, journalist, visionary Public Key:Â http://bit.ly/29z9fG0 #BitMessageÂ BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.codeandmusic.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

2 4

SortedCollection>>reverse answers an inconsistent object in Pharo 6
by Richard O'Keefe April 27, 2018

April 27, 2018

Test case: #(1 2 4) asSortedCollection reverse add: 3; yourself <print it> The answer *should* be aSortedCollection(4 3 2 1) but *is* aSortedCollection(4 2 1 3). This works in Squeak. The problem is that SortedCollection does not define #reverse[d] but simply inherits it(them), and the inherited code pays no attention to the sortBlock. I propose adding the following two methods to SortedCollection: reverseInPlace |a z| a := firstIndex. z := lastIndex. [a < z] whileTrue: [array swap: a with: z. a := a + 1. z := z - 1]. sortBlock := sortBlock ifNil: [[:x :y | y <= x]] ifNotNil: [[:x :y | sortBlock value: y value: x]]. ^self reversed ^self copy reverseInPlace The ANSI method is #reverse, not #reversed, but Pharo defines #reverse to call #reversed, and OrderedCollection overrides #reversed, so SortedCollection *must* override #reversed. #reverseInPlace is the name Squeak uses for the other method. It also has a definition in SequenceableCollection, which is not but is equivalent to reverseInPlace |a z| a := 1. z := self size. [a < z] whileTrue: [self swap: a with: z. a := a + 1. z := z - 1].l ^self r

3 12

UFFI - Could not coerce arguments
by Serge Stinckwich April 27, 2018

April 27, 2018

I would like to pass a pointer to an array of pointers to a FFI call and I have problems ... âI have this method: runOutputs: aTF_OutputArray size: anInteger | status outvalues | status := TF_Status create. outvalues := FFIExternalArray externalNewType: 'TF_Tensor*' size: anInteger. self library runSession: self options: FFIExternalObject null inputs: FFIExternalObject null values: FFIExternalObject null count: 0 outputs: aTF_OutputArray getHandle values: outvalues getHandle count: anInteger targets: FFIExternalObject null count: 0 metadata: FFIExternalObject null status: status. status check. ^ outvalues âthe FFI call is like that : runSession: aTF_Session options: opsTF_Buffer inputs: inTF_OutputArray values: inTF_TensorArray count: inCount outputs: outTF_OutputArray values: outTF_TensorArrayPtr count: outCount targets: aTF_OperationArray count: targetCount metadata: metaTF_Buffer status: aTF_Status "F_CAPI_EXPORT extern void TF_SessionRun( TF_Session* session, // RunOptions const TF_Buffer* run_options, // Input tensors const TF_Output* inputs, TF_Tensor* const* input_values, int ninputs, // Output tensors const TF_Output* outputs, TF_Tensor** output_values, int noutputs, // Target operations const TF_Operation* const* target_opers, int ntargets, // RunMetadata TF_Buffer* run_metadata, // Output status TF_Status*);" ^ self ffiCall: #(void TF_SessionRun #(TF_Session * aTF_Session, TF_Buffer * opsTF_Buffer, TF_Output * inTF_OutputArray, TF_Tensor * inTF_TensorArray, int inCount, TF_Output * outTF_OutputArray, TF_Tensor * outTF_TensorArrayPtr, int outCount, TF_Operation * aTF_OperationArray, int targetCount, TF_Buffer * metaTF_Buffer, TF_Status * aTF_Status)) module: TensorFlowCAPI TF_Tensor is an opaque object. I have an error: "Could not coerce arguments". I guess this is related to the way I pass arguments to the FFI function ? -- Serge Stinckwich UMI UMMISCO 209 (SU/IRD/UY1) "Programs must be written for people to read, and only incidentally for machines to execute."http://www.doesnotunderstand.org/

3 4