March 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Reflectivity] Tiny progress of the day: MetaLink

by phil＠highoctane.be

Is there any background material one can read about these things? TIA Phil On Mon, Mar 2, 2015 at 9:38 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > The tiny progress of today: I reviewed the code for the MetaLink from Claraâs Breakpoints > and added it to Pharo4. I has as state: > > metaObject the target > selector what to call > arguments which args? > condition true, false or [block evaluating to a boolean] > control before, after, replaceâ¦ > level active at base or meta level? (to stop meta-recursion) > nodes where it is installed. > > > ------ Examples ----- > > MetaLink new > metaObject: Halt; > selector: #now. > > MetaLink new > metaObject: [ self halt ]; > selector: #value. > > MetaLink new > metaObject: #node; > selector: tagExecuted > > or one that can only be installed on Message send: > > MetaLink > metaObject: #object; > selector: perform:withArguments; > arguments: #(selector arguments); > control: #replace > > > Of course, the real core of the whole things is next: An AST transforming compiler plugin > that takes these links into account. > Of course, exact details might change (e.g. control using symbols or classes (ControlBefore)â, > do we call it instead, replace or even AOP-style âaroundâ? > > The first will be just a #before with no arguments, as this is what we need for simple breakpoints. > > Marcus

March 2, 2015

Re: [Pharo-dev] [Reflectivity] Tiny progress of the day: MetaLink

by Sven Van Caekenberghe

Yes, a good breakpoint facility, even a simple one, is really needed. > On 02 Mar 2015, at 09:38, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > The tiny progress of today: I reviewed the code for the MetaLink from Claraâs Breakpoints > and added it to Pharo4. I has as state: > > metaObject the target > selector what to call > arguments which args? > condition true, false or [block evaluating to a boolean] > control before, after, replaceâ¦ > level active at base or meta level? (to stop meta-recursion) > nodes where it is installed. > > > ------ Examples ----- > > MetaLink new > metaObject: Halt; > selector: #now. > > MetaLink new > metaObject: [ self halt ]; > selector: #value. > > MetaLink new > metaObject: #node; > selector: tagExecuted > > or one that can only be installed on Message send: > > MetaLink > metaObject: #object; > selector: perform:withArguments; > arguments: #(selector arguments); > control: #replace > > > Of course, the real core of the whole things is next: An AST transforming compiler plugin > that takes these links into account. > Of course, exact details might change (e.g. control using symbols or classes (ControlBefore)â, > do we call it instead, replace or even AOP-style âaroundâ? > > The first will be just a #before with no arguments, as this is what we need for simple breakpoints. > > Marcus

March 2, 2015

[Reflectivity] Tiny progress of the day: MetaLink

by Marcus Denker

Hi, The tiny progress of today: I reviewed the code for the MetaLink from Claraâs Breakpoints and added it to Pharo4. I has as state: metaObject the target selector what to call arguments which args? condition true, false or [block evaluating to a boolean] control before, after, replaceâ¦ level active at base or meta level? (to stop meta-recursion) nodes where it is installed. ------ Examples ----- MetaLink new metaObject: Halt; selector: #now. MetaLink new metaObject: [ self halt ]; selector: #value. MetaLink new metaObject: #node; selector: tagExecuted or one that can only be installed on Message send: MetaLink metaObject: #object; selector: perform:withArguments; arguments: #(selector arguments); control: #replace Of course, the real core of the whole things is next: An AST transforming compiler plugin that takes these links into account. Of course, exact details might change (e.g. control using symbols or classes (ControlBefore)â, do we call it instead, replace or even AOP-style âaroundâ? The first will be just a #before with no arguments, as this is what we need for simple breakpoints. Marcus

March 2, 2015

[pharo-project/pharo-core] acb5a4: 40523

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: acb5a491ca4ddce3ead7e6c41152977e76f5bc2a https://github.com/pharo-project/pharo-core/commit/acb5a491ca4ddce3ead7e6c4… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-03-02 (Mon, 02 Mar 2015) Changed paths: M NautilusRefactoring.package/NautilusRefactoring.class/instance/private-method/privateRenameMethodFor_.st R OpalCompiler-Core.package/OCASTSemanticAnalyzer.class/instance/error handling/unknownSelector_.st R OpalCompiler-Core.package/OCUnknownSelectorWarning.class/README.md R OpalCompiler-Core.package/OCUnknownSelectorWarning.class/definition.st R OpalCompiler-Core.package/OCUnknownSelectorWarning.class/instance/accessing/node_.st R OpalCompiler-Core.package/OCUnknownSelectorWarning.class/instance/correcting/openMenuIn_.st R OpalCompiler-Core.package/OCUnknownSelectorWarning.class/instance/correcting/replaceSelectorTextTo_.st R OpalCompiler-Tests.package/OCCompilerExceptionsTest.class/instance/tests/testUnknownSelector.st A Reflectivity-Tests.package/MetaLinkTest.class/README.md A Reflectivity-Tests.package/MetaLinkTest.class/definition.st A Reflectivity-Tests.package/MetaLinkTest.class/instance/tests/testBlockLink.st A Reflectivity-Tests.package/MetaLinkTest.class/instance/tests/testConditionLink.st A Reflectivity-Tests.package/MetaLinkTest.class/instance/tests/testCotrolLink.st A Reflectivity-Tests.package/MetaLinkTest.class/instance/tests/testSimpleHaltLink.st M Reflectivity-Tests.package/ReflectiveMethodTest.class/README.md M Reflectivity-Tests.package/ReflectivityExamples.class/README.md M Reflectivity.package/MetaLink.class/README.md M Reflectivity.package/MetaLink.class/definition.st A Reflectivity.package/MetaLink.class/instance/accessing/condition.st A Reflectivity.package/MetaLink.class/instance/accessing/control.st A Reflectivity.package/MetaLink.class/instance/accessing/level.st R Reflectivity.package/MetaLink.class/instance/accessing/metaObject_.st M Reflectivity.package/MetaLink.class/instance/accessing/selector.st R Reflectivity.package/MetaLink.class/instance/accessing/selector_.st A Reflectivity.package/MetaLink.class/instance/ast/asLiteralNode.st M Reflectivity.package/MetaLink.class/instance/initialization/initialize.st M Reflectivity.package/MetaLink.class/instance/installing/installOn_.st M Reflectivity.package/MetaLink.class/instance/installing/uninstall.st A Reflectivity.package/MetaLink.class/instance/link api/arguments_.st A Reflectivity.package/MetaLink.class/instance/link api/condition_.st A Reflectivity.package/MetaLink.class/instance/link api/control_.st A Reflectivity.package/MetaLink.class/instance/link api/level_.st A Reflectivity.package/MetaLink.class/instance/link api/metaObject_.st A Reflectivity.package/MetaLink.class/instance/link api/selector_.st A Reflectivity.package/MetaLink.class/instance/testing/hasCondition.st M Reflectivity.package/ReflectiveMethod.class/instance/invalidate/removeLink.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script522.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script523.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40522.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40523.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40523 15025 privateRenameMethodFor: calls #token https://pharo.fogbugz.com/f/cases/15025 15027 Flesh out MetaLink https://pharo.fogbugz.com/f/cases/15027 15017 remove OCUnknownSelectorWarning https://pharo.fogbugz.com/f/cases/15017 http://files.pharo.org/image/40/40523.zip

March 2, 2015

[pharo-project/pharo-core]

by GitHub

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

March 2, 2015

Re: [Pharo-dev] WhatsUp from: 2015-03-02 until: 2015-03-15

by phil＠highoctane.be

Le 2 mars 2015 07:00, <seaside(a)rmod.lille.inria.fr> a Ã©crit : > > Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: > Using Roassal and GTPlayground to explore data sets. Works very well. Started moving XStreams doc to Pillar format. Resumed development on an ETL component for http://noselus.be using PostgresV2, Sqlite3, and Mongotalk > > ### What's next, until 2015-03-15 (*): > Continuing Pillar docs for XStreams Commercial project work with Seaside, Mongotalk, and Roassal web features. > > (*) we'll be expecting results by then ;) > Phil

March 2, 2015

WhatsUp from: 2015-03-02 until: 2015-03-15

by seaside＠rmod.lille.inria.fr

Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS ### What's next, until 2015-03-15 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)

March 2, 2015

Re: [Pharo-dev] Fwd: Re: Super fast delay

by Ben Coman

This is not going to get as much use before Release as I had hoped, so I refactored it to be able to easily switch between the existing and new code by making two schedulers... * DelayMillisecondScheduler - essentially the existing code * DelayMicrosecondScheduler - based off new primitive which are switchable on the fly via a System Setting. To try to make it easier to review, I've separated changes into three stages: * SLICE.10 accumulates changes the Delay class to add some better semantics to instance variables and method renames * SLICE.14 accumulates changes to split DelayScheduler into two subclasses for the two different schedulers (use the incoming code in the merge conflict) * SLICE.17 accumulates changes to modify DelayMicrosecondScheduler, plus a couple of polishing things. I've added some review notes to the issue https://pharo.fogbugz.com/default.asp?14353 fyi, Tomorrow I start a new job at Buewaters Power Station [1] (2 x 208MW generators). They've been without an electrical engineer for three months leading up to their annual outage in five weeks, so I'm probably flat there playing catch-up for the next two months. Today (GMT+8) would be a really good time to engage me with feedback and queries. I'll try to hang out on IRC as much as possible to speed up discussion. [1] http://www.bluewatersps.com.au/ cheers -ben On Mon, Mar 2, 2015 at 3:09 AM, stepharo <stepharo(a)free.fr> wrote: Please help us to push ben code. -------- Message transfÃ©rÃ© -------- Sujet : Re: [Pharo-dev] Super fast delay Date : Wed, 25 Feb 2015 02:00:25 +0800 De : Ben Coman <btc(a)openInWorld.com> RÃ©pondre Ã : Pharo Development List <pharo-dev(a)lists.pharo.org> Pour : Pharo Development List <pharo-dev(a)lists.pharo.org> I've updated this fix for build 40504. The following slice is read for review. SLICE-Issue-14353-Delay-refactoring-part-2---change-from-milliseconds-to-microseconds-BenComan.6 Even if you do not feel up to reviewing the code, it would be good for a few people to merge this to get a broad sample of symptoms fixed or caused. 1. Open up Monticello and get ready to load the above slice from Pharo4Inbox repository. 2. In a workspace, do "Delay stopTimerEventLoop". Ignore the #intercyclePause: message that stream by. 3. Merge slice. 4. In a workspace, do "Delay startTimerEventLoop". The stream of #interCyclePause message should fade. 5. Operate as you normally would. Test some cases that previously caused an error. cheers -ben On Thu, Feb 19, 2015 at 11:17 PM, Ben Coman <btc(a)openinworld.com> wrote: On Thu, Feb 19, 2015 at 9:50 PM, Ben Coman <btc(a)openinworld.com> wrote: 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 btw, after the cleanup done by Issue 14942, Issue 14966 can delete ten class variables from Delay. When 14942 is integrated, can 14966 be integrated very soon after that. I am basing the change of Delay to microsecond delay off 14966. cheers -ben 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

March 2, 2015

Fwd: Re: Super fast delay

by stepharo

Please help us to push ben code. -------- Message transfÃ©rÃ© -------- Sujet : Re: [Pharo-dev] Super fast delay Date : Wed, 25 Feb 2015 02:00:25 +0800 De : Ben Coman <btc(a)openInWorld.com> RÃ©pondre Ã : Pharo Development List <pharo-dev(a)lists.pharo.org> Pour : Pharo Development List <pharo-dev(a)lists.pharo.org> I've updated this fix for build 40504. The following slice is read for review. SLICE-Issue-14353-Delay-refactoring-part-2---change-from-milliseconds-to-microseconds-BenComan.6 Even if you do not feel up to reviewing the code, it would be good for a few people to merge this to get a broad sample of symptoms fixed or caused. 1. Open up Monticello and get ready to load the above slice from Pharo4Inbox repository. 2. In a workspace, do "Delay stopTimerEventLoop". Ignore the #intercyclePause: message that stream by. 3. Merge slice. 4. In a workspace, do "Delay startTimerEventLoop". The stream of #interCyclePause message should fade. 5. Operate as you normally would. Test some cases that previously caused an error. cheers -ben On Thu, Feb 19, 2015 at 11:17 PM, Ben Coman <btc(a)openinworld.com <mailto:btc@openinworld.com>> wrote: On Thu, Feb 19, 2015 at 9:50 PM, Ben Coman <btc(a)openinworld.com <mailto:btc@openinworld.com>> wrote: On Mon, Feb 16, 2015 at 4:01 PM, Holger Hans Peter Freyther <holger(a)freyther.de <mailto:holger@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 btw, after the cleanup done by Issue 14942, Issue 14966 can delete ten class variables from Delay. When 14942 is integrated, can 14966 be integrated very soon after that. I am basing the change of Delay to microsecond delay off 14966. cheers -ben 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

March 1, 2015

Re: [Pharo-dev] New Pharo Collections: Question about MultiDictionary

by stepharo

Hello Alexander May be MultiValuesDictionary would be a better name. "As You can understand from name of this collection, the multi-dictionary is dictionary which stores a pairs which looks like "key - array of values"." Don't expect that people can understand... Did you define some tests? I suggest that you check all the dictionary API and tests. Do you store an array or an ordered collection? Stef Le 1/3/15 14:39, Max Leske a Ã©crit : > >> On 01 Mar 2015, at 13:33, AlexanderBrenchev via Pharo-dev >> <pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org>> wrote: >> >> >> *Date: *1 Mar 2015 13:24:58 CET >> *From: *AlexanderBrenchev <alexzund3r(a)yahoo.com >> <mailto:alexzund3r@yahoo.com>> >> *To: *pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org> >> *Subject: **New Pharo Collections: Question about MultiDictionary* >> >> >> Greetings to everyone. Recently i started my pre-bachelor's work >> called "New >> Collections for Pharo". ( introduction to my project >> <http://forum.world.st/New-Pharo-Collections-td4794762.html> ) >> I decided to start with the MultiDictionary. There is a very basic >> prototype >> available on my project page on smalltalkhub >> <http://smalltalkhub.com/#!/~OBrenchev/NewPharoCollections >> <http://smalltalkhub.com/#%21/%7EOBrenchev/NewPharoCollections>> >> >> You can also read my post >> <http://pillarhub.pharocloud.com/hub/brenchev/duntw01nrp9hkz6a00qmi16c5> >> about this implementation on PillarHub. >> > > I took a quick look at the current API and I have one small > suggestion: I think it would make sense to add a message #at:add: (the > selector is just an example) and then use that to implement #add: like > so (again, just an example): > > add: anAssociation > self > at: anAssociation key > add: anAssociation value > > This why users are not required to use associations, which are simply > intermediate objects in many cases. If you have large collections you > donât want to create those intermediate objects. > > Cheers, > Max > >> At this point, i need your help, users and developers of Pharo! Feel >> free to >> make your suggestions about functionality of MultiDictionary that you >> need. >> Also, I'll really appreciate your suggestions about code style and in >> programming with Pharo in general. Thank you and best wishes. >> >> >> >> -- >> View this message in context: >> http://forum.world.st/New-Pharo-Collections-Question-about-MultiDictionary-… >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com <http://Nabble.com>. >> >> >> >

March 1, 2015