- Pharo-dev - lists.pharo.org

NativeBoose-Win32 fix in Pharo4

by Richard Wettel

Hi Some time ago I found a bug in NativeBoost-Win32, which would not allow me to run CodeCity in Pharo 4 (CodeCity depends on this package, through a dependency onConfigurationOfNBOpenGL, version: #stable): https://pharo.fogbugz.com/f/cases/14728 I fixed the bug and the fiix was integrated on 14.01, with the comment "in 40443". My expectation was that as soon as I would switch to Pharo 4, I would also get this bug fix. That is not the case at the moment. I get Name: NativeBoost-Win32-TheIntegrator.54 and the one including my fix is the next one, NativeBoost-Win32-TheIntegrator.56 (in http://smalltalkhub.com/mc/Pharo40/main) It seems that something is still missing there. I would appreciate any help. Cheers Ricky

Feb. 19, 2015

Re: [Pharo-dev] [Slots] Invisible Slots

by Marcus Denker

> On 19 Feb 2015, at 10:45, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> -> generate better byte code, the reflective read is of course slow. > > > this is easy. What we need to do is to override #emitValue: and #emitStore: > > emitValue: methodBuilder > > methodBuilder > pushInstVar: baseSlot index; > pushLiteral: self name; > pushLiteral: nil; > send: #at:ifAbsent: > > for storing, the problem is that the value to be saved is on top of the stack. so > we need to first save it and pop it off to be able to use #at:put:: > > emitStore: methodBuilder > | tempName | > > tempName := ('0generated_',self name) asSymbol. > > methodBuilder > addTemp: tempName; > storeTemp: tempName; > popTop; > pushInstVar: baseSlot index; > pushLiteral: self name; > pushTemp: tempName; > send: #at:put: > > committed. https://pharo.fogbugz.com/f/cases/14962/emit-bytecode-for-PropertySlot-impr… This in addition uses the same trick of the temp to not need a writeToSlot:of: method in object for the default code generated for reflective write of slots. Marcus

Feb. 19, 2015

Re: [Pharo-dev] Why was #asLegalSelector removed?

by stephan

The way this was handled can be improved. It is sometimes difficult for us not in Lille to find out what is going on. - a specific issue name helps us notice what changes - check where code is used. DeprecationFinder works for that (and should add more repos and team projects). And a specific one: the rename from #asSmalltalkComment to #asComment is problematic. There are 2 kinds of thing casually known as comments: the comment text in a method, and the class comment. The method name should reflect that. Stephan

Feb. 19, 2015

Re: [Pharo-dev] Super fast delay

by Ben Coman

On Mon, Feb 16, 2015 at 4:01 PM, Holger Hans Peter Freyther < holger(a)freyther.de> wrote: > On Thu, Oct 30, 2014 at 06:32:48PM -0400, stepharo wrote: > > Good Morning Ben, Stef, > > > We really need people to have a look at the code of Ben. > > I downloaded a Pharo-4 image today and executed: > To clarify. The fix is not yet in Pharo-4. > > time pharo --nodisplay --headless ./Pharo-40490.image eval "(Delay > forSeconds: 5) wait" > a Delay(5000 msecs) > > real 0m1.254s > user 0m1.192s > sys 0m0.060s > > > So the first delay doesn't appear to wait the five seconds. I > would like to work on kqueue/epoll and remove polling and it > looks this involves code with Delay as well. I wonder if you > could provide an overview of what needs to be done and what is > done? > The pre-requisite issue 14942 is waiting for review. It really should take only 10 minutes to review... 1. In latest Pharo 4, inspect "Delay newCodeEnabled" and observe that it is "true". 2. Open the Pharo4Inbox and filter on 14942. 3. Select newest slice and <Merge>. 4. Observe the diff shows all "false" parts removed (it doesn't really get much simpler than this to review). 5. Click <merge> to finish. 6. Observe the image continues to run smoothly. 7. Report your observations on https://pharo.fogbugz.com/default.asp?14942 I need to refresh myself on the fix I did back in 2-Dec. Its languished while some support infrastructure was added to help the system ride-through the change. cheers -ben

Feb. 19, 2015

Re: [Pharo-dev] I just crashed sthub

by Ben Coman

thanks for the notice. cheers -ben On Thu, Feb 19, 2015 at 9:31 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > is restoredâ¦ but I couldnât applied the change I wantedâ¦ maybe tomorrow :) > > > On 19 Feb 2015, at 14:24, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > > > Thank you Esteban. > > > > > >> On 19 Feb 2015, at 14:18, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> > >> is temporal > >> and for the better good. > >> > >> please, be patient :) > >> > >> Esteban > >> > > > > > > >

Feb. 19, 2015

Re: [Pharo-dev] I just crashed sthub

by Esteban Lorenzano

is restoredâ¦ but I couldnât applied the change I wantedâ¦ maybe tomorrow :) > On 19 Feb 2015, at 14:24, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Thank you Esteban. > > >> On 19 Feb 2015, at 14:18, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> is temporal >> and for the better good. >> >> please, be patient :) >> >> Esteban >> > >

Feb. 19, 2015

Re: [Pharo-dev] I just crashed sthub

by Yuriy Tymchuk

Thank you Esteban. > On 19 Feb 2015, at 14:18, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > is temporal > and for the better good. > > please, be patient :) > > Esteban >

Feb. 19, 2015

I just crashed sthub

by Esteban Lorenzano

is temporal and for the better good. please, be patient :) Esteban

Feb. 19, 2015

Re: [Pharo-dev] Spec terminology: renaming some terms

by Ben Coman

Thanks for this Johan. On Thu, Feb 19, 2015 at 8:37 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > You got my vote. > > > On 19 Feb 2015, at 13:22, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > > > Hi all, > > > > I donât read mails on pharo-dev usually, so sorry if this has been > discussed before (and then pointers to the discussion would be appreciated). > > > > Last week, in Pharo-users I proposed the Spec terminology changes below. > Responses were positive. I am willing to volunteer to do that next week so > itâs finished before the 28th and itâs included in Pharo 4. And then I will > update the documentation as well. But first I want to know if there are any > objections from people on this list. > > > > I propose to rename: > > - ComposableModel to ComposableUI > > - all the protocols âprotocol-*â to âAPI-*â > > > > Other renaming-related comments are also welcome. > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > > > Johan Fabry - http://pleiad.cl/~jfabry > > PLEIAD lab - Computer Science Department (DCC) - University of Chile > > > > > > >

Feb. 19, 2015

Re: [Pharo-dev] Spec terminology: renaming some terms

by Sven Van Caekenberghe

You got my vote. > On 19 Feb 2015, at 13:22, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > Hi all, > > I donât read mails on pharo-dev usually, so sorry if this has been discussed before (and then pointers to the discussion would be appreciated). > > Last week, in Pharo-users I proposed the Spec terminology changes below. Responses were positive. I am willing to volunteer to do that next week so itâs finished before the 28th and itâs included in Pharo 4. And then I will update the documentation as well. But first I want to know if there are any objections from people on this list. > > I propose to rename: > - ComposableModel to ComposableUI > - all the protocols âprotocol-*â to âAPI-*â > > Other renaming-related comments are also welcome. > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD lab - Computer Science Department (DCC) - University of Chile > >

Feb. 19, 2015