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

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

by Damien Pollet

### Here's what I've been up to since the last WhatsUp: Not much (yay burnout), but started reading code again (PPM, FileTreeâ¦) > ### What's next, until 2015-03-15 (*): > - hacking on a new FileTree reader/writer that follows the latest cypress design, and will allow to simplify the current implementation - this in order to port a couple libs over from VW (small ones mostly, but Andres' Assessments would be nice eventually) -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

March 2, 2015

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

by Sean P. DeNigris

Marcus Denker-4 wrote >> Could this be used in stead of Spec Adapters? That would probably require >> MetaLinkCollection. > > We need to be careful using these mechanismsâ¦ it is powerful but you can > build very hard > to understand systems when using it too much... Yes, IMHO opinion, this feature should be thought of like #instVarNamed:put: - awesome & powerful when you /really/ need it (usually deep within the IDE itself), but an anti-pattern for general use ----- Cheers, Sean -- View this message in context: http://forum.world.st/Reflectivity-Tiny-progress-of-the-day-MetaLink-tp4808… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 2, 2015

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

by Clara Allende

Le 2 mars 2015 05:38, "Marcus Denker" <marcus.denker(a)inria.fr> a Ã©crit : > > Hi, > > The tiny progress of today: I reviewed the code for the MetaLink from Claraâs Breakpoints > and added it to Pharo4. Yay! There was also one extension method in Slot to make work with those, have you seen it? 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

Flattr

by phil＠highoctane.be

I guess we should add a button like this to the Pharo website. https://flattr.com/ Phil

March 2, 2015

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

by Clara Allende

Le 2 mars 2015 05:58, "Marcus Denker" <marcus.denker(a)inria.fr> a Ã©crit : > > > > On 02 Mar 2015, at 09:51, phil(a)highoctane.be wrote: > > > > Is there any background material one can read about these things? > > > > I fear only my PhDâ¦ I never published a paper about the whole thing (huge mistakeâ¦). > > http://scg.unibe.ch/archive/phd/denker-phd.pdf > > The problem is that this tells the story including the first steps that where wrong (based on byte code > and too complex). Chapter 5 is about the final model, chapter 6 discusses meta-recursion. > So one could read 2, the intro of 3 + 4, and then 5. > > I will write a real paper about the version in Pharo when it is done. Specifically for the breakpoints there is my paper, and my blog (which I should update at some point): clariallende(a)wordpress.com In both I do a small introduction to Reflectivity, and explain how we use it for the breakpoints. Maybe you can start from there and then follow up with Marcus' thesis. > > Marcus > >

March 2, 2015

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

by Marcus Denker

> On 02 Mar 2015, at 11:04, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Could this be used in stead of Spec Adapters? That would probably require MetaLinkCollection. > We need to be careful using these mechanismsâ¦ it is powerful but you can build very hard to understand systems when using it too much... > Peter > > On Mon, Mar 2, 2015 at 9:58 AM, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: > > > On 02 Mar 2015, at 09:51, phil(a)highoctane.be <mailto:phil@highoctane.be> wrote: > > > > Is there any background material one can read about these things? > > > > I fear only my PhDâ¦ I never published a paper about the whole thing (huge mistakeâ¦). > > http://scg.unibe.ch/archive/phd/denker-phd.pdf <http://scg.unibe.ch/archive/phd/denker-phd.pdf> > > The problem is that this tells the story including the first steps that where wrong (based on byte code > and too complex). Chapter 5 is about the final model, chapter 6 discusses meta-recursion. > So one could read 2, the intro of 3 + 4, and then 5. > > I will write a real paper about the version in Pharo when it is done. > > Marcus > > >

March 2, 2015

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

by Peter UhnÃ¡k

Could this be used in stead of Spec Adapters? That would probably require MetaLinkCollection. Peter On Mon, Mar 2, 2015 at 9:58 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > On 02 Mar 2015, at 09:51, phil(a)highoctane.be wrote: > > > > Is there any background material one can read about these things? > > > > I fear only my PhDâ¦ I never published a paper about the whole thing (huge > mistakeâ¦). > > http://scg.unibe.ch/archive/phd/denker-phd.pdf > > The problem is that this tells the story including the first steps that > where wrong (based on byte code > and too complex). Chapter 5 is about the final model, chapter 6 discusses > meta-recursion. > So one could read 2, the intro of 3 + 4, and then 5. > > I will write a real paper about the version in Pharo when it is done. > > Marcus > > >

March 2, 2015

[pharo-project/pharo-core] be23e3: 40524

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: be23e3914c2b3be0ee661b5723bb01c56a16dbfb https://github.com/pharo-project/pharo-core/commit/be23e3914c2b3be0ee661b57… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-03-02 (Mon, 02 Mar 2015) Changed paths: M Kernel.package/CompiledMethod.class/class/instance creation/headerFlagForEncoder_.st M Kernel.package/CompiledMethod.class/instance/debugger support/prepareForSimulationWith_.st M Refactoring-Core.package/RBRenameInstanceVariableRefactoring.class/instance/initialize-release/rename_to_in_.st R Refactoring-Tests-Core.package/RBRenameInstanceVariableTest.class/instance/tests/testRenameInstVarAccessorsReferences.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script523.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script524.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40523.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40524.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40524 14988 failing test testErrorCodeNotFound https://pharo.fogbugz.com/f/cases/14988 15002 Rename instance variable is broken https://pharo.fogbugz.com/f/cases/15002 http://files.pharo.org/image/40/40524.zip

March 2, 2015

[pharo-project/pharo-core]

by GitHub

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

March 2, 2015

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

by Marcus Denker

> On 02 Mar 2015, at 09:51, phil(a)highoctane.be wrote: > > Is there any background material one can read about these things? > I fear only my PhDâ¦ I never published a paper about the whole thing (huge mistakeâ¦). http://scg.unibe.ch/archive/phd/denker-phd.pdf The problem is that this tells the story including the first steps that where wrong (based on byte code and too complex). Chapter 5 is about the final model, chapter 6 discusses meta-recursion. So one could read 2, the intro of 3 + 4, and then 5. I will write a real paper about the version in Pharo when it is done. Marcus

March 2, 2015