Re: [Pharo-dev] Java Future

Hi Steph, As a newcomer, here is my experience with my first bug-fix: I wrote the fix in about 5 minutes. It then took several weeks to get the big-fix accepted because of issues with the repository and, separately, with bitrot in the list of maintainers. On 30 November 2015 at 16:52, stepharo

[Pharo-dev] Community Building [was: please name your thread]

Tudor, You say that we are talking about different mails. I hope so. "We need to focus on building a great platform." "acting is the only thing that will push us further.". I agree that action is what achieves things. To make sure the correct actions are taken, in a productive and efficient

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

On Thu, Dec 3, 2015 at 4:51 PM, Ben Coman wrote: > On Fri, Dec 4, 2015 at 3:26 AM, Chris Cunningham > wrote: > > > > > > On Thu, Dec 3, 2015 at 5:48 AM, Ben Coman wrote: > >> > >> > >> > >> * Points are summable " { 2@2 . 3@3 } " --> 5@5. But then " 2@2 + > >> 1 " --> 3@3 , so " {} su

Re: [Pharo-dev] Hook "WACurrentRequestContext" into debugger?

On 2015-12-03 6:34 PM, Mariano Martinez Peck wrote: Hi guys, This thing I will ask in this email it's in my mind since YEARS. But I have always thought it was like that and that there was nothing we could do. However, I think it's time I ask again :) For those that have used Seaside, and y

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

On Fri, Dec 4, 2015 at 3:26 AM, Chris Cunningham wrote: > > > On Thu, Dec 3, 2015 at 5:48 AM, Ben Coman wrote: >> >> >> >> * Points are summable " { 2@2 . 3@3 } " --> 5@5. But then " 2@2 + >> 1 " --> 3@3 , so " {} sum " returning 0 would seem to not >> cause any error in this case. >

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

On Fri, Dec 4, 2015 at 4:23 AM, Nicolai Hess wrote: > > > 2015-12-03 14:48 GMT+01:00 Ben Coman : >> >> On Wed, Dec 2, 2015 at 10:45 PM, Sven Van Caekenberghe >> wrote: >> > >> >> On 02 Dec 2015, at 15:21, Nicolai Hess wrote: >> >> >> >> >> >> >> >> 2015-12-02 15:03 GMT+01:00 Ben Coman : >> >> On

Re: [Pharo-dev] VoyageMongo and cache compaction

I haven't used VoyageMongo, but just a general comment that maybe the testcase is best produced at your end, since you understand the symptoms and can cut down a slice of your application as a template. Publishing that to the mail list provides an explicit demonstration of the problem making it eas

Re: [Pharo-dev] [Moose-dev] Re: Explanation how to use GT Debugger and GT SUnit Debugger with DarkThem in Pharo 4.0 [was] Using Re: Re: showing a diff on #assert:equals:

On Thu, Dec 3, 2015 at 10:25 PM, Mariano Martinez Peck < marianop...@gmail.com> wrote: > > > On Thu, Dec 3, 2015 at 6:02 PM, Andrei Chis > wrote: > >> Finally it works :) >> >> Now this is a rather generic extension. >> If you want to go one step further you can create an extension that shows >>

Re: [Pharo-dev] [Moose-dev] Re: Explanation how to use GT Debugger and GT SUnit Debugger with DarkThem in Pharo 4.0 [was] Using Re: Re: showing a diff on #assert:equals:

On Thu, Dec 3, 2015 at 6:02 PM, Andrei Chis wrote: > Finally it works :) > > Now this is a rather generic extension. > If you want to go one step further you can create an extension that shows > more contextual information related to your application. > > I think I still have some generic possibl

Re: [Pharo-dev] [Moose-dev] Explanation how to use GT Debugger and GT SUnit Debugger with DarkThem in Pharo 4.0 [was] Using Re: Re: showing a diff on #assert:equals:

Finally it works :) Now this is a rather generic extension. If you want to go one step further you can create an extension that shows more contextual information related to your application. Cheers, Andrei On Thu, Dec 3, 2015 at 8:22 PM, Mariano Martinez Peck wrote: > Andrei... you rock!!! It

Re: [Pharo-dev] Differences Compiler vs. OpalCompiler (or parser)

2015-12-03 16:59 GMT+01:00 Marcus Denker : > > On 20 Nov 2015, at 22:37, Nicolai Hess wrote: > > GTDummyExamples class > d: anInteger > > > anInteger'> > > MessageNotUnderstood> > > ^ 1 + anInteger > > The old Parser complains about the class name "MessageNotUnderstoo

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

2015-12-03 14:48 GMT+01:00 Ben Coman : > On Wed, Dec 2, 2015 at 10:45 PM, Sven Van Caekenberghe > wrote: > > > >> On 02 Dec 2015, at 15:21, Nicolai Hess wrote: > >> > >> > >> > >> 2015-12-02 15:03 GMT+01:00 Ben Coman : > >> On Wed, Dec 2, 2015 at 12:38 AM, Tudor Girba > wrote: > >> > Hi, > >> >

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

On Thu, Dec 3, 2015 at 5:48 AM, Ben Coman wrote: > > > * Points are summable " { 2@2 . 3@3 } " --> 5@5. But then " 2@2 + > 1 " --> 3@3 , so " {} sum " returning 0 would seem to not > cause any error in this case. > > > cheers -ben but points aren't commutative: 2@2 + 1 " = 3@3" 1

Re: [Pharo-dev] Differences Compiler vs. OpalCompiler (or parser)

> On 20 Nov 2015, at 22:37, Nicolai Hess wrote: > > GTDummyExamples class > d: anInteger > > > anInteger'> > > MessageNotUnderstood> > > ^ 1 + anInteger > > The old Parser complains about the class name "MessageNotUnderstood" used as > a pragma > argument with

Re: [Pharo-dev] Semantic analysis doesn't compute RBArgumentNode instances

Done: https://pharo.fogbugz.com/f/cases/17179/Semantic-analysis-doesn-t-compute-RBArgumentNode-instances On Thu, Dec 3, 2015 at 2:30 PM, Marcus Denker wrote: > yes ! > > On 03 Dec 2015, at 14:16, Martin Dias wrote: > > > > Hi, > > > > In Pharo 4, the RBExplicitVariableParser computed the argume

[Pharo-dev] How to listen Monticello load start/end (and origin of changes)

Hi, Doru asked me how does Epicea listen this information, and I created a snippet to demo it *in a plain Pharo 5 image* (no need to load Epicea before). Maybe somebody else is interested, that's why I share it with everybody. You can open a Transcript and evaluate the following snippet. After ev

Re: [Pharo-dev] VoyageMongo and cache compaction

> On 03 Dec 2015, at 09:58, Holger Freyther wrote: > > Hi guys, > This is a write "heavy" workload but at no point in time more than a couple > of objects will > be in the cache. So somehow the VOMongoCache>>#compactIfNeeded check does not > trigger and/or given the difference in the sizes of

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

On Wed, Dec 2, 2015 at 10:45 PM, Sven Van Caekenberghe wrote: > >> On 02 Dec 2015, at 15:21, Nicolai Hess wrote: >> >> >> >> 2015-12-02 15:03 GMT+01:00 Ben Coman : >> On Wed, Dec 2, 2015 at 12:38 AM, Tudor Girba wrote: >> > Hi, >> > >> >> On Dec 1, 2015, at 5:13 PM, Max Leske wrote: >> >> >> >>

Re: [Pharo-dev] Semantic analysis doesn't compute RBArgumentNode instances

yes ! > On 03 Dec 2015, at 14:16, Martin Dias wrote: > > Hi, > > In Pharo 4, the RBExplicitVariableParser computed the argument variables as > RBArgumentNodes: > > (Integer >> #bitAnd:) parseTree arguments > "--> an OrderedCollection(RBArgumentNode(n))" > > In Pharo 50191, such parser was rem

[Pharo-dev] Semantic analysis doesn't compute RBArgumentNode instances

Hi, In Pharo 4, the RBExplicitVariableParser computed the argument variables as RBArgumentNodes: (Integer >> #bitAnd:) parseTree arguments "--> an OrderedCollection(RBArgumentNode(n))" In Pharo 50191, such parser was removed (case 16026) because "semantic analysis" does the same job. However, it

Re: [Pharo-dev] vm crash in SmalltalkImage>garbageCollect

Hi, I discovered a similar issue described in this issue https://pharo.fogbugz.com/f/cases/14165/ObsoleteTest-testFixObsoleteSharedPools. Might be related. Cheers, Max > On 24 Nov 2015, at 19:34, Eliot Miranda wrote: > > > > On Mon, Nov 23, 2015 at 4:57 PM, Andrei Chis

[Pharo-dev] VoyageMongo and cache compaction

Hi guys, I started to run a production load with VoyageMongo and every day the maximum latency of it goes up a bit. Today I looked at the production system and the VOMongoRepository and the VOMongoCache and saw that the cache had around 90 entries in the "objects" WeakValueDictionary al

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

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

[Pharo-dev] [pharo-project/pharo-core] e5a9d5: 50482

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: e5a9d5fb62466db4fa8eeb32b048bba460adfaeb https://github.com/pharo-project/pharo-core/commit/e5a9d5fb62466db4fa8eeb32b048bba460adfaeb Author: Jenkins Build Server Date: 2015-12-03 (Thu, 03 Dec 2015

Re: [Pharo-dev] fixing our tools

Hi, Yes, I think we really need to unify both the editor (get really rid of the old one) and the tools… e.g. it is strange that all the changes we did for breakpoint visuals now have to be redone 3 times to get them in all tools… I will have a look at these, many seem to be related to the sugge