Re: [Pharo-dev] #sum:, #detectSum:, #sumNumbers:

Hi, I cannot seem to agree with the current line of reasoning, so I am withdrawing from this debate. It’s late in the year and I know I need a break, so it is likely that I am missing something obvious or that I am just persisting in some sort of bike-shedding point of view :). Thanks for

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Consortium Sponsored Development Effort

On Sun, Dec 20, 2015 at 08:56:43AM +, Dimitris Chloupis wrote: > Fuel I assume enters here the equation as a data exchange format , the > problem I have with fuel is that its not backward compatible which for me Once you have a set of OS processes running Pharo how they talk to each other is

Re: [Pharo-dev] [Vm-dev] Re: SecureSession frame types

Le 20/12/2015 12:20, Clément Bera a écrit : > Hello, > > I tried to get your document but I got: > > Dropbox - error > > Is it only me ? > > Hi, I could get it without problem. -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France signature.asc

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Consortium Sponsored Development Effort

I mentions this because in OSProcess-Unix there is UnixProcess class, at the class side there are several examples that launch a separate instance of Squeak/Pharo and make the two communicate with each other. In the instance of the class there are methods like forkHeadlessSqueak ,

Re: [Pharo-dev] [Vm-dev] VM Maker: VMMaker.oscog-eem.1609.mcz

Super !!! Eliot what will be 1 class maxval then? Stef Le 17/12/15 20:12, Eliot Miranda a écrit : Hi All, the real Cog 64-bit Spur x64 VM just evaluated 3+4 correctly on Mac OS X:

Re: [Pharo-dev] #sum:, #detectSum:, #sumNumbers:

Max, sum: aBlock ifEmpty: emptyBlock needs to obtain the sample evaluating the block. sum: aBlock ifEmpty: emptyBlock | sum sample | self isEmpty ifTrue: [ ^ emptyBlock value ]. sample := aBlock value: self anyOne. sum := self inject: sample into: [ :accum :each | accum + (aBlock value: each) ].

Re: [Pharo-dev] #sum:, #detectSum:, #sumNumbers:

> On 20 Dec 2015, at 12:59, Max Leske wrote: > > I would like to wrap up this discussion. Good idea. >> On 05 Dec 2015, at 18:14, stepharo wrote: >> >> So what is the conclusion? >> I like the idea of Esteban M to have iterator because it moves some

Re: [Pharo-dev] #sum:, #detectSum:, #sumNumbers:

Hi, Could we not have sum, but sumNumbers instead? So, we would end up with: sum:ifEmpty: sum: (with error) sumNumbers (without error) From the outside, #sum: looks like it should parameterize #sum, but the implementation is actually different. So, given that in this implementation #sum is

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Consortium Sponsored Development Effort

Hi Dimitri, Dave et all. First let me do a little disclaimer. Regarding the developments itself of this sponsorship, we discussed about the topics I said in the first email. However, those are not written in stone and that's why I also asked for feedback. As you know, Pharo has relatively little

Re: [Pharo-dev] #sum:, #detectSum:, #sumNumbers:

> On 20 Dec 2015, at 13:43, Gabriel Cotelli wrote: > > Max, > > sum: aBlock ifEmpty: emptyBlock needs to obtain the sample evaluating the > block. > > sum: aBlock ifEmpty: emptyBlock > | sum sample | > self isEmpty ifTrue: [ ^ emptyBlock value ]. >

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Consortium Sponsored Development Effort

not really because as I said UnixProcess already has an implementation for doing this, you dont need any of those protocols/libraries you mentioned, it does not even need Fuel. It already works. And the reason why I mentioned Python multiprocessing module is because multiprocessing does not only

Re: [Pharo-dev] #sum:, #detectSum:, #sumNumbers:

I would like to wrap up this discussion. > On 05 Dec 2015, at 18:14, stepharo wrote: > > So what is the conclusion? > I like the idea of Esteban M to have iterator because it moves some behavior > out of core classes. > > [[[ > > aCollection arithmetic sum: [...] or

Re: [Pharo-dev] [Vm-dev] VM Maker: VMMaker.oscog-eem.1609.mcz

SmallInteger maxVal highBit -> 60. 3 bits reserved for immediate tags, 1 bit for sign, 60 remaining for positive magnitude... 2015-12-20 11:56 GMT+01:00 stepharo : > Super !!! > Eliot what will be > > 1 class maxval > then? > > Stef > > Le 17/12/15 20:12, Eliot Miranda a écrit

Re: [Pharo-dev] #sum:, #detectSum:, #sumNumbers:

> On 20 Dec 2015, at 14:10, Tudor Girba wrote: > > Hi, > > Could we not have sum, but sumNumbers instead? So, we would end up with: > > sum:ifEmpty: > sum: (with error) > sumNumbers (without error) > > From the outside, #sum: looks like it should parameterize #sum, but

Re: [Pharo-dev] #sum:, #detectSum:, #sumNumbers:

Hi, > On Dec 20, 2015, at 2:30 PM, Max Leske wrote: > > >> On 20 Dec 2015, at 14:10, Tudor Girba wrote: >> >> Hi, >> >> Could we not have sum, but sumNumbers instead? So, we would end up with: >> >> sum:ifEmpty: >> sum: (with error) >> sumNumbers

Re: [Pharo-dev] #sum:, #detectSum:, #sumNumbers:

Hi, It’s clear that choices we would make would not be the same :). So, let’s drop past discussions and stay with the current situation. Do you agree with the observation that in the proposal of Max #sum and #sum: would not share the same meaning? If yes, do you agree that it would be

Re: [Pharo-dev] #sum:, #detectSum:, #sumNumbers:

No means I don't want to start adding Numbers to beautiful unary selectors. I don't understand why you don't understand that point about beauty and simplicity. > On 20 Dec 2015, at 14:54, Tudor Girba wrote: > > Hi, > > I am not sure I understand the meaning of NO in the

Re: [Pharo-dev] #sum:, #detectSum:, #sumNumbers:

> On 20 Dec 2015, at 14:57, Tudor Girba wrote: > > Hi, > > It’s clear that choices we would make would not be the same :). So, let’s > drop past discussions and stay with the current situation. Do you agree with > the observation that in the proposal of Max #sum and

Re: [Pharo-dev] #sum:, #detectSum:, #sumNumbers:

Doru, For me this whole discussion started because you (the standpoint that you take) hijacked the best selector (#sum) for a use case that is much less common than adding a collection of numbers which should give 0 when empty (you hijack it by not wanting to return 0, which I totally

Re: [Pharo-dev] #sum:, #detectSum:, #sumNumbers:

NO > On 20 Dec 2015, at 14:32, Tudor Girba wrote: > > Hi, > >> On Dec 20, 2015, at 2:30 PM, Max Leske wrote: >> >> >>> On 20 Dec 2015, at 14:10, Tudor Girba wrote: >>> >>> Hi, >>> >>> Could we not have sum, but sumNumbers

Re: [Pharo-dev] #sum:, #detectSum:, #sumNumbers:

Hi, I am not sure I understand the meaning of NO in the context of the previous message. Is the NO related to the sumNumbers, or to the min, max? Cheers, Doru > On Dec 20, 2015, at 2:43 PM, Sven Van Caekenberghe wrote: > > NO > >> On 20 Dec 2015, at 14:32, Tudor Girba

Re: [Pharo-dev] #sum:, #detectSum:, #sumNumbers:

Hi, > On Dec 20, 2015, at 3:07 PM, Sven Van Caekenberghe wrote: > > >> On 20 Dec 2015, at 14:57, Tudor Girba wrote: >> >> Hi, >> >> It’s clear that choices we would make would not be the same :). So, let’s >> drop past discussions and stay with the

Re: [Pharo-dev] #sum:, #detectSum:, #sumNumbers:

On Mon, Dec 21, 2015 at 12:43 AM, Sven Van Caekenberghe wrote: > Doru, > > For me this whole discussion started because you (the standpoint that you > take) hijacked the best selector (#sum) for a use case that is much less > common than adding a collection of numbers which should

Re: [Pharo-dev] #sum:, #detectSum:, #sumNumbers:

Updated benchmarks with pre-calculated collection of numbers (as suggested by Sven): Benchmarks of the current versions: [ (1 to: 100) asArray sum ] benchFor: 10 seconds. 124 iterations, 12.389 per second [ (1 to: 100) asArray sum: [ :e | e ] ] benchFor: 10 seconds.

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Consortium Sponsored Development Effort

On Sun, Dec 20, 2015 at 05:07:47PM +0800, Pierce Ng wrote: > On Sun, Dec 20, 2015 at 08:56:43AM +, Dimitris Chloupis wrote: > > Fuel I assume enters here the equation as a data exchange format , the > > problem I have with fuel is that its not backward compatible which for me > Fuel works

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Consortium Sponsored Development Effort

how the communication is happening via Fuel , does it save to a fuel file or it does it through memory some way ? On Sun, Dec 20, 2015 at 6:04 PM David T. Lewis wrote: > On Sun, Dec 20, 2015 at 05:07:47PM +0800, Pierce Ng wrote: > > On Sun, Dec 20, 2015 at 08:56:43AM +,

Re: [Pharo-dev] #sum:, #detectSum:, #sumNumbers:

> On 20 Dec 2015, at 15:26, Ben Coman wrote: > > On Mon, Dec 21, 2015 at 12:43 AM, Sven Van Caekenberghe > wrote: >> Doru, >> >> For me this whole discussion started because you (the standpoint that you >> take) hijacked the best

Re: [Pharo-dev] #sum:, #detectSum:, #sumNumbers:

I did a pass on all the changes that would be required (whatever the outcome of this discussion). Looks easy enough. One interesting point: FloatArray>>sum is implemented as a primitive in the FloatArrayPlugin and the zero element is explicitly defined as 0.0. The primitive will not fail for an

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Consortium Sponsored Development Effort

yeah I completely agree that any improvement is more than welcomed. Thanks I will check out RemoteTask and Seamless :) On Sun, Dec 20, 2015 at 8:55 PM Mariano Martinez Peck wrote: > Hi Dimitri, Dave et all. > > First let me do a little disclaimer. Regarding the

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Consortium Sponsored Development Effort

Hi Mariano, Le 20/12/2015 19:54, Mariano Martinez Peck a écrit : Hi Dimitri, Dave et all. First let me do a little disclaimer. Regarding the developments itself of this sponsorship, we discussed about the topics I said in the first email. However, those are not written in stone and that's why