- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] super initialize

by Norbert Hartl

> Am 26.06.2014 um 18:48 schrieb stepharo <stepharo(a)free.fr>: > > >> When you create a new instance with #new automatically >> #initialize is sent. >> >> The default #initialize is provided in ProtoObject at >> the highest level of the class hierarchy (doing nothing). >> >> If you look deeper in the hierarchy you will notice that >> >> - some subclasses of Object override the #initialize >> method and call "super initialize" >> - some subclasses of Object override the #initialize >> method without calling "super initialize" >> >> No problem at the moment as there is no initialization >> done in Object or ProtoObject at the current point in >> time. >> >> But the question is should we care if there may be >> in the future? > I prefer to have a super call for consistency reasons. Igor jokes me usually on that. I'm on your side. Screw Igor :) Norbert > Now there should not be an initialize in ProtoObject and Object in the future. > > So which ones > > - some subclasses of Object override the #initialize > method without calling "super initialize" > > > > Stef >> >> Thx >> T. > >

June 26, 2014

Re: [Pharo-dev] super initialize

by stepharo

> When you create a new instance with #new automatically > #initialize is sent. > > The default #initialize is provided in ProtoObject at > the highest level of the class hierarchy (doing nothing). > > If you look deeper in the hierarchy you will notice that > > - some subclasses of Object override the #initialize > method and call "super initialize" > - some subclasses of Object override the #initialize > method without calling "super initialize" > > No problem at the moment as there is no initialization > done in Object or ProtoObject at the current point in > time. > > But the question is should we care if there may be > in the future? I prefer to have a super call for consistency reasons. Igor jokes me usually on that. Now there should not be an initialize in ProtoObject and Object in the future. So which ones - some subclasses of Object override the #initialize method without calling "super initialize" Stef > > Thx > T. > > > >

June 26, 2014

Re: [Pharo-dev] Pharo and Amber relationship

by stepharo

On 26/6/14 10:10, Torsten Bergmann wrote: > Hi, > > as I read somewhere that Amber want to stay compatible > with Pharo it is important. > (at least with the core classes) I wonder > how this compatibility is measured/enforced these days. Difficult. > > Are there tools to exchange code between the two? > > I also wonder if what would be necessary to run Amber on > Java Nashorn (a JS engine that comes with the JDK 8). > Could serve as a horse to also run on JVM... May be we should stop developing in our lovely language and jump in JS. It would solve many problems and open a lot more. But seriously after the Java wave.... > > Why I'm asking: I think one of our goals should be to > make Pharo more widely usable to not end up as an island. We daily try to improve our system but this is not easy. > > If Pharo and Amber stay compatible to a certain amount > Amber could open the door for Pharo to other target platforms > (browser, mobile devices, other language runtimes) as > JS is available nearly everywhere. Running Pharo on JS VM would be interesting too. Stef

June 26, 2014

Re: [Pharo-dev] evicted zombie process from run queue

by stepharo

> Esteban wrote: >> Other frameworks use a datasource design (like cocoa, swtâ¦ and basically all the serious frameworks I know about). can you give a pointer? >> and no, we do not have a default design for this kind of big components (a serious absence, IMO). > Serious absence indeed. > > Stephan >

June 26, 2014

Re: [Pharo-dev] about ~=

by stepharo

;) On 26/6/14 12:46, Nicolas Cellier wrote: > $! is not classified as a binary character right now, is it? > Of course it's possible but I'd just say why this particular symbol? > It does not look mathematical either. Or do you love C/C++ so much? > > Note that ~= has same meaning in Matlab. > > There are other possibilities like /= or <> (Fortran 95, ADA), even > the long form =/=. > > But frankly, I don't buy this kind of change, for the sake of looking > like some {} language, making such a deep change is overkill. > > In any case, a big -1 for != >

June 26, 2014

How to get started with Git and Pharo?

by stepharo

Hi I do not know the dif between git file tree, file tree.... and I would like to know how to get started with git in Pharo? What should I read? Stef

June 26, 2014

Re: [Pharo-dev] about ~=

by Richard Sargent

Esteban A. Maringolo wrote > If one thing confuses people in that realm is non arithmetic precedence: > Eg. 2 + 3 * 4 = 20 instead of the "expected" 14. > > And we're not going to change that either. It's not worthy, and I > doubt if it is possible at all. I'm probably late to the party with this reply. The primary reason for not changing this is that it would be incorrect. It comes down to intrinsic versus extrinsic meaning. A multiple operator has an intrinsic meaning: it means multiple. But a message name does not have intrinsic meaning (other than it is a good idea to have the name represent what it does). The meaning of a message is determined by the receiver. e.g. if PetitParser defines #* to mean "0 or more repetitions", what happens when someone has decided that it should be evaluated before #+? Message sending precedence can only be defined in terms of the type of message: unary, binary (or infix), and keyword, since the interpretation of the message is the receiver's responsibility, not the compiler's. -- View this message in context: http://forum.world.st/about-tp4764892p4765070.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 26, 2014

[pharo-project/pharo-core]

by GitHub

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

June 26, 2014

[pharo-project/pharo-core] a4c40a: 40047

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: a4c40ae92c67b2d4d63635d89dac0f7bbaa214d5 https://github.com/pharo-project/pharo-core/commit/a4c40ae92c67b2d4d63635d8… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-06-26 (Thu, 26 Jun 2014) Changed paths: A Kernel.package/Object.class/instance/introspection/readSlotNamed_.st A Kernel.package/Object.class/instance/introspection/readSlot_.st A Kernel.package/Object.class/instance/introspection/writeSlotNamed_value_.st A Kernel.package/Object.class/instance/introspection/writeSlot_value_.st A Kernel.package/Object.class/instance/introspection/writeToSlot_of_.st A KernelTests.package/ObjectTest.class/instance/tests - introspection/testReadSlot.st A KernelTests.package/ObjectTest.class/instance/tests - introspection/testReadSlotNamed.st A KernelTests.package/ObjectTest.class/instance/tests - introspection/testWriteSlotNamedValue.st A KernelTests.package/ObjectTest.class/instance/tests - introspection/testWriteSlotValue.st A KernelTests.package/ObjectTest.class/instance/tests - introspection/testWriteToSlotOf.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script47.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40047.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Slot.package/InstanceVariableSlot.class/class/cleanup/resetIvarSlots.st M Slot.package/Slot.class/instance/meta-object-protocol/write_to_.st M Slot.package/Slot.class/instance/private/internalWrite_to_.st Log Message: ----------- 40047 13412 add Helper: resetIvarSlots https://pharo.fogbugz.com/f/cases/13412 13414 Keyboard shortcuts in Nautilus stopped working https://pharo.fogbugz.com/f/cases/13414 13418 reflective API for Slots on Object https://pharo.fogbugz.com/f/cases/13418 http://files.pharo.org/image/40/40047.zip

June 26, 2014

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

by Marcus Denker

On 25 Jun 2014, at 14:06, 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 > As Camille noted, we need a different API on the Objects to read and write slots. We came up with: #readSlot: #readSlotNamed: #writeSlot:value: #writeSlotNamed:value: #writeToSlot:of: (this is what the compiler generates to reflectively write a slot) e.g. 5@3 readSlot: (Point slotNamed: #x) 5@3 writeSlotNamed: #x value: 7 This is in the issue tracker: https://pharo.fogbugz.com/f/cases/13418/reflective-API-for-Slots-on-Object Marcus

June 26, 2014