- Pharo-dev - lists.pharo.org

[Pharo-project] Linux Pharo VM on Pharo website
by laurent laffont April 7, 2010

April 7, 2010

Hi, I've prepared the following archive. It may replace the "Unix (3.11-3)" download link. http://lolgzs.free.fr/pharo/squeak-vm/squeak-3.11.3.2151-pharo-src.tar.gz In this archive: - patched squeak-vm rev. 2151. (The 2 patches are for FT2Plugin build and multiple options in CFLAGS to work. Patchs in archive). - awk gnuification - README with instructions to build and regenerate this source from VMMaker - All Pharo-1.0 tests green (on my machine ...) - it has been built/tested by several people in order to send me tinyBenchmark results :) The tinyBenchmarks are not as good as Exupery one, but this vary a lot depending on the CPU. Cheers, Laurent Laffont

4 7

[Pharo-project] who is maintaining shout?
by StÃ©phane Ducasse April 7, 2010

April 7, 2010

Because I would like to change the default color of comments. Green is really ugly for the release. Stef defaultStyleTable "color can be a valid argument to Color class>>colorFrom: , or nil to use the editor text color. Multiple emphases can be specified using an array e.g. #(bold italic). If emphasis is not specified, #normal will be used. if pixel height is not specified , then the editor font size will be used. " ^#( "(symbol color [emphasisSymbolOrArray [textStyleName [pixelHeight]]])" (default black ) (invalid red ) (excessCode red ) (comment (gray muchDarker) italic) (unfinishedComment (red muchDarker) italic) (#'$' (red muchDarker) ) (character (red muchDarker) ) (integer (red muchDarker) ) (number (red muchDarker) ) (#- (red muchDarker) ) (symbol (blue muchDarker) bold) (stringSymbol (blue muchDarker) bold) (literalArray (blue muchDarker) bold) (string (magenta muchDarker) normal) (unfinishedString red normal ) (assignment nil bold ) (ansiAssignment nil bold) (literal nil italic) (keyword (blue muchDarker) ) (binary (blue muchDarker) ) (unary (blue muchDarker) ) (incompleteKeyword (gray muchDarker) underlined) (incompleteBinary (gray muchDarker) underlined) (incompleteUnary (gray muchDarker) underlined) (undefinedKeyword red ) (undefinedBinary red ) (undefinedUnary red ) (patternKeyword nil bold) (patternBinary nil bold) (patternUnary nil bold) (#self (red muchDarker) bold) (#super (red muchDarker) bold) (#true (red muchDarker) bold) (#false (red muchDarker) bold) (#nil (red muchDarker) bold) (#thisContext (red muchDarker) bold) (#return (red muchDarker) bold) (patternArg (blue muchDarker) italic) (methodArg (blue muchDarker) italic) (blockPatternArg (blue muchDarker) italic) (blockArg (blue muchDarker) italic) (argument (blue muchDarker) italic) (blockArgColon black ) (leftParenthesis black ) (rightParenthesis black ) (leftParenthesis1 (green muchDarker) ) (rightParenthesis1 (green muchDarker) ) (leftParenthesis2 (magenta muchDarker) ) (rightParenthesis2 (magenta muchDarker) ) (leftParenthesis3 (red muchDarker) ) (rightParenthesis3 (red muchDarker) ) (leftParenthesis4 (green darker) ) (rightParenthesis4 (green darker) ) (leftParenthesis5 (orange darker) ) (rightParenthesis5 (orange darker) ) (leftParenthesis6 (magenta darker) ) (rightParenthesis6 (magenta darker) ) (leftParenthesis7 blue ) (rightParenthesis7 blue ) (blockStart black ) (blockEnd black ) (blockStart1 (green muchDarker) ) (blockEnd1 (green muchDarker) ) (blockStart2 (magenta muchDarker) ) (blockEnd2 (magenta muchDarker) ) (blockStart3 (red muchDarker) ) (blockEnd3 (red muchDarker) ) (blockStart4 (green darker) ) (blockEnd4 (green darker) ) (blockStart5 (orange darker) ) (blockEnd5 (orange darker) ) (blockStart6 (magenta darker) ) (blockEnd6 (magenta darker) ) (blockStart7 blue ) (blockEnd7 blue ) (arrayStart black ) (arrayEnd black ) (arrayStart1 black ) (arrayEnd1 black ) (leftBrace black ) (rightBrace black ) (cascadeSeparator black ) (statementSeparator black ) (externalCallType black ) (externalCallTypePointerIndicator black ) (primitiveOrExternalCallStart black bold ) (primitiveOrExternalCallEnd black bold ) (methodTempBar gray ) (blockTempBar gray ) (blockArgsBar gray ) (primitive (green muchDarker) bold) (pragmaKeyword (green muchDarker) bold) (pragmaUnary (green muchDarker) bold) (pragmaBinary (green muchDarker) bold) (externalFunctionCallingConvention (green muchDarker) bold) (module (green muchDarker) bold) (blockTempVar gray italic) (blockPatternTempVar gray italic) (instVar black bold) (workspaceVar black bold) (undefinedIdentifier red bold) (incompleteIdentifier (gray darker) (italic underlined)) (tempVar (gray darker) italic) (patternTempVar (gray darker) italic) (poolConstant (gray darker) italic) (classVar (gray darker) bold) (globalVar black bold) )

2 1

[Pharo-project] todo after 1.0 is released
by StÃ©phane Ducasse April 7, 2010

April 7, 2010

Hi Adrian Once 1.0 is released we should check that all the fixes that went in 1.0 after the fork to 1.1 are integrated in 1.1. Would be nice also to remove the testsexpected to break so that we give them a chance to be fixed in 1.1. Stef

3 3

[Pharo-project] [For Testing] RC3 One-Click
by Torsten Bergmann April 7, 2010

April 7, 2010

>- splash.bmp says release candidate 2. It should be release stable 1.0 or RC3. Use the attached one. >This comes from the vm package. I personally honestly don't understand >spash-screens. Is windows so slow in loading an image file? There is no reason to have one to fill load time since this is fast as on any other platform. It is more or less a short intro screen to display version info and show the logo. It is very common to provide one and often you can already guess the version from the style of the splash without reading the provided version info. As a developer you would ask "why" - wearing a marketing hat you should say "absolutely necessary". Smalltalk should not only evolve in programming features but also learn some marketing/branding so people will remember it. Read the german entry on Wikipedia for more infos: [1] http://de.wikipedia.org/wiki/Splash_Screen Another bonus is that if one takes the one-click to develop a commercial application he just has to replace the splash with a custom one. If you dislike it, then just delete/rename the splash.bmp after unzipping the one click and you are done. Bye T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

3 2

[Pharo-project] Splash for 1.0...Torsten ? Re: [For Testing] RC3 One-Click
by Mariano Martinez Peck April 7, 2010

April 7, 2010

On Wed, Apr 7, 2010 at 3:04 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Apr 3, 2010, at 1:10 PM, Mariano Martinez Peck wrote: > > > Hi Marcus. I have been testing a little the one click image and I found > the following things: > > > > - splash.bmp says release candidate 2. It should be release stable 1.0 > or RC3. > > This comes from the vm package. I personally honestly don't understand > spash-screens. Is windows so > slow in loading an image file? > > Torsten, I don't have the background image neither the tools handly...can you make a new .bmp that says only Pharo 1.0 instead of "Pharo 1.0 Rlease candidate 2" Thanks! mariano

1 0

[Pharo-project] [For Testing] RC3 One-Click
by Marcus Denker April 7, 2010

April 7, 2010

Here is a one-click image (for easy starting for newbies). I only tested this under macos, so it needs a testrun on Linux and Windows https://gforge.inria.fr/frs/download.php/26774/Pharo-1.0-10515-rc3dev.zip -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

6 9

[Pharo-project] Fwd: [squeak-dev] OB performance (Re: Slime)
by Mariano Martinez Peck April 7, 2010

April 7, 2010

Thanks Andreas :) Lukas, do you think this is worth? ---------- Forwarded message ---------- From: Andreas Raab <andreas.raab(a)gmx.de> Date: Wed, Apr 7, 2010 at 5:25 AM Subject: [squeak-dev] OB performance (Re: Slime) To: The general-purpose Squeak developers list < squeak-dev(a)lists.squeakfoundation.org> On 4/3/2010 2:22 PM, Colin Putney wrote: > > On 2010-04-03, at 11:50 AM, Andreas Raab wrote: > > On 4/3/2010 11:27 AM, Levente Uzonyi wrote: >> >>> On Sat, 3 Apr 2010, Andreas Raab wrote: >>> >>>> Interesting. My encounters with OB mostly originate from Pharo where >>>> it's always been dog-slow so I was never interested in looked deeper. >>>> Any ideas how to install OB without that stuff? >>>> >>> >>> Try this: >>> >> >> Thanks. It's definitely better than I remembered. I'm still noticing a >> real delay in some areas though, for example when I click on a system >> category. One thing you can try to test this is to open a regular browser >> and OB and then just keep scrolling through the system categories with >> cursor up or cursor down. In the regular browser this entirely smooth; in OB >> it's "stuttering" and at least I notice the same delay when clicking on the >> list. >> > > Yeah, this one area where OB is certainly not as fast. That's because OB > sorts classes according to inheritance, rather than name. It's just more > work. I find the tradeoff worthwhile - it's not that slow, and the extra > information imparted by the sort order is useful - but reasonable people may > disagree. It wouldn't be hard to make this a preference. > Nope it's not that. A bit of profiling shows the particular problem is caused by some gross inefficiencies when updating. If you file in the attached tweaks, OB scrolls just as smoothly as the standard browser. I'm not sure if the tweaks have side effects though; you might want to verify that (in particular because of the comment in OBColumn>>switchFilter: which indicates some interference although I can't see how that could make a difference if the filter is identical). Cheers, - Andreas

2 1

Re: [Pharo-project] Redline Smalltalk
by Mariano Martinez Peck April 7, 2010

April 7, 2010

> > Are you aware of the work I did that enables class fault detection in > Squeak? > > If a class has a nil methodDictionary, it causes a fault (ie it sends > recoverFromMDFault to the class). That code then restores the MD in > addition to any anyalysis you want. I never cleaned it up for posterity, but > it enabled lots of interesting work... > > By nilling all but a few MDs, and then running some application, you > could > tell exactly what classes were needed and which were not. > See the method discoverActiveClasses. > A special feature even recorded the call stack that caused each > class to be > touched. > What I was doing was restructuring the entire system as a bunch of > image segments that could be swapped out and brought in > on demand -- a sort of user-programmable swapping memory. > This all worked at one point. Swapping of projects was a bit > flakier > because of our weak discipline on pointer scope, but it > even worked in many cases. > > Where I was going with the whole "reorganizeEverything" project was that > the SystemDictionary would be partitioned into many separate dictionaries in > each project, and that namespaces would be the same as the project swapping > unit, and the whole thing would be simple and fast. It actually worked once > (;-) also. > > Loom was cool, but it could never come close to the speed of imageSegments. > I played around with swapping out the entire VM Support category with all > classes and methods, and it would swap in the entirety in less than 200 > milliseconds, and this was a decade ago. > > Sorry for the long digression, but maybe some of this thinking or even the > actual mechanism can be of use to your experiments. > > Hi Dan. First let me say that it is really cool to have you in the list :) Yes, I know about that MD faults and I did some experiments with it. As part of my work, I remove that from core and I put it in a separate package. I also rewrite some things a little. I invite you, if you want/have time to look at it. It is in http://www.squeaksource.com/ClaseUseDiscovery You can see the class comments of CUDClassesUseDiscoverer and also the CUDClassesUseDiscovererTest This tool is working perfect. I sent an email some weeks ago: http://n4.nabble.com/ANN-ClaseUseDiscovery-tool-td1296859.html#a1296861 Now, my conclusions were that it is a great tool but it has the problem that when ever you do a Smalltalk allClassesDo or similar, it brings all the classes back. I saw there was the *gentlly* so that you could do allClassesDoGently etc and the gently checks for isInMemory, where in ImageSegmentRootStub answers false. The problem is that you have to put those gently everywhere and once you forget about that....you are dead. The other problem is the gradunalirity. I mean, even when sending a simple message to a single object of a class, the whole class is loaded. Even with all that, it was great to see and have in mind a percentage of the used classes against different scenarios. Cheers Mariano > - Dan > > > > >> James Ladd <james_ladd(a)hotmail.com> wrote... > >>>> Hi Pharo-ites, > >>>> > >>>> I'm working on a port of Pharo to the Java Virtual Machine called > Redline Smalltalk. > >>>> (read more here: http://jamesladdcode.com/?p=323) > >>>> > >>>> I'm wanting to port every single class over time, but initially enough > to get the > >>>> compiler working and have a minimum runtime. > >>>> > >>>> Of the 1600+/- classes which are those necessary to make a small > workable compiler > >>>> and runtime environment? > >> > >> Hi, James - > >> > >> Bert Freudenberg forwarded this along to me, as I'm not on a Pharo > mailing list. > >> > >> I think you know of my JSqueak project (a.k.a. Potato) -- a Squeak VM > written in Java. The image that I used with it, is the same that I always > use for this kind of experiment -- mini.image built in Squeak 2.2. > >> > >> The reason it is so cool is that it includes browser, editor, compiler, > inspector debugger, and files -- everything you need for self-support. Plus > it has the decompiler, and special temp-name hack, so you can actually > browse sources with temp names before any file system works. My favorite > thing about this image is that although it is only 600k, if you decompile > all its sources, it comprises over 850k of Smalltalk, so it's like a > compressed version of the sources with a full-function IDE thrown in for > free ;-). > >> > >> As I said, the image is about 600k, of which 240k is code -- 202 classes > (x2 if you count the metas) with 4590 methods. This should be a good guide > for you in choosing classes to start with. > >> > >> You can actually run this image live in JSqueak on the web if you have > Java installed and the planets are aligned correctly... > >> http://Weather-dimensions.com/Dan/JSqueak.jnlp > >> Another interesting statistic is that the Java .jar file is only 433k, > including not only the VM, but also the entire image! This is possible > because the image is so small that the pointers in it are mostly zeroes, so > it compresses nicely. I just checked that this runs, and was happy to see > that it putts along at 21 million bytecodes/sec on my laptop. > > > > >> I haven't looked recently, but I think you'll find Mini2.2.image or > something like it in the same place where all the historical releases of > Squeak are kept. Let me know if you can't find it. > >> > >> Have fun with your project! I hope this helps > >> > >> - Dan > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > >_______________________________________________ > >Pharo-project mailing list > >Pharo-project(a)lists.gforge.inria.fr > >http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

1 0

[Pharo-project] FFI+Linux+double return value
by Schwab,Wilhelm K April 7, 2010

April 7, 2010

Hello all, I had some strange results with double return values and boiled it down to a C function Double AnyDouble() { return 1.0; } called via anyDouble < cdecl: double 'AnyDouble' () > and driven by | out | out := Array writeStream. 100 timesRepeat:[ out nextPut:Library default anyDouble ]. out contents. The results are not good. It works for the first three elements, after which it produces NaN. The real problem appears to be comparison of floats being broken after that point, as evidenced by a walkback that arises when trying to inspect the resulting collection - exploring it works. I need to try this on the latest image/vm, but wanted to start gathering opinions. Any ideas? Bill

3 8

[Pharo-project] Mac carbon VM goes to 4.2.4beta1U
by John M McIntosh April 7, 2010

April 7, 2010

In order to wrap up some VM fixes that should be pushed into the Squeak 4.x offering I've compiled up a 4.2.4beta1U VM This will be the last 4.x series of macintosh VMs as the 5.x series gains support. Someone should run the Sunit and smoke test to ensure the VM is sane. Follow the macintosh link from http://www.squeakvm.org/index.html 4.2.4b1 We update to VMMaker 168 Change #versionString from 3.x.x to 4.0.2. Fix loading of image segments that are from older, but compatible image versions. fix bounds bug in primitiveSoundRecordSamples. Add primitiveUtcWithOffset. Provide an explicit imageFormatBackwardCompatibilityVersion Merge some/*lots* of 64bit fixes -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

2 1