- Pharo-dev - lists.pharo.org

[Pharo-project] [update 2.0] #20577
by Marcus Denker March 1, 2013

March 1, 2013

20577 ----- Issue 7624: #condenseSources should not do a CompiledMethod cleanUp http://code.google.com/p/pharo/issues/detail?id=7624 Diff information: http://ss3.gemstone.com/ss/Pharo20/System-Support-MarcusDenker.796.diff

1 0

[Pharo-project] String asPacked/fromPacked:
by Martin Dias March 1, 2013

March 1, 2013

Hi I discovered this protocol in String hierarchy. Are you familiar with it? The method comment of #fromPacked: is: "Convert from a longinteger to a String of length 4." The only sender in Pharo 2.0 is MethodFinder. For WideString, it does not work. In examples: ByteString fromPacked: 'text' asPacked. ---> 'text' ByteString fromPacked: 'martin' asPacked. ---> 'rtin' WideString fromPacked: ('text' asWideString asPacked). ---> error WideString>>asPacked can be easily fixed adding an explicit return to the calculation (it's now implicitly returning self). But... it only encodes one letter: WideString fromPacked: 'martin' asWideString asPacked ---> 'n' I checked that in Squeak 4.3 there are not senders too. So... Should we fix the WideString implementation, or directly remove this protocol? Martin

7 14

[Pharo-project] [update 2.0] #20576
by Marcus Denker March 1, 2013

March 1, 2013

20576 ----- Issue 7589: ScriptLoader is too large to ship http://code.google.com/p/pharo/issues/detail?id=7589

1 0

[Pharo-project] One-Click now uses latest build VMS
by Marcus Denker March 1, 2013

March 1, 2013

The one click at: https://ci.inria.fr/pharo/job/Pharo-2.0/lastSuccessfulBuild/artifact/Pharo2… now uses the -latest zips from http://pharo.gforge.inria.fr/ci/vm/pharo/ Marcus

1 1

[Pharo-project] [update 2.0] #20575
by Esteban Lorenzano Feb. 28, 2013

Feb. 28, 2013

20575 ----- Issue 7621: Protocols are sometimes messed up https://code.google.com/p/pharo/issues/detail?id=7621 Issue 7620: remove IslandVMTweaksTestCase https://code.google.com/p/pharo/issues/detail?id=7620 Issue 7615: unload NativeBoost tests for now... https://code.google.com/p/pharo/issues/detail?id=7615 Issue 7609: [Horrible Error]: Class creation not logged in changes https://code.google.com/p/pharo/issues/detail?id=7609 Diff information: http://ss3.gemstone.com/ss/Pharo20/Tests-EstebanLorenzano.517.diff http://ss3.gemstone.com/ss/Pharo20/System-Support-EstebanLorenzano.794.diff http://ss3.gemstone.com/ss/Pharo20/System-Changes-EstebanLorenzano.198.diff http://ss3.gemstone.com/ss/Pharo20/KernelTests-EstebanLorenzano.472.diff http://ss3.gemstone.com/ss/Pharo20/Kernel-EstebanLorenzano.1322.diff

2 1

[Pharo-project] Kind of Stuff I would like to change in 3.0
by Noury Bouraqadi Feb. 28, 2013

Feb. 28, 2013

TestCase>>cleanUpInstanceVariables self class allInstVarNames do: [ :name | name = 'testSelector' ifFalse: [ self instVarNamed: name put: nil ] ] Jannik & Noury -- http://twitter.com/#!/NouryBouraqadi http://car.mines-douai.fr/noury Afin de contribuer au respect de l'environnement, merci de n'imprimer ce courriel qu'en cas de necessite Please consider the environment before you print

2 3

Re: [Pharo-project] IslandVMTweaksTestCase and Memory corruption
by Fernando Olivero Feb. 28, 2013

Feb. 28, 2013

Island are part of the TeaTime implementation in Croquet. If the tests are referring to that "Island" then why should Pharo include such tests? Fernando On Thu, Feb 28, 2013 at 4:23 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Feb 28, 2013, at 4:15 PM, Ciprian Teodorov <ciprian.teodorov(a)gmail.com<mailto:ciprian.teodorov@gmail.com>> wrote: > > > No, I think that those tests should be shipped... And fix the VM to not corrupt the memory. That's only in the case these test are wrote in pure smalltalk. If they use ffi then yeah they should be removed > > They have primitives in methods for which the primitive was not written. > > On Feb 28, 2013 3:11 PM, "Marcus Denker" <marcus.denker(a)inria.fr<mailto:marcus.denker@inria.fr>> wrote: > > On Feb 28, 2013, at 3:09 PM, ClÃ©ment Bera <bera.clement(a)gmail.com<mailto:bera.clement@gmail.com>> wrote: > > Hello, > > I was looking for VM tests in the Pharo image and I found the class IslandVMTweaksTestCase. The strange thing is its comments : > "Test case for some tweaks to the VM that Islands requires. These tests are largely for documentation; with an un-tweaked VM, the tests mostly still succeed, albeit with possible memory corruption." > > Does that really mean if I run those tests it might result into memory corruption ? > > I don't think it is a good idea to ship Pharo with this memory corruption tests in IslandVMTweaksTestCase. I suggest that if the tests may really corrupt memory we remove them from Pharo, or if they cannot corrupt memory then we fix the memory corruption comment. > > Yes, we should not ship code like that. > > Marcus > >

1 0

Feb. 28, 2013

Hello, I was looking for VM tests in the Pharo image and I found the class IslandVMTweaksTestCase. The strange thing is its comments : "Test case for some tweaks to the VM that Islands requires. These tests are largely for documentation; with an un-tweaked VM, the tests mostly still succeed, albeit *with possible memory corruption*." Does that really mean if I run those tests it might result into memory corruption ? I don't think it is a good idea to ship Pharo with this memory corruption tests in IslandVMTweaksTestCase. I suggest that if the tests may really corrupt memory we remove them from Pharo, or if they cannot corrupt memory then we fix the memory corruption comment. Regards,

3 3

[Pharo-project] fast #becomeForward: crashes without PharoV10.sources
by Camillo Bruni Feb. 28, 2013

Feb. 28, 2013

While setting up the new multi platform VM tests I saw that the tests fail extremely quickly when there are not PharoV10.sources available. It is still our know #becomeForward: but on CompiledMethods, but I just want to share that.

5 6

[Pharo-project] StackVM running on iOS 6.1.2 and Xcode 4.6 and cmake 2.8.10 on OSX Lion 10.7.5
by phil＠highoctane.be Feb. 28, 2013

Feb. 28, 2013

Hello, After much fiddling, I got the StackVM running again on my iPad.(yeah!) I used the code of Esteban from gitorious (the blessed one )and the Pharo 1.4 image from the ci server at inria. I had to change quite a bunch of stuff to get Cmake working fine as there seems to have been lots of changes related to the OSX build that had an effect on the IOS build. Some Cmake issues didn't helped. For some reason the generated sources of the interpreter contained twice isFree around lines 17564 and 17574. Looks like there is something weird going on there. I commented out one of them. Same for the ioHighResClock which doesn't contain #ifnded TARGET_IS_IPHONE when generating the StackVM for iPhone. I did before, so I wonder why it is so now. It looks like the VM should be able to have a SocketPlugin but there is no tcp.h in the SDK of 6.1 or I am looking at the wrong place. Help welcome to know where this lives. Also, in sqSqueakIPhoneApplication+imageReadWrite.m, I had to change the defines to iOS and PharoV10 as the system now has iOS.image and not iPhone.image anymore (and requires download). Most of my changes to the generate.image went towards getting cmake happy, helping finding the includes and frameworks properly since CMAKE_OSX_DEPLOYMENT_TARGET has to be set to nothing to get things to work (Cmake known bug). Also had to remove the FT2Plugin which was enabled for iOS, which I think is wrong. I had to use cmake -G Xcode . to get the thing running on the iPad as the cmake . generate unix makefiles that mess up things with OpenGL for some reason. I'll wrap all the stuff in an archive if anyone wants that. Esteban, maybe could we do an online meeting when you have time so that I can walk you through what I did (as I kept a bunch of notes). Now, I'll try to patch the handling of the bluetooth keyboard events to be able to use an external keyboard instead of that damn on-screen thing. That way, I'll be able to use proper Cmd- shortcuts and enable to code something on the device itself. I've got the keyboard thing figured out but in the codebase using iOS5.1 (which didn't wanted to work in Xcode anymore in the first place). It uses the GSEvent structure which is a non public API but there is no other way. I also parted ways with the UIKeyInput protocol which is way too primitive to do anything useful with modifiers etc. Screenshot in attach. Stay tuned. Phil

1 0