- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [ANN 1.2] prebuilt core 1.2 final
by Marcus Denker March 20, 2011

March 20, 2011

>> >> Yes, but it was not done for 1.2 and 1.2 is *finished*. >> >> If we want to do that, we need to do that *not after the release is released* >> but before. This whole thing just shows that "I only look at 1.2 when it is released" *DOES NOT WORK*. 1.2 Core was "Release Canditate" for *two months*. Release Canditate means "this will be released *unchanged* if no problems are found". So isn't *that* the point to do things that could need a fix in the release? I am really tempted to declare 1.3 stable now and abandon any concept of release, as it's a complete waste of time. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

3 2

[Pharo-project] Cog Unix/Cog MacOS now should not crash while running Pharo tests
by Igor Stasenko March 19, 2011

March 19, 2011

.. of course it needs to be verified. Cog Mac Carbon [1] build past #10 and Cog Unix [2] build past #46 using latest Eliot's update. Note that built VMs are not MT-enabled (using a CoInterpreter class instead of CoInterpreterMT). (we should decide if we create new jobs on Hudson for MT-enabled VMs or just change existing ones to use new class). Please, go to Hudson, download and play with new VMs. Let me know if there's everything alright. [1] https://pharo-ic.lille.inria.fr/hudson/view/Cog/job/Cog%20Mac%20Carbon/ [2] https://pharo-ic.lille.inria.fr/hudson/job/Cog%20Unix/ -- Best regards, Igor Stasenko AKA sig.

1 0

[Pharo-project] Woohoo.. Cog not crashing anymore
by Igor Stasenko March 19, 2011

March 19, 2011

Good news everyone (c) :) Currently i am the only happily owner of JIT VM , which no longer crashing while running all Pharo tests... I will prepare new configs and publish them soon. P.S. @Henrik Your MethodContextTest>>testClosureRestart are failing. P.P.S. @Lukas , i made small modifications to your HudsonBuildTools, see an attached changeset. First i introducing a counter, which allows to arrange files in order they run (it is important to know which tests are run before, because it could be possible that crash were caused by combination of tests), and also added stream flushing before running each test case, so if VM will crash, we will observe a half-populated file. So, on Hudson, instead of running: HDTestReport runCategories: Smalltalk organization categories one should run : HDTestReport resetCounter. HDTestReport runCategories: Smalltalk organization categories Please let me know if you willing to integrate this changeset. Maybe in separate subclass, but we should be prepared that tests could crash VM (because we will be testing newly built VMs), so it is important to know which test were causing failure. P.P.S. On second thought, i thinking that it could be made even more direct by overwriting a 'runningCase.txt' file each time we running test.. P.P.P.S. It would be nice to integrate stdout output into images and make stdout == Transcript in headless mode, so running any image in headless mode by default will print stuff on stdout, so we don't need to worry about flushing files etc and can easily see progress via Hudson console output view. -- Best regards, Igor Stasenko AKA sig.

1 0

[Pharo-project] Issue 3832 in pharo: allOverriddenMethods returns all the overridden methods not just the one of the package
by pharo＠googlecode.com March 19, 2011

March 19, 2011

Status: Accepted Owner: stephane...(a)gmail.com New issue 3832 by stephane...(a)gmail.com: allOverriddenMethods returns all the overridden methods not just the one of the package http://code.google.com/p/pharo/issues/detail?id=3832 PackageInfo allInstances first allOverriddenMethods returns all the overridden methods.

1 0

[Pharo-project] Method expressed as symbol, used as argument
by DougEdmunds March 19, 2011

March 19, 2011

It was pointed out that given an instance method MyClass >> doSomething that MyClass do: [:each | each doSomething]. can be expressed as MyClass do: #doSomething. Can someone suggest something to read that explains the usage of # here (#doSomething), the relation of methods to symbols, etc. Trying to wrap my head around it. Thanks. -dae -- View this message in context: http://forum.world.st/Method-expressed-as-symbol-used-as-argument-tp3388864… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

7 6

[Pharo-project] SUnit and Tests inheritance or 'Data' injection
by Stefan Marr March 19, 2011

March 19, 2011

Hi: I have a design problem with my test cases. In my benchmark suite I have a runner class that controls how benchmarks are executed. Now I want to subclass it to provide a runner that automatically finds a reasonable number of iterations for microbenchmarks. Thus, it will first measure the time of a first run and then double the number of iterations until it has some like at least 300ms runtime. Ok, thats the domain design, now the question how do I test that hierarchy with SUnit? It seems like my test hierarchy that parallels the domain hierarchy is not actually working like I would expected it. Thus, my basic test class implements some 9 tests, and my auto-sizing test-class adds two more test. However, when I run the tests, only 11 tests are executed and not 2*9 + 2 = 20 tests. Is there something I am missing? Is there a way that I can force SUnit to also execute the tests of the superclass? Or, something that would actually be nice, is there a way that I can automatically parameterize my tests with data? Then I would not need to us subclassing in my test hierarchy, but could just tell the basic tests to run with all the different runner classes, and for the autosizing runners, I can just run additional tests. Thanks Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525 -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

4 5

[Pharo-project] Issue 3534 in pharo: LargePositiveInteger(Object)>>error
by pharo＠googlecode.com March 19, 2011

March 19, 2011

Status: Accepted Owner: Torsten....(a)astares.de CC: eliot.miranda Labels: Milestone-1.2 New issue 3534 by Torsten....(a)astares.de: LargePositiveInteger(Object)>>error http://code.google.com/p/pharo/issues/detail?id=3534 It was already discussed here: http://lists.gforge.inria.fr/pipermail/pharo-project/2011-January/039447.ht… but I havent found an issue yet. From time to time I now also get the following error when opening the world menu (the menu with the help icon is red crossed due to display error) I use the latest prebuilt Cog VM Here is the stack: VM: Win32 - IX86 - 5.1 - Croquet Closure Cog VM [CoInterpreter VMMaker-oscog.45] Image: Pharo1.2beta [Latest update: #12297] LargePositiveInteger(Object)>>error: Receiver: 4278190081 Arguments and temporary variables: aString: 'MessageNotUnderstood: LargePositiveInteger>>pixelValueForDepth:' Receiver's instance variables: 4278190081 [:err :rcvr | | errCtx errMorph | errCtx := thisContext. [errCtx := errCtx sender. [errCtx notNil and: [errCtx receiver isMorph not]] whileTrue: [errCtx := errCtx sender]. errCtx ifNil: [^ self handleFatalDrawingError: err]. errMorph := errCtx receiver. errMorph hasProperty: #errorOnDraw] whileTrue. errMorph setProperty: #errorOnDraw toValue: true. rcvr error: err] in WorldState>>displayWorldSafely: Receiver: a WorldState Arguments and temporary variables: err: 'MessageNotUnderstood: LargePositiveInteger>>pixelValueForDepth:' rcvr: 4278190081 errCtx: ToggleMenuItemMorph>>drawIcon:on:in: errMorph: a ToggleMenuItemMorph(17825792)'Help' Receiver's instance variables: hands: an Array(a HandMorph(843055104)) viewBox: 0@0 corner: 1672@982 canvas: a FormCanvas on: DisplayScreen(1672x982x32) damageRecorder: a DamageRecorder stepList: a Heap(StepMessage(#stepAt: -> an OverflowRowMorph(157810688))(an Ove...etc... lastStepTime: 105085 lastStepMessage: nil lastCycleTime: 105055 alarms: a Heap() lastAlarmTime: 105085 menuBuilder: a PragmaMenuBuilder BlockClosure>>cull:cull: Receiver: [:err :rcvr | | errCtx errMorph | errCtx := thisContext. [errCtx := errCtx sender. [err...etc... Arguments and temporary variables: firstArg: 'MessageNotUnderstood: LargePositiveInteger>>pixelValueForDepth:' secondArg: 4278190081 Receiver's instance variables: outerContext: WorldState>>displayWorldSafely: startpc: 73 numArgs: 2 [:ex | errorHandlerBlock cull: ex description cull: ex receiver] in BlockClosure>>ifError: Receiver: [aWorld displayWorld] Arguments and temporary variables: errorHandlerBlock: MessageNotUnderstood: LargePositiveInteger>>pixelValueForDep...etc... ex: [:err :rcvr | | errCtx errMorph | errCtx := thisContext. [errCtx := errCt...etc... Receiver's instance variables: outerContext: WorldState>>displayWorldSafely: startpc: 66 numArgs: 0 BlockClosure>>cull: Receiver: [:ex | errorHandlerBlock cull: ex description cull: ex receiver] Arguments and temporary variables: anArg: MessageNotUnderstood: LargePositiveInteger>>pixelValueForDepth: Receiver's instance variables: outerContext: BlockClosure>>ifError: startpc: 40 numArgs: 1 [(self tempAt: 2) cull: exception] in MethodContext(ContextPart)>>handleSignal: Receiver: BlockClosure>>on:do: Arguments and temporary variables: exception: MessageNotUnderstood: LargePositiveInteger>>pixelValueForDepth: Receiver's instance variables: sender: BlockClosure>>ifError: pc: 17 stackp: 3 method: (BlockClosure>>#on:do: "a CompiledMethod(88866816)") closureOrNil: nil receiver: [aWorld displayWorld] BlockClosure>>ensure: Receiver: [(self tempAt: 2) cull: exception] Arguments and temporary variables: aBlock: [self tempAt: 3 put: true] complete: nil returnValue: nil Receiver's instance variables: outerContext: MethodContext(ContextPart)>>handleSignal: startpc: 90 numArgs: 0 MethodContext(ContextPart)>>handleSignal: Receiver: BlockClosure>>on:do: Arguments and temporary variables: exception: MessageNotUnderstood: LargePositiveInteger>>pixelValueForDepth: val: nil Receiver's instance variables: sender: BlockClosure>>ifError: pc: 17 stackp: 3 method: (BlockClosure>>#on:do: "a CompiledMethod(88866816)") closureOrNil: nil receiver: [aWorld displayWorld] MessageNotUnderstood(Exception)>>signal Receiver: MessageNotUnderstood: LargePositiveInteger>>pixelValueForDepth: Arguments and temporary variables: Receiver's instance variables: messageText: nil tag: nil signalContext: MessageNotUnderstood(Exception)>>signal handlerContext: BlockClosure>>on:do: outerContext: nil message: pixelValueForDepth: 32 receiver: 4278190081 reachedDefaultHandler: false LargePositiveInteger(Object)>>doesNotUnderstand: #pixelValueForDepth: Receiver: 4278190081 Arguments and temporary variables: aMessage: pixelValueForDepth: 32 exception: MessageNotUnderstood: LargePositiveInteger>>pixelValueForDepth: resumeValue: nil Receiver's instance variables: 4278190081 ColorForm>>colormapIfNeededForDepth: Receiver: ColorForm(5x9x1) Arguments and temporary variables: destDepth: 32 newMap: a Bitmap of length 2 i: 2 iLimiT: 2 Receiver's instance variables: bits: a Bitmap of length 9 width: 5 height: 9 depth: 1 offset: nil colors: {(Color transparent). 4278190081} cachedDepth: nil cachedColormap: nil ColorForm>>colormapIfNeededFor: Receiver: ColorForm(5x9x1) Arguments and temporary variables: destForm: DisplayScreen(1672x982x32) newMap: nil color: nil pv: nil i: nil iLimiT: nil Receiver's instance variables: bits: a Bitmap of length 9 width: 5 height: 9 depth: 1 offset: nil colors: {(Color transparent). 4278190081} cachedDepth: nil cachedColormap: nil FormCanvas>>image:at:sourceRect:rule: Receiver: a FormCanvas on: DisplayScreen(1672x982x32) Arguments and temporary variables: aForm: ColorForm(5x9x1) aPoint: 689@404 sourceRect: 0@0 corner: 5@9 rule: 24 Receiver's instance variables: target: nil filterSelector: nil origin: 0@0 clipRect: 544@234 corner: 699@501 form: DisplayScreen(1672x982x32) port: a GrafPort shadowColor: nil FormCanvas(Canvas)>>translucentImage:at:sourceRect: Receiver: a FormCanvas on: DisplayScreen(1672x982x32) Arguments and temporary variables: aForm: ColorForm(5x9x1) aPoint: 689@404 sourceRect: 0@0 corner: 5@9 Receiver's instance variables: target: nil filterSelector: nil origin: 0@0 clipRect: 544@234 corner: 699@501 form: DisplayScreen(1672x982x32) port: a GrafPort shadowColor: nil FormCanvas(Canvas)>>translucentImage:at: Receiver: a FormCanvas on: DisplayScreen(1672x982x32) Arguments and temporary variables: aForm: ColorForm(5x9x1) aPoint: 689@404 Receiver's instance variables: target: nil filterSelector: nil origin: 0@0 clipRect: 544@234 corner: 699@501 form: DisplayScreen(1672x982x32) port: a GrafPort shadowColor: nil ToggleMenuItemMorph>>drawIcon:on:in: Receiver: a ToggleMenuItemMorph(17825792)'Help' Arguments and temporary variables: aForm: ColorForm(5x9x1) aCanvas: a FormCanvas on: DisplayScreen(1672x982x32) aRectangle: 689@404 corner: 694@413 iconForm: ColorForm(5x9x1) Receiver's instance variables: bounds: 549@399 corner: 694@417 owner: a MenuMorph(415236096) submorphs: #() fullBounds: 549@399 corner: 694@417 color: Color black extension: a MorphExtension (20447232) [other: (errorOnDraw -> true)] font: a StrikeFont(Bitmap DejaVu Sans 9 14) emphasis: 0 contents: 'Help' hasFocus: false isEnabled: true subMenu: a MenuMorph(37486592) isSelected: false target: nil selector: nil arguments: nil icon: Form(16x16x32) getStateSelector: nil enablementSelector: nil keyText: nil ToggleMenuItemMorph>>drawSubMenuMarker:on:in: Receiver: a ToggleMenuItemMorph(17825792)'Help' Arguments and temporary variables: aForm: ColorForm(5x9x1) aCanvas: a FormCanvas on: DisplayScreen(1672x982x32) aRectangle: 567@401 corner: 694@417 markerRect: 689@404 corner: 694@413 Receiver's instance variables: bounds: 549@399 corner: 694@417 owner: a MenuMorph(415236096) submorphs: #() fullBounds: 549@399 corner: 694@417 color: Color black extension: a MorphExtension (20447232) [other: (errorOnDraw -> true)] font: a StrikeFont(Bitmap DejaVu Sans 9 14) emphasis: 0 contents: 'Help' hasFocus: false isEnabled: true subMenu: a MenuMorph(37486592) isSelected: false target: nil selector: nil arguments: nil icon: Form(16x16x32) getStateSelector: nil enablementSelector: nil keyText: nil

1 5

Re: [Pharo-project] [Pharo-users] Riak Interface for Pharo Smalltalk
by Mariano Martinez Peck March 19, 2011

March 19, 2011

You should update http://book.pharo-project.org/book/PharoTools/ for both, zinc and riak binding otherwise, people forget or never read this email On Tue, Mar 15, 2011 at 10:48 AM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > > On 14 Mar 2011, at 22:59, Runar Jordahl wrote: > > > I have published the first beta version of a Pharo Smalltalk interface > > to Bashoâs key-value database âRiakâ: > > http://blog.epigent.com/2011/03/riak-interface-for-pharo-smalltalk.html > > > > Regards > > Runar Jordahl > > http://blog.epigent.com/ > > Pretty cool! > > Do you have anything to tell about performance ? > Are you satisfied ? > > Sven > > PS: It is also good to see that you are using Zinc HTTP Components ;-) > > > >

2 2

Re: [Pharo-project] need your attention: Package
by Marcus Denker March 19, 2011

March 19, 2011

On Mar 18, 2011, at 9:56 PM, StÃ©phane Ducasse wrote: > > - marcus was suggesting me to create a package with the same contents as the one of loaded by MC. > and to have tags to only represent categories. > > Now my time is short so I will > - probably not implement tags Even then, I would vote for mapping one PackageInfo --> one Rpackage. Categories are not packages, if we make every category a package we will end up in a big mess (as groups of these would have lots and lots of dependencies). Already the PackageInfo Packages for Network and Collection (the split into just the class categories - as- packages) was a mistake, purely driven by speed of MC. > - check again the implementation of RPackage and in particular the necessary compatibility layer, because I saw some strange > code. > - check the MC dependency on method category conventions, because some logic is not defined in the right place > like overrides in the MC tools and not in the PackageInfo > - check how a package gets created when loaded: the key question is that there is a problem to rely on categories to > associate classes to packages because we can end up with overlapping (normally the IDE captures the category renames > and change the packages accordingly). > - we should not rely on most-specific-category kind of pattern matching. > > So if you have suggestion please talk now. > > > Stef -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

3 4

[Pharo-project] Source in a file format ...
by James Ladd March 19, 2011

March 19, 2011

The Pharo File out format is currently supported by Redline Smalltalk. However, editing a class in a file in "chunk" format is not that pleasant. What would you suggest as a format for source code that is in a file? Avi Bryant of DabbleDB/Twitter fame suggested having a + (class) or - (instance) before a method pattern and just ending the method with a period. What do you think ? for example: - yourself ^ self. Rgs, James.

2 1