March 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Trying to make KomHttpServer load in 1.4

by Philippe Marschall

On 17.03.2012 18:00, StÃ©phane Ducasse wrote: > Hi guys > > I saw that TranscriptStream is deprecated in 1.3 and I was looking at the logic of the Logger. > > I do not understand the use of isTranscriptStream especially since it is defined only on Stream ^ false > and the EmergencyEvaluator which is particularly not respecting the stream protocol. > > Any suggestion? Do you really need KomHttpServer or would KomLight work as well? Cheers Philippe

March 20, 2012

Re: [Pharo-project] Compiler bug!!!

by Marcus Denker

On Mar 20, 2012, at 5:42 PM, Igor Stasenko wrote: > here the fix.. > i can't say that i like it.. but it works. > <compiler-errornode-fix.1.cs> http://code.google.com/p/pharo/issues/detail?id=5528 -- Marcus Denker -- http://marcusdenker.de

March 20, 2012

[Pharo-project] Refactor method

by Dario Trussardi

Hi, i work with Pharo 1.0. I have a DTRConfig class with class method 'pippo'. When i select on it the menu option: refactor method / pushdown option the system display the message: DTRConfig class is not one abstract class I don't understund because it. On other class the refactor method / pushdown option work fine. Thank for any considerations. Dario

March 20, 2012

Re: [Pharo-project] Compiler bug!!!

by Igor Stasenko

here the fix.. i can't say that i like it.. but it works.

March 20, 2012

Re: [Pharo-project] Compiler bug!!!

by Igor Stasenko

The problem is with #newTemp: used for binding a temporary in a block argument - [:foo <<< ] which increments the total number of temps in encoder (nTemps).. and as result, at the point where #fixTemp: is sent, the nTemps = 2, while actually should be = 1. resulting that error code temp having wrong index. and if you look later, the total number of temps in compiled method are not based on nTemps variable of encoder, but actually calculated from scratch: aCompiledMethodClass newBytes: blkSize trailerBytes: trailer nArgs: arguments size nTemps: (encoder supportsClosureOpcodes ifTrue: [| locals | locals := arguments, temporaries, (primErrNode ifNil: [#()] ifNotNil: [{primErrNode}]). encoder noteBlockExtent: block blockExtent hasLocals: locals. locals size] ifFalse: [encoder maxTemp]) here, locals size = 2, not 3 which means, that (storeIntoTemp: 2) won't work, because it lies outside of method's temps range. Here's even more crazy... if we compile code like that: badat: index <primitive: 60 error: x > [:foo | | xx y z | 5]. ^ x Bytecode: <primitive: 60 error: x> 17 <81 45> storeIntoTemp: 5 19 <8F 01 00 05> closureNumCopied: 0 numArgs: 1 bytes 23 to 27 23 <73> pushConstant: nil 24 <73> pushConstant: nil 25 <73> pushConstant: nil 26 <20> pushConstant: 5 27 <7D> blockReturn 28 <87> pop 29 <15> pushTemp: 5 30 <7C> returnTop -- Best regards, Igor Stasenko.

March 20, 2012

[Pharo-project] Pharo 1.4 Tests-Mac - Build # 284 - Still Unstable!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

March 20, 2012

[Pharo-project] Compiler bug!!!

by Igor Stasenko

Here the simple method: at: index <primitive: 60 error: x > ^ x And its bytecode: <primitive: 60 error: x> 13 <81 41> storeIntoTemp: 1 15 <11> pushTemp: 1 16 <7C> returnTop Now, if i add this: at: index <primitive: 60 error: x > [:foo | 5]. ^ x I get following bytecode: <primitive: 60 error: x> 17 <81 42> storeIntoTemp: 2 19 <8F 01 00 02> closureNumCopied: 0 numArgs: 1 bytes 23 to 24 23 <20> pushConstant: 5 24 <7D> blockReturn 25 <87> pop 26 <12> pushTemp: 2 27 <7C> returnTop so, if we ignore the block closure bytecodes, we have: <primitive: 60 error: x> 17 <81 42> storeIntoTemp: 2 26 <12> pushTemp: 2 27 <7C> returnTop The problem is that for method context there are only 2 temps (argument + error code) .. but not 3 (index is zero-based). The fix should be simple.. in code which calculates the temp index for 'error code' temp. -- Best regards, Igor Stasenko.

March 20, 2012

Re: [Pharo-project] Zodiac is cool!

by Sven Van Caekenberghe

On 20 Mar 2012, at 14:05, Camillo Bruni wrote: > We're currently setting up the build-server to include the SqueakSSL plugin. > hence Zodiac should work out of the box :) That would be really nice ! Sven

March 20, 2012

[Pharo-project] [update 1.4] #14405

by Marcus Denker

14405 ----- Issue 5523: Collection union: and intersection: should use species http://code.google.com/p/pharo/issues/detail?id=5523 Issue 5514: Enhance error Categorizer>>removeCategory: cat http://code.google.com/p/pharo/issues/detail?id=5514 -- Marcus Denker -- http://marcusdenker.de

March 20, 2012

Re: [Pharo-project] Wait or not?

by Pavel Krivanek

On Tue, Mar 20, 2012 at 11:52 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Mar 20, 2012, at 11:46 AM, Norbert Hartl wrote: > >> >> Am 20.03.2012 um 09:23 schrieb Pavel Krivanek: >> >>> Hi, >>> >>> I would like to ask you on your opinion about time scale of some big >>> repackaging steps. At start we talk about issue 5520 >>> (http://code.google.com/p/pharo/issues/detail?id=5520#makechanges) >>> that should rename Morphic package to Morphic-Base. The reason to do >>> it is to prepare Morphic and MorphicTests packages for the next >>> reorganization, namely to separate Morphic-Core package(s) with >>> content of the uMorphic image (the minimal morphic image with only the >>> most basic subset of the Morphic). >>> >>> The question is if we want to do it now or wait on the verson 1.5. At >>> start it is only the reorganization of packages that should not change >>> any behavior of the system. On the other hand, we may expect that it >>> will bring some sort-term problems. >>> >> This question is almost easy to answer. There are no things that do not produce side effects. So this is a no go in 1.4. But it can also mean that 1.4 needs to be shipped soon. Or just open 1.5 before 1.4 is shipped. But that might to be too much work for Marcus et. al. > > We did that in the past. > Now we should get all tests green for 1.4. > After only we should open 1.5 elseâ¦ the fun will take over > To say now that we only need to make to two tests green is like to say in late 19th century that we need to solve only two little problems: black body radiation and Michelson's experiment ;-) -- Pavel >> >> Norbert >> >> > >

March 20, 2012