January 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Commits of two last week

by Marcus Denker

On 27 Jan 2014, at 12:23, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 27 Jan 2014, at 12:20, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > >> Nice. Is possilbe to add dates and links to Penelope for outsiders that do not have FogBugz account? >> > > The problem is that Penelope never updated its contents since it was installed... > https://pharo.fogbugz.com/f/cases/10157/http-bugs-pharo-org-is-not-in-sync-… (opened 27 March 2013) Marcus

Jan. 27, 2014

Re: [Pharo-dev] Commits of two last week

by Marcus Denker

On 27 Jan 2014, at 12:20, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Nice. Is possilbe to add dates and links to Penelope for outsiders that do not have FogBugz account? > The problem is that Penelope never updated its contents since it was installed... > -- Pavel > > > 2014-01-27 Pharo4Stef <pharo4Stef(a)free.fr> > http://association.pharo.org/web/weekly/Commits-Jan-1 > >

Jan. 27, 2014

Re: [Pharo-dev] Commits of two last week

by Pavel Krivanek

Nice. Is possilbe to add dates and links to Penelope for outsiders that do not have FogBugz account? -- Pavel 2014-01-27 Pharo4Stef <pharo4Stef(a)free.fr> > http://association.pharo.org/web/weekly/Commits-Jan-1 > >

Jan. 27, 2014

Re: [Pharo-dev] build validation shows wrong slice loaded

by Max Leske

On 27.01.2014, at 08:07, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 26 Jan 2014, at 20:59, Max Leske <maxleske(a)gmail.com> wrote: > >> In 12259 I had validation warnings and so I went and looked at that page for the first time (pretty cool btw!). The problem with issue 12259 is now that there are multiple slices in there. The validation performed on the image has been done correctly with my version of the slice, but all the messages on the page say that itâs Damienâs slice (which doesnât contain the same code and would produce completely different results). >> >> So, my guess is, that the name is somehow being cached (?) or something. It would be nice to have the validation show the correct slice to avoid others spending the extra 20 minutes until theyâve figured it outâ¦ :) >> > > It is always the slice loaded with the highest number. And MC gives lower numbers as it just numbers the ones with your name in order. You need to change the number yourself when committing. Ok, thanks. > > Marcus > >

Jan. 27, 2014

Re: [Pharo-dev] Two videos to explain what we do when integrating a fix.

by Marcus Denker

On 27 Jan 2014, at 10:24, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > ok I will check that with marcus to see how we can publish on the pharo account. > Yes, we can do that tomorrow. > Stef > > > >> Pharo4Stef wrote >>> Should put them on youtbue but I dod not how. >> >> I'm still having problems viewing the second one. Will you host it somewhere >> else pleeeeease? I want to learn!!! >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: http://forum.world.st/Two-videos-to-explain-what-we-do-when-integrating-a-f… >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> > >

Jan. 27, 2014

Re: [Pharo-dev] IDE reloading based on configuration

by Pharo4Stef

Hi pavel my reply was using a wrong mail. So here it is: Mega hyper cool. I still want to introduce Morphic-Widgets as a package as shown on the bugtracker. Stef On 21 Jan 2014, at 20:06, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hi, > > I transformed the Morphic reloading script into a configuration and it works :-) > > Jenkins job: > https://ci.inria.fr/pharo-contribution/view/Pharo-Kernel-3.0/job/PharoKerne… > > Configuration repository: > http://smalltalkhub.com/#!/~Pharo/SystemConfigurations/ > > it's named ConfigurationOfIDE. > > Small note, I must parse versions list from a string because the method has too many literals if I try to use standard form used in normal configurations generated by the tools. > > Cheers, > -- Pavel

Jan. 27, 2014

Re: [Pharo-dev] bugs with blocks

by Camille Teruel

On 27 janv. 2014, at 09:28, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > Hello, > > I don't think this line was there by mistake. In some cases, the activePC with this code is lower than the startpc and then the debugger shows an error 'no ast node found at this pc' and cannot properly highlight the current executed code because the pc is outside the method bytecode. Ok, thanks ClÃ©ment. So shouldn't it be: activePC <= self home startpc ifTrue: [ activePC := pc ] since self may be the context of a block? > I remember adding this line as a hack to fix a bug report.... But I don't remember any more... > > Here's an extract from my blog post, at that time the method had not this line, and we added it due to a bug report: > > in a debugger, the context on the top of the stack does not highlight the same way other contexts does. In fact, the top context highlights the instruction in source code that *will* be executed in the next step. On the contrary, all the other contexts highlights the instruction in source code that *has been* executed previously. That means that you need to take care about that in the mapping to highlight the correct range. > > Right now we had to keep the old mapping API so there is a method named rangeForPC:contextIsActiveContext: that has a boolean as second argument. With this boolean you know if you need to look for the range of the current pc (first argument) of the previous pc of the first argument. On the old mapping, they needed the exact pc for their pc to abstract pc mapping. So they needed a method previousPCFor: to handle the case of multiple byte code instructions. But we donât care, as the pc will be used in the scan of instructionForPC:, so we just need to do pc â 1. > > The result is : > > DebuggerMethodMapOpal>>#rangeForPC: aPC contextIsActiveContext:contextIsActive > "return the debug highlight for aPC" > | pc | > pc := contextIsActive ifTrue: [aPC] ifFalse: [aPC - 1]. > ^ (methodNode sourceNodeForPC: pc) debugHighlightRange > RBMethodNode>>#sourceNodeForPC: anInteger > ^ (self ir instructionForPC: anInteger) sourceNode > > IRMethod>>#instructionForPC: aPC > 0 to: -3 by: -1 do: [ : off | > (self firstInstructionMatching: [:ir | ir bytecodeOffset = (aPC - off) ]) ifNotNil: [:it |^it]] > > > > 2014/1/27 Camille Teruel <camille.teruel(a)gmail.com> > > On 27 janv. 2014, at 08:44, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On 26 Jan 2014, at 10:08, Camille Teruel <camille.teruel(a)gmail.com> wrote: >> >>> [ [ ] ] >>> prints: >>> [ ] >>> instead of: >>> [ [ ] ] >>> >>> and >>> [ :arg | [ arg ] ] >>> prints: >>> DoIt >>> ^ [ :arg | [ arg ] ] yourself >>> instead of: >>> [ :arg | [ arg ] ] >>> >>> >>> Apparently it's the print that is not correct because of problem in #sourceNode. >>> Any clue? Marcus? ClÃ©ment? >> >> Other than âthe devil is in the detailsâ (this is all far too complex for my taste, implementation wiseâ¦) >> >> Can you add an issue? My problem is that i have no time right now to even think about itâ¦ > > My problem is that I found a fix with try-and-fail without really understanding the code. > I just found that problematic examples were passing through that condition whereas non problematic examples were not. > I looked at the versions and though that you may have left this line by error. > I removed it and so far, it *seems* to work. So the fix is there but I have no clue if it's correct or not. > Here it the case: https://pharo.fogbugz.com/f/cases/12732/sourceNode-broken > >> >> Marcus > >

Jan. 27, 2014

Re: [Pharo-dev] [Pharo-users] Commits of two last week

by Sven Van Caekenberghe

Nice, nice ! On 27 Jan 2014, at 10:23, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > http://association.pharo.org/web/weekly/Commits-Jan-1 Would it be possible to have these summaries for the past as well ?

Jan. 27, 2014

Re: [Pharo-dev] Two videos to explain what we do when integrating a fix.

by Pharo4Stef

ok I will check that with marcus to see how we can publish on the pharo account. Stef > Pharo4Stef wrote >> Should put them on youtbue but I dod not how. > > I'm still having problems viewing the second one. Will you host it somewhere > else pleeeeease? I want to learn!!! > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Two-videos-to-explain-what-we-do-when-integrating-a-f… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Jan. 27, 2014

Commits of two last week

by Pharo4Stef

http://association.pharo.org/web/weekly/Commits-Jan-1

Jan. 27, 2014