- Pharo-dev - lists.pharo.org

[Pharo-project] Fwd: [squeak-dev] ANN: NanoTraits v0.5
by StÃ©phane Ducasse Dec. 22, 2009

Dec. 22, 2009

this is interesting. I had on my todo to look at the old implementation of andreas since years. Adrian it would be really interesting to check because having a smaller/with less impact traits implementation would be cool. Stef > > My experiments with a simpler traits implementation are starting to bear results. Attached a version of NanoTraits which is the smallest implementation of traits that I could come up with. Making it loadable inside a current trunk image has been a bit of a challenge since it needs to operate side-by-side with the existing traits during load (apologies for the various isKindOf:'s), but it seems to work fairly well now (fingers crossed). There are few differences to the Berne trait implementation including: > > - TraitDescription is a subclass of ClassDescription. This is the main simplification since it avoids creating a dual trait/class hierarchy. It comes at the "cost" of having potentially support for instance variables in traits (i.e., stateful traits) but since this isn't exposed there is very little actual overhead. > > - NanoClassTrait is the class of NanoTrait (i.e., the same meta structure that classes have). Since this models exactly the structure that classes have, it makes browser integration significantly simpler (NanoTraits would work fine in 3.8 for example without changing browsers etc) and allows us to remove the (now unecessary) additional tool support. > > - Methods used from other traits retain a "method home" reference so that for any method in a class you can tell whether it was defined locally or in some other trait. This makes several things *a lot* easier and will allow us to get rid of all the localSelectors stuff in ClassDescription in the next pass (Igor - this gives you the information where a method is from without poking in other places; just ask i.e., (ClassDescription>>#addSelectorSilently:withMethod:) methodHome ==> TAccessingMethodDictDescription) > > - Some previously invalid trait composition are now valid, in particular T - {#x} - {#y} (meaning T- {#x. #y}) as well as T @ {#x->#y} @ (#a -> #b} (meaning T @ { #x -> #y. #a -> #b}. > > - You can't mix Berne and Nano traits. If you try it, things will blow up (incompatible internals). > > - You can't mix Berne and Nano traits tests. I don't know why but if you run them at the same time things go wrong. > > To install NanoTraits: > * Load NanoTraits-Kernel.st > * Load NanoTraits-Tests.st > * Load NanoTraits-Extensions.cs > * Run the NanoTraits-Tests > * (assuming all tests are green) execute: NanoTraits install. > > This will make NanoTraits the default traits implementation and convert any existing traits. I've successfully played with Nile (the only other traits stuff I was aware about besides the class kernel which is a bit difficult to experiment with) but from what I can tell everything should work just fine. > > The one extra thing I'm seriously considering after our recent discussions is to change NanoTraits to actually use mixins to implement traits composition. What this would mean is that instead of adding trait methods to a class directly, they would be added to a (hidden) superclass. Composition rules would be unaffected by this change but it would solve the issue of trait methods messing up the methods *actually* defined in a class, showing a seven times when looking for implementors and more. > > Consider this my holiday gift to the community :-) > > Cheers, > - Andreas > > >

1 0

[Pharo-project] [update 1.1] #11111
by Marcus Denker Dec. 22, 2009

Dec. 22, 2009

11111 ----- Issue 1646: SLICE-PreferencesReferencesRemovalPart2 * remove all remaining Preferences references * also fix a DiffMorph bug introduced by previous SLICE-PreferencesReferencesRemovalPart1 (send of #setting instead of #settings) Thanks, Alain! Issue 1649: Workspace cannot print object whose class does not inherit from Behavior Thanks to Adrian Kuhn

2 2

[Pharo-project] Name: SLICE-allowUnderscoreAssignmentFix-AlainPlantec.1
by StÃ©phane Ducasse Dec. 21, 2009

Dec. 21, 2009

I lost track about this change. Alain should I integrate it? Stef Name: SLICE-allowUnderscoreAssignmentFix-AlainPlantec.1 Author: AlainPlantec Time: 4 December 2009, 5:15:50 pm UUID: f1c44699-23e8-46b5-a7d2-27db7b31c14e Ancestors: Dependencies: Compiler-AlainPlantec.147 make the allowUnderscoreAssignment preference work

2 2

[Pharo-project] nil DNU #size
by csrabak＠bol.com.br Dec. 21, 2009

Dec. 21, 2009

In PharoDev (PharoCore1.0rc1 Latest update: #10502) evaluting this expression: nil size. "Leads to a DNU Instances of UndefinedObject are not indexable" For some reason, at some moment the #size overload of the Object>>size was taken off (w.r.t. Squeak). This is weird because a lot of protocols that would work flawlessly (Null object pattern) now have to be patched for ifNil:[] or ifNotNil:[]. Also, Pharo coming from Squeak inheritance keeps the Object>>size implementation as: size "Primitive. Answer the number of indexable variables in the receiver. This value is the same as the largest legal subscript. Essential. See Object documentation whatIsAPrimitive." <primitive: 62> self class isVariable ifFalse: [self errorNotIndexable]. ^ 0 The version comment is "di 3/29/1999" so this is very old indeed. This particular decisions is now making even the Luka's suggestion to do Gofer update itself to fail with a MNU. . . Before I open an issue, I would like to know from the elder folks at the Pharo project if the decision to make this change in the accessing protocol of UndefinedObject was deliberated or we just stumbled a new bug? -- Cesar Rabak

1 0

[Pharo-project] 1.1unstable Gofer gofer update -> break
by StÃ©phane Ducasse Dec. 21, 2009

Dec. 21, 2009

Hi lukas I wanted to load the latest version of Gofer (with Fetch :)) in pharo so I did Gofer gofer update and I got a GoferReference with a name = nil -> breaks If you have a look let me know but enjoy the moutains Stef PS: here we got snow (10 cm) so this is fun to drive cars on empty parkings :)

3 4

[Pharo-project] Update to current in one go?
by Stan Shepherd Dec. 21, 2009

Dec. 21, 2009

-- View this message in context: http://n2.nabble.com/Update-to-current-in-one-go-tp4199609p4199609.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 2

[Pharo-project] I will do a quick release now.
by StÃ©phane Ducasse Dec. 21, 2009

Dec. 21, 2009

1 0

[Pharo-project] Issue 1634: Object allSubInstances slooooow
by Stan Shepherd Dec. 21, 2009

Dec. 21, 2009

Pharo image: Pharo | Pharo-core PharoCore1.0rc1 Latest update: #10502 VM: unix - i686 - linux-gnu - Pharo0.1 of 16 May 2008 [latest update: #10074] Steps to reproduce: 1.[Object allSubInstances size inspect] timeToRun 375479 (6 minutes) with fix [Object allSubInstances size inspect] timeToRun 22335 (22 seconds) Attached treats Object as a special case, and takes advantage of primitive in SystemNavigation>>allObjectsDo: Test also attached (it's slow without the mod) http://code.google.com/p/pharo/issues/detail?id=1634 http://code.google.com/p/pharo/issues/detail?id=1634 http://n2.nabble.com/file/n4189848/BehaviorTest-testAllObjectsPerformance.st BehaviorTest-testAllObjectsPerformance.st http://n2.nabble.com/file/n4189848/Behavior-allSubInstancesDo.st Behavior-allSubInstancesDo.st http://n2.nabble.com/file/n4189848/Behavior-allSubInstancesDo.st Behavior-allSubInstancesDo.st -- View this message in context: http://n2.nabble.com/Issue-1634-Object-allSubInstances-slooooow-tp4189848p4… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

5 9

[Pharo-project] SUnit
by Torsten Bergmann Dec. 21, 2009

Dec. 21, 2009

>identified two requirements I would add another one: if necessary keep your additions simple. As of today SUnit is a simple framework everybody is able to understand and therefore able to use. Thx T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

2 1

[Pharo-project] About projects with Metacello
by Mariano Martinez Peck Dec. 21, 2009

Dec. 21, 2009

Hi folks. Now that I am starting to write some configurations, I realized that we have a "change of concept" with Metacello. With Gofer or Installer (someone tell me if I am wrong) we are use to manage projects that are a certain repository of squeaksource or similar. And then we have the packages. So, for example we are talking about the RefactoringBrowser, you have: www.squeaksource.com/rb and the packages AST-Core, Refactoring-Core and Refactoring-Spelling. Then there is the project OB where you have also OB-Refactory and OB-Regex for example. At first, of course, I thought to have one ConfigurationOf per project. I mean, map one to one. But now...I was wondering that I can have a ConfigurationOfRefactoring for example, that can deals with ALL the things related to RB. In this case AST-Core, Refactoring-Core and Refactoring-Spelling from rb repo and OB-Refactory and OB-Regex from OB repo....and see all of them like a project. What do you think ? Do you have any thoughts with this? pors and cons? I would like to listen opinions. Cheers, Mariano

7 13