Re: [Pharo-users] Set >> collect:thenDo:

2019-09-09 Thread Richard O'Keefe
An automatic refactoring rule that converts (a collect: b) do: c to (a collect: b thenDo: c) would change the semantics of the code in all of Squeak, Pharo, and Smalltalk/X, whichever definition of #collect:thenDo: is taken, and in Squeak would make the code slower, not faster. Using a differe

Re: [Pharo-users] Set >> collect:thenDo:

2019-09-09 Thread Richard O'Keefe
Digging a bit further, the change from the pointless implementation to the current implementation was made between Pharo 2.0 and Pharo 3.0 and the current definition was introduced into ST/X some time between 2010 and 2012, which is about the same time as Pharo. {collect,select,reject}:thenDo: were

Re: [Pharo-users] My Pharo Wiki

2019-09-09 Thread Julien
Hello Sean, Nice work. :-) Do you know about pharo-open-documentation/pharo-wiki [1] ? With Cyril and Oleks, we started it to collect code snippets. Now that it gows bigger and people start to contribute, we try to build a real wiki to document obscure features of Pharo. Tell us if you want t

[Pharo-users] My Pharo Wiki

2019-09-09 Thread Sean P. DeNigris
I've been collecting Pharo tidbits that I found interesting for quite a while. I was aggregating everything today and realized that it had grown into a small "cookbook" which has some useful information not otherwise easily available. I share it in case it is of help: https://github.com/seandenigr

Re: [Pharo-users] Set >> collect:thenDo:

2019-09-09 Thread Steffen Märcker
I think this thread indicates that the selector #collect:thenDo: may indeed cause some missunderstanding given standard semantics of #collect:. Is there any reason not to use a different one, such as #map:thenDo:, to make the difference clearer? A nice side effect could be a new automatic refacto

Re: [Pharo-users] Set >> collect:thenDo:

2019-09-09 Thread David T. Lewis
On Mon, Sep 09, 2019 at 05:46:48PM +1200, Richard O'Keefe wrote: > > (3) Oddly enough, the reason that #collect:thenDo: exists in my > library is that I copied it from Squeak, at a time when it had > the same definition as Pharo and ST/X. Had I known of the change > in Squeak I would

Re: [Pharo-users] uFFI Structure Problem

2019-09-09 Thread Georg Hagn
Thank you Esteban for your fast answer. 1) NULL Pointer assignment: I have implemented your advise, and changed the attribute "abrufCode" to "ExternalAddress null"; >> fieldDesc #(myStruct uint32 version; ... void * abrufCode; ) The Structure has a NULL pointer assigned!? (see Inspector on M