- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo4] Slots: API for Classes

by Marcus Denker

On 25 Jun 2014, at 14:41, Torsten Bergmann <astares(a)gmx.de> wrote: > Norbert wrote: >> Could we name it InstanceVariableSlot then? Pleeeeaaaase? > > +1 > Ok. The only downside is that there will be more to type in the class definitionâ¦ else it is actually easier. Marcus

June 25, 2014

Re: [Pharo-dev] [Pharo4] Slots: API for Classes

by Torsten Bergmann

Norbert wrote: > Could we name it InstanceVariableSlot then? Pleeeeaaaase? +1 bye T.

June 25, 2014

Re: [Pharo-dev] [Pharo4] Slots: API for Classes

by Norbert Hartl

Am 25.06.2014 um 14:22 schrieb Marcus Denker <marcus.denker(a)inria.fr>: > > On 25 Jun 2014, at 14:16, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Very nice! >> >> Next would be an example of how to specialize a slot :) >> > > Yes, the next steps are: > > - introduce abstract superclass for Slot > > (I am not yet sure: will the be âSlotâ and the default slots are âInstVarSlotâ, or do I add a > âAbstractSlotâ class and Slot stays the default? Maybe thatâs better) > I like the former better. But if you do can you please help stop that naming scheme? Could we name it InstanceVariableSlot then? Pleeeeaaaase? Norbert > - Opal needs to delegate code generation to the Slot. > > - The abstract slot generates by default reflective read/write access code > > - subclasses can override. (e.g. the default slot overrides to do pushIvar/storeIvar bytecode) > > This is the enough to do behavioural changes to simple Slots. > > After that we need to check the code for âvirtualâ slots where e.g. multiple Boolean slots are mapped to one > hidden flag ivar. > > And the of course > > - new class template (optional at first) > - Monticello support > > Marcus > >

June 25, 2014

Re: [Pharo-dev] [Pharo4] Slots: API for Classes

by Marcus Denker

On 25 Jun 2014, at 14:16, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Very nice! > > Next would be an example of how to specialize a slot :) > Yes, the next steps are: - introduce abstract superclass for Slot (I am not yet sure: will the be âSlotâ and the default slots are âInstVarSlotâ, or do I add a âAbstractSlotâ class and Slot stays the default? Maybe thatâs better) - Opal needs to delegate code generation to the Slot. - The abstract slot generates by default reflective read/write access code - subclasses can override. (e.g. the default slot overrides to do pushIvar/storeIvar bytecode) This is the enough to do behavioural changes to simple Slots. After that we need to check the code for âvirtualâ slots where e.g. multiple Boolean slots are mapped to one hidden flag ivar. And the of course - new class template (optional at first) - Monticello support Marcus

June 25, 2014

Re: [Pharo-dev] [Pharo4] Slots: API for Classes

by Tudor Girba

Very nice! Next would be an example of how to specialize a slot :) Doru On Wed, Jun 25, 2014 at 2:06 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > Already in Pharo3 all instance variables are described using meta-objects > (so called slots). > > To make it easier to access the slots, I added some simple methods to > ClassDescription on 4.0 043, > Now we can do e.g.: > > Context slots > Context allSlots > > Point hasSlotNamed: #x > Point slotNamed: #x > > e.g. the slot âxâ of Point knows how to reflectively read itself from a > point: > > (Point slotNamed: #x) read: 5@3 > > ==> 5 > > Marcus > -- www.tudorgirba.com "Every thing has its own flow"

June 25, 2014

[Pharo4] Slots: API for Classes

by Marcus Denker

Hi, Already in Pharo3 all instance variables are described using meta-objects (so called slots). To make it easier to access the slots, I added some simple methods to ClassDescription on 4.0 043, Now we can do e.g.: Context slots Context allSlots Point hasSlotNamed: #x Point slotNamed: #x e.g. the slot âxâ of Point knows how to reflectively read itself from a point: (Point slotNamed: #x) read: 5@3 ==> 5 Marcus

June 25, 2014

[pharo-project/pharo-core]

by GitHub

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

June 25, 2014

[pharo-project/pharo-core] 27b98a: 40043

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 27b98a24079dbc820baef8f7679f588653c7db57 https://github.com/pharo-project/pharo-core/commit/27b98a24079dbc820baef8f7… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-06-25 (Wed, 25 Jun 2014) Changed paths: A KernelTests.package/ClassDescriptionTest.class/instance/tests - slots/testAllSlots.st A KernelTests.package/ClassDescriptionTest.class/instance/tests - slots/testHasSlotNamed.st A KernelTests.package/ClassDescriptionTest.class/instance/tests - slots/testSlotNamed.st A KernelTests.package/ClassDescriptionTest.class/instance/tests - slots/testSlotNames.st A KernelTests.package/ClassDescriptionTest.class/instance/tests - slots/testSlots.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script43.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40043.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Slot.package/AbstractLayout.class/instance/accessing/slots.st A Slot.package/LayoutClassScope.class/instance/accessing/slots.st A Slot.package/PointerLayout.class/instance/accessing/slots.st R Slot.package/PointerLayout.class/instance/compatibility/includesName_.st M Tool-Finder.package/MethodFinder.class/instance/initialize/initialize.st R Traits.package/TClassDescription.class/instance/instance variables/checkForInstVarsOK_.st M Traits.package/TClassDescription.class/instance/instance variables/instVarIndexFor_.st M Traits.package/TClassDescription.class/instance/instance variables/instVarIndexFor_ifAbsent_.st M Traits.package/TClassDescription.class/instance/instance variables/instVarNames.st A Traits.package/TClassDescription.class/instance/slots/allSlots.st A Traits.package/TClassDescription.class/instance/slots/hasSlotNamed_.st A Traits.package/TClassDescription.class/instance/slots/slotNamed_.st A Traits.package/TClassDescription.class/instance/slots/slotNames.st A Traits.package/TClassDescription.class/instance/slots/slots.st Log Message: ----------- 40043 13400 API for slots on Classes https://pharo.fogbugz.com/f/cases/13400 http://files.pharo.org/image/40/40043.zip

June 25, 2014

Re: [Pharo-dev] is STHUB slow?

by Tudor Girba

Hi Hilaire, Glad to see you interested in Moose. A good place to start from is this blog post: http://www.humane-assessment.com/blog/moose-custom-analyses-made-easy The main idea of Moose is to allow you to map your questions on a tool. That means that you have to start from the question(s). Also, for Pharo, it is often cheaper and simpler to work directly with the Pharo code model rather than import the code into FAMIX. Cheers, Doru On Sun, Jun 22, 2014 at 9:12 AM, Hilaire Fernandes < hilaire.fernandes(a)gmail.com> wrote: > A bit off topic, I took a look yesterday to Moose, I would like to > analysis (not clear idea, more like to see what is Moose) the DrGeo > source code but I did not went very far. Any tips or pointer you could > share related to that? > > Hilaire > > Le 21/06/2014 23:51, Tudor Girba a Ã©crit : > > Indeed. The Moose jobs started to take 50% or more time since this > morning. > > > > Cheers, > > Doru > > > > > > On Sat, Jun 21, 2014 at 10:01 PM, Hilaire Fernandes > > <hilaire.fernandes(a)gmail.com > > <mailto:hilaire.fernandes@gmail.com>> wrote: > > > > I confirm, since this morning > > > > Le 21/06/2014 20:27, stepharo a Ã©crit : > > > Hi > > > > > > I'm experience strange speed problem when even loading packages. > > > Does any of you get the same? > > > > > > Stef > > > > > > > > > > -- > > Dr. Geo http://drgeo.eu > > iStoa - https://launchpad.net/istoa > > > > > > > > > > > > -- > > www.tudorgirba.com <http://www.tudorgirba.com> > > > > "Every thing has its own flow" > > -- > Dr. Geo http://drgeo.eu > iStoa - https://launchpad.net/istoa > > > -- www.tudorgirba.com "Every thing has its own flow"

June 25, 2014

[pharo-project/pharo-core]

by GitHub

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

June 25, 2014