December 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] Where does Regex-Core and friends live
by Dale Henrichs Dec. 10, 2010

Dec. 10, 2010

I am porting the latest Regex to GemStone and in the interest of Pharo compatibility, I found Regex-Core and and Regex-Tests-Core in the Pharo repository. In loading Regex-Tests-Core I found some compile errors (doubled '.', a common porting problem) in RxParserTest>>testTranslatingMatchesUsing and RxParserTest>>test, but I don't know where the home repository (other then Pharo) resides, where I could submit my updates. I've got a GemSource repository, but I'm actually hoping (haven't run tests yet:) that I will be able to use Regex-Core without making any GemStone-specific changes ... Dale

4 12

Re: [Pharo-project] Issue 3254 in pharo: [Repackage] "Regular expressions" should be well structured
by pharo＠googlecode.com Dec. 10, 2010

Dec. 10, 2010

Updates: Cc: marcus.denker Comment #10 on issue 3254 by Torsten....(a)astares.de: [Repackage] "Regular expressions" should be well structured http://code.google.com/p/pharo/issues/detail?id=3254 So stef integrated the latest version available on lukas repository. Ready for inclusion in 1.2 then?

1 3

Re: [Pharo-project] Issue 3263 in pharo: Add a followingBytecode to InstructionStream
by pharo＠googlecode.com Dec. 10, 2010

Dec. 10, 2010

Comment #2 on issue 3263 by siguctua: Add a followingBytecode to InstructionStream http://code.google.com/p/pharo/issues/detail?id=3263 it would be nice to have a test, which covering this refactoring

1 0

[Pharo-project] Issue 3399 in pharo: SystemNavigation should directly use CompiledMethods instead of their wrapper where its appropriate
by pharo＠googlecode.com Dec. 10, 2010

Dec. 10, 2010

Status: Accepted Owner: siguctua Labels: Milestone-1.3 New issue 3399 by siguctua: SystemNavigation should directly use CompiledMethods instead of their wrapper where its appropriate http://code.google.com/p/pharo/issues/detail?id=3399 SystemNavigation exposing the currently running system to tools. This means that it is always operates with objects located in system in its current state, not somewhere outside. In own turn this means, that it should not use any indirections or wrapping real compiled methods with method references, but instead should pass them directly to development tools. For navigating remote systems or any other kinds of indirection, one could create a subclass of SystemNavigation, which then can expose the remote system internal using compiled method references, classes and other proxies like that. This also means that we should analyze and impose the required protocol which both CompiledMethod and MethodReference(s) should comply with. As well as Classes and MetaClasses, Packages and organization.

1 0

[Pharo-project] Creating temporary classes for testing
by Sean P. DeNigris Dec. 10, 2010

Dec. 10, 2010

I was playing with creating temporary classes for testing in a separate SystemDictionary, so I don't have to worry about removing them. But I'm a little beyond the boundary of my knowledge (although I stepped through it in the debugger and it seemed pretty straight forward). Are there any hidden side-effects/implications of the following? Specifically, after the SystemDictionary is garbage collected, is the system exactly the same as it was before the code was run? It seems like a better approach than creating them in the global namespace and cleaning up. testingEnvironment := SystemDictionary withOrganizer: SystemOrganizer new. ClassBuilder new name: #AClassForTesting inEnvironment: testingEnvironment subclassOf: Object type: Object typeOfClass instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'TemporaryTesting'. newClass := (testingEnvironment at: #AClassForTesting). newClass compile: 'greeting ^ ''hello there''' classified: 'greeting'. newClass new greeting. "Returns 'hello there'" Thanks. Sean -- View this message in context: http://forum.world.st/Creating-temporary-classes-for-testing-tp3080408p3080… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

4 8

Re: [Pharo-project] Fuel - a fast object deployment tool
by Martin Dias Dec. 10, 2010

Dec. 10, 2010

Hi Colin Another thing to consider are the clusters. I think they are good because they avoid a lot of overhead. Following the example used in the slides, for serializing N rectangles, it writes: - in vertexes section: 'Rectangle' 'origin' 'corner' N - in edges section: 2*N indexes (references to the origin and corner points) Without clustering, I think each rectangle stored should have some header to say that its an instance of Rectangle. Martin On Fri, Dec 10, 2010 at 11:03 AM, Tristan Bourgois <tristan.bourgois(a)gmail.com> wrote: > >> Hi Martin, >> >> Looks very interesting. Reading the material you posted, the question >> that jumps out at me is this: from the benchmarks, it's clear that >> materializing is faster than serializing, but it's not clear why. How >> does separating the nodes from the edges of the object graph make >> materializing faster? >> >> Thanks, >> >> Colin > > Hi! > > Separate the nodes from the edges of the object permit during the > serialization > to pass only one time on the byte code. > So first we pass on the node so we recreate the objects/nodes and second > when > we pass on the edges we recreate the links between the objects. > > I hope I answered your question :) > > Tristan >

1 0

[Pharo-project] Why was the old Editor Functionality Removed?
by Lukas Renggli Dec. 10, 2010

Dec. 10, 2010

I wonder why the old editor functionality was removed instead of being deprecated until the next release like this is normally done? It is extremely difficult to get any GUI related stuff ported, because the packages cannot simply be loaded. One has to fix part of the package in the old image, and part of the package in the new image. One wrong method, and everything blows up irreversibly. I spent the whole afternoon trying to get OB, Shout and eCompletion working. OB and Shout kind of work (thanks to the preparations in the PharoTaskForces), but they are still subtly broken. eCompletion is very hard to get working. The idea of making completion part of the ToolSet doesn't help at all, the patch now just moved from Morphic to the StandardToolSet class. I am frustrated and give up, I revert back to Pharo 1.1. Lukas -- Lukas Renggli www.lukas-renggli.ch

8 15

[Pharo-project] about cloud in pharo
by stephane ducasse Dec. 10, 2010

Dec. 10, 2010

Hi guys When I see that. I would really like to see how we can create something around the cloud. We have a lot of assets. Does anybody have some interest bootstrapping a business around that? Today http://heroku.com/ were bought by Salesforce for over 200 million (http://techcrunch.com/2010/12/08/breaking-salesforce-buys-heroku-for-212-mi…) Stef

9 10

[Pharo-project] Cog+NativeBoost @ Mac OS
by Igor Stasenko Dec. 10, 2010

Dec. 10, 2010

Hello, since recently i got access to macs, i were finally able to add NB support for Mac OS. I built the Cog VM with NativeBoost plugin , which you can download at NativeBoost project page [1]. At image side you just load NativeBoost-Installer package and then evaluate: NBInstaller install. Should i also build Squeak VM with NB plugin, or i could stick with Cog? :) [1] http://code.google.com/p/nativeboost/downloads/list -- Best regards, Igor Stasenko AKA sig.

3 6

[Pharo-project] Some Tests failing in 1.2
by Luc Fabresse Dec. 10, 2010

Dec. 10, 2010

Hi all, 6 tests in SystemNavigationTest and SystemNavigationOnNewlyCreatedEnvironementTest are failing in 1.2 This is because of the introduction of SourcedMethodReference. I already speak about this problem here: http://forum.world.st/About-SourcedMethodReference-td3035187.html SourcedMethodReference>>= must not be based on identity (==) because it prevents to have multiple SourcedMethodReference pointing to the same CompiledMethod. And we need that because each tools will use different SourcedMethodReference. IMHO, SourcedMethodReference are just proxies and we don't care of their identity. I made these 6 tests pass by: -replacing MethodReference by SourcedMethodReference in SystemNavigationTest and al... -modifying the equality method of SourcedMethodReference: SourcedMethodReference>>= anotherMethodReference ^ (super = anotherMethodReference) and: [ (self timeStamp = self timeStamp) and: [ self sourceCode = self sourceCode ]] I have no idea of the impact of this change for the SourcedMethodReference stuff point of view. Written here: http://code.google.com/p/pharo/issues/detail?id=3398 #Luc

1 0