[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/50515 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] [Ann] ReadWriteLock

2016-01-07 0:15 GMT+01:00 Ben Coman : > > I'm not qualified to judge, but is sounds okay. I have an alternative > proposal to consider that hopefully might remove Semaphore handling > completely from Process>>terminate. > > What if we have a wait primitive that instead of

Re: [Pharo-dev] ConfigurationOfXXX package is not visible in nautilus...

is in Configurations group :) that’s by design, I think > On 07 Jan 2016, at 11:14, Blondeau Vincent > wrote: > > Hi, > > Happy new year ! > > It seems that any configuration loaded by Jenkins is not visible in Nautilus > (at package level) but are

[Pharo-dev] ifError: implementation is bad

Hi I look at implementation of BlockClosure>>ifError: . I did't know that it culls arguments to errorBlock. But what is this arguments? It is not error instance but specific properties from it. BlockClosure>>ifError: errorHandlerBlock ^ self on: Error do: [:ex | errorHandlerBlock cull: ex

Re: [Pharo-dev] ConfigurationOfXXX package is not visible in nautilus...

I loaded a configuration too (not with command line), and it wasn’t in the Configurations group. The spotter finds it, and auto-completion does too. It can’t be found in Nautilus.. > On Jan 7, 2016, at 11:29 AM, Esteban Lorenzano wrote: > > is in Configurations group :) >

Re: [Pharo-dev] ifError: implementation is bad

2016-01-07 13:35 GMT+01:00 Sven Van Caekenberghe : > If think it makes more sense to #cull: the exception instance, it is more > object oriented We all know it. But then we found such methods in the system and cry :). who can wrote it

Re: [Pharo-dev] Atomic commits

Hi, Nicolas Cellier writes: > I wish the commits were much more atomic than they currently are... I agree. This is important (and one of my research topics https://hal.inria.fr/hal-01116225 :-)). Martin Dias worked on EpiceaUntangler to help developers do

Re: [Pharo-dev] ifError: implementation is bad

> On 07 Jan 2016, at 13:11, Denis Kudriashov wrote: > > Hi > > I look at implementation of BlockClosure>>ifError: . I did't know that it > culls arguments to errorBlock. > But what is this arguments? It is not error instance but specific properties > from it. > >

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

Thanks for the (positive) feedback. My problem is: if you think this through, lots of things could change. Consider that I added #magnitudes this would imply that sorting should move too, because you cannot assume the objects to be sortable (i.e. Magnitudes or conforming to that protocol).

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

2016-01-07 13:14 GMT+01:00 Max Leske : > Very, very cool Sven (and Henrik!)! > > And it even works with exotic objects: { 1@2. 2@3 } numbers sum “—> (3@5)” > I really not understand how it helps with original problem. There was example with colors sum which was stop people to

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

On Mon, Jan 4, 2016 at 10:55 PM, Guillermo Polito wrote: > I like these last. > > Particularly because > > - it cleans the collection’s API > - we can continue extending this idea to add parallelism, mutual exclusion... I don't understand the second point. > > >> On

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

I'd say that it is not quite a proxy nor a decorator as their main characteristic is to maintain the api of its wrapee, and so be polymorphic and transparent. At least not the number example. The main reason of this wrappers are to augment the api. But i do not know if that has a name. However, a

[Pharo-dev] [pharo-project/pharo-core] bcba85: 50516

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: bcba85d5f995016da96d32402b00aa0613161dca https://github.com/pharo-project/pharo-core/commit/bcba85d5f995016da96d32402b00aa0613161dca Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/50516 Home: https://github.com/pharo-project/pharo-core

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

On Thu, Jan 7, 2016 at 9:40 PM, Sven Van Caekenberghe wrote: > >> On 07 Jan 2016, at 14:23, Ben Coman wrote: >> >> On Mon, Jan 4, 2016 at 10:55 PM, Guillermo Polito >> wrote: >>> I like these last. >>> >>> Particularly because >>>

Re: [Pharo-dev] [ANN] I created a web page so you can stalk me :)

> On 07 Jan 2016, at 18:18, Esteban Lorenzano wrote: > > Hi, > > Stef told me I need to make a bit more visibility my work, and while being in > Togo I sketched an application I tested last few days and seems to be working > fina. > Of course, easiest way would be to

Re: [Pharo-dev] [ANN] I created a web page so you can stalk me :)

2016-01-07 16:54 GMT-03:00 stepharo : > This is not to be visible. > This is to educate you guys :) > The point is how much time does it take esteban to fix FFI > How much worth is that? > All these questions and like that you know what esteban is doing for > real

[Pharo-dev] [ANN] I created a web page so you can stalk me :)

Hi, Stef told me I need to make a bit more visibility my work, and while being in Togo I sketched an application I tested last few days and seems to be working fina. Of course, easiest way would be to use twitter as a work log, but I was not satisfied with the idea. Why? well… some reasons

[Pharo-dev] Changing performance balance between CPU & non-volatile storage

An enlightening article (if a bit long). I wonder how non-volatile storage being faster than a CPU might affect Pharo systems. Perhaps the importance of migrating between live and backup Images gains in importance to backups via files. https://queue.acm.org/detail.cfm?id=2874238 cheers -ben

Re: [Pharo-dev] [ANN] I created a web page so you can stalk me :)

Nice! However I wouldn't say you're not visible in the community. ;-) Esteban A. Maringolo 2016-01-07 14:21 GMT-03:00 Esteban Lorenzano : > > On 07 Jan 2016, at 18:18, Esteban Lorenzano wrote: > > Hi, > > Stef told me I need to make a bit more

Re: [Pharo-dev] [Vm-dev] Where to get Monitor implementation based on primitives?

Hi Ben, On Thu, Jan 7, 2016 at 10:39 AM, Ben Coman wrote: > > On Fri, Jan 8, 2016 at 1:20 AM, Eliot Miranda > wrote: > > > > and here's a version with a better class comment > > > > On Thu, Jan 7, 2016 at 9:12 AM, Eliot Miranda