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

[Pharo-project] Block explained continued
by StÃ©phane Ducasse Jan. 30, 2012

Jan. 30, 2012

I did another pass on the Block chapter I'm writing and I would like to know if I'm not saying something wrong. Here is what I wrote. The following examples shows that escaping blocks jumped to their home context but do not unwind the stack after this point. \ct{valueWithExit} is defined on the class BlockClosure as follows. \begin{code}{} BlockClosure>>valueWithExit self value: [ ^nil ] \end{code} \begin{code}{} BExp>>assert: aBoolean aBoolean ifFalse: [Error signal] BExp>>testValueWithExitBreak | val | [ :break | 1 to: 10 do: [ :i | val := i. i = 4 ifTrue: [break value]. ] ] valueWithExit. self assert: val = 4. \end{code} \ct{testValueWithExitBreak} shows that the block \ct{break} is created and activated once and as effect it cancels the rest of the computation. The following method \ct{testValueWithExitContinue} shows that just the computation left from the block activation is skipped (here \ct{val := val + 1. last := i}, when i = 4) and this is why the value of \ct{val} is 9 and not 10. In this example, a new block is created \begin{code}{} BExp>>testValueWithExitContinue | val last | val := 0. 1 to: 10 do: [ :i | [ :continue | i = 4 ifTrue: [continue value]. val := val + 1. last := i ] valueWithExit. ]. self assert: val = 9. self assert: last = 10. \end{code} Pay attention here \ct{valueWithExit} is not equivalent to \ct{value: [^nil]} because it changes the home context of the block. In the first case the homeContext of the block is not the method \ct{testValueWithExitContinue} while in the second it is. Put a self halt before the assert: to convince you. In one case, you will reach the halt while in the other not.

3 5

[Pharo-project] loading Seaside 3.0.6.3 in Pharo 1.4
by Esteban Lorenzano Jan. 30, 2012

Jan. 30, 2012

Hi, I loaded last version of seaside into a pharo 1.4 image. Everything looks working fine, but there a couple of fixes: 1) KomLogger>>#attachTranscript self detachTheTranscript. ^(self streams detect: [:ea | ea isTranscriptStream] ifNone: [nil]) ifNil: [self addStream: TranscriptStream new] "TranscriptStream" is not anymore on pharo and should be replaced with ThreadSafeTranscript 2) String>>#withBlanksTrimmed is deprecated, and now it should use #trimBoth how can I proceed to apply this fixes into seaside (without breaking other platforms)? cheers, Esteban

6 11

[Pharo-project] [:x :y| x*x. â x + y]
by StÃ©phane Ducasse Jan. 30, 2012

Jan. 30, 2012

Hi guys is there a naming convention for such blocks. In the chapter I called them escaping block but I also used continuation blocks. (I do not like continuation blocks since to me it is unclear) but if this is a convention I would follow it. Stef

4 3

[Pharo-project] MCWorkingCopy>>#uniqueVersionName
by Sven Van Caekenberghe Jan. 30, 2012

Jan. 30, 2012

Today I pressed Command-. while looking at a slow Monticello save, I was wondering what the system was doing before I even had written my commit message. Apparently, MCWorkingCopy>>#uniqueVersionName checks every repository linked to the package, (6 for Zn in my case), to see if the proposed version name is unique across all these repositories, not using the cache. I understand this, but this comes down to 6 times getting the list of all package names from remote servers. One way to speed this up would be to parallelize these. But fundamentally, I thought Monticello was supposed to be a distributed version control system ? Would it not be possible to assign the version name based on local, best effort knowledge alone and deal with possible conflicts afterwards (there is the ancestory) ? Just thinking out loud. Sven

3 4

[Pharo-project] pier2 loaded successfully on Pharo 1.4
by Esteban Lorenzano Jan. 30, 2012

Jan. 30, 2012

Hi, with seaside 3.0 fixed (as I send in another mail), I can report that pier2 loads and runs out of the box on pharo 1.4 best, Esteban

3 3

Re: [Pharo-project] [Moose-dev] Re: browsers vs. guis
by Tudor Girba Jan. 30, 2012

Jan. 30, 2012

Hi, Well, you can customize the UI. There are two ways: 1. Directly embed a widget from the UI framework. For example, in Morphic, you can simply embed a morph. For example, see GLMBasicExample>>starBrowser for a demo in which we embed various system browsers in a Glamour browser. Or here: http://www.themoosebook.org/book/internals/glamour/presentations/custom However, up to now, we mostly only use this solution for situations in which the data only arrives in the custom morph. We still need to add the ability of specifying how data should go out of the morph and into the surrounding Glamour pane so that it can be completely embedded in the overall data flow. 2. Extend Presentations with your own widget. This involves, subclassing GLMPresentation, and writing the rendering code. This requires knowledge about the inner workings on Glamour. Cheers, Doru On 30 Jan 2012, at 03:59, Offray Vladimir Luna CÃ¡rdenas wrote: > Hi, > > > El sÃ¡b 28 ene 2012 17:52:38 COT, Igor Stasenko escribiÃ³: >> Nice post. >> Still, we want a data-flow browser + being able to control/customize UIs :) >> Sure, this is veeeery hard to achieve. > > As a total newbie, I believe that this Igor's idea would be what one is looking for and the question is if there is a way to do it keeping the minimal syntax of Glamour... just wondering. > > Cheers, > > Offray > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com "Obvious things are difficult to teach."

1 0

[Pharo-project] [update 1.4] #14298
by Marcus Denker Jan. 30, 2012

Jan. 30, 2012

14298 ----- Issue 5220: MenuRegistration do not allow menu with more than 2 levels of deapth http://code.google.com/p/pharo/issues/detail?id=5220 Issue 5222: mc slowdown with big package-cache http://code.google.com/p/pharo/issues/detail?id=5222 Issue 5182: Problem in PluggableListMorph http://code.google.com/p/pharo/issues/detail?id=5182 -- Marcus Denker -- http://marcusdenker.de

2 2

Re: [Pharo-project] Trying to build CogVM in MacOSX 10.7 Lion
by dimitris chloupis Jan. 29, 2012

Jan. 29, 2012

its ok , I am not in any hurry you can take all the time in the world. Thanks for helping me to go that far. You were right downloading that file did not help. But all is ok, I already have a NBCogVm app to play around , trying both CogVM and Nativeboost. I know that there are some things that one cannot Â rush, and I know Pharo Â devs are not that many to solve all the problems that may arise, immediately.Â So I will wait and I will also try to explore VMMaker abit more see what makes it tick. And if it all fails I can fall back to old FFI. The reason why I wanted to build CogVM is basically Nativeboost's new FFI. I wanted to use the newest and badest since my project is long term and it seems both CogVM and NB are the future for both Pharo and Squeak . But as I said the very fact that my project will take years to reach version 1 since its huge, has the positive side effect that I am not in any hurry to see this work very well.Â So take your time and I will try to learn and assist any way I can. I will certainly take it slowly and enjoy the whole process ;) ________________________________ From: Esteban Lorenzano <estebanlm(a)gmail.com> To: dimitris chloupis <thekilon(a)yahoo.co.uk> Sent: Sunday, 29 January 2012, 23:52 Subject: Re: [Pharo-project] Trying to build CogVM in MacOSX 10.7 Lion I have serious doubts that this will work, but ok, I'm sending compiler :) other solution (temporary solution, of course), would be download xcode 4.0, install it, then "update" to 4.2 (I'm not happy with all of this, but well... I need time to create a proper compilation with llvm or ported gcc)Â El 29/01/2012, a las 6:12p.m., dimitris chloupis escribiÃ³: tried all the steps and generated sources when i try to make it fails here is my log > > >DIMITRISs-iMac:~ kilon$ cd cogvm >DIMITRISs-iMac:cogvm kilon$ cd blessed >DIMITRISs-iMac:blessed kilon$ cd build >DIMITRISs-iMac:build kilon$ ../codegen-scripts/extract-commit-info.sh >DIMITRISs-iMac:build kilon$ cmake . >-- The C compiler identification is GNU >-- The CXX compiler identification is GNU >-- Checking whether C compiler has -isysroot >-- Checking whether C compiler has -isysroot - yes >-- Checking whether C compiler supports OSX deployment target flag >-- Checking whether C compiler supports OSX deployment target flag - yes >-- Check for working C compiler: /usr/bin/gcc >-- Check for working C compiler: /usr/bin/gcc -- works >-- Detecting C compiler ABI info >-- Detecting C compiler ABI info - done >-- Checking whether CXX compiler has -isysroot >-- Checking whether CXX compiler has -isysroot - yes >-- Checking whether CXX compiler supports OSX deployment target flag >-- Checking whether CXX compiler supports OSX deployment target flag - yes >-- Check for working CXX compiler: /usr/bin/c++ >-- Check for working CXX compiler: /usr/bin/c++ -- works >-- Detecting CXX compiler ABI info >-- Detecting CXX compiler ABI info - done > > >Adding internal plugin: ADPCMCodecPlugin >Adding internal plugin: BMPReadWriterPlugin >Adding internal plugin: B2DPlugin >Adding internal plugin: BitBltPlugin >Adding internal plugin: ClipboardExtendedPlugin >Adding internal plugin: DSAPrims >Adding internal plugin: ZipPlugin >Adding internal plugin: DropPlugin >Adding internal plugin: FFTPlugin >Adding internal plugin: FilePlugin >Adding internal plugin: FloatArrayPlugin >Adding internal plugin: GeniePlugin >Adding internal plugin: HostWindowPlugin >Adding internal plugin: JPEGReadWriter2Plugin >Adding internal plugin: JPEGReaderPlugin >Adding internal plugin: Klatt >Adding internal plugin: LargeIntegers >Adding internal plugin: Matrix2x3Plugin >Adding internal plugin: MiscPrimitivePlugin >Adding internal plugin: RePlugin >Adding internal plugin: SecurityPlugin >Adding internal plugin: SocketPlugin >Adding internal plugin: SoundCodecPrims >Adding internal plugin: SoundPlugin >Adding internal plugin: StarSqueakPlugin >Adding internal plugin: SurfacePlugin >Adding internal plugin: UnixOSProcessPlugin >Adding external plugin: SqueakFFIPrims >Adding external plugin: IA32ABI >Adding external plugin: UUIDPlugin >Adding external plugin: FloatMathPlugin >Adding external plugin: AsynchFilePlugin >Adding external plugin: SerialPlugin >Adding external plugin: Mpeg3Plugin >Adding external plugin: CroquetPlugin >Adding external plugin: JoystickTabletPlugin >Adding external plugin: MIDIPlugin >Adding external plugin: B3DAcceleratorPlugin >Adding external plugin: LocalePlugin >Adding external plugin: ObjectiveCPlugin >Adding external plugin: QuicktimePlugin >Adding external plugin: TestOSAPlugin >Adding external plugin: FT2Plugin >-- Configuring done >-- Generating done >-- Build files have been written to: /Users/kilon/cogvm/blessed/build >DIMITRISs-iMac:build kilon$ make >Scanning dependencies of target UnixOSProcessPlugin >[ Â 1%] Building C object UnixOSProcessPlugin/CMakeFiles/UnixOSProcessPlugin.dir/Users/kilon/cogvm/blessed/src/plugins/UnixOSProcessPlugin/UnixOSProcessPlugin.c.o >cc1: error: unrecognized command line option "-arch" >cc1: error: unrecognized command line option "-arch" >cc1: error: unrecognized command line option "-arch" >make[2]: *** [UnixOSProcessPlugin/CMakeFiles/UnixOSProcessPlugin.dir/Users/kilon/cogvm/blessed/src/plugins/UnixOSProcessPlugin/UnixOSProcessPlugin.c.o] Error 1 >make[1]: *** [UnixOSProcessPlugin/CMakeFiles/UnixOSProcessPlugin.dir/all] Error 2 >make: *** [all] Error 2 >DIMITRISs-iMac:build kilon$Â > > > > > >________________________________ > From: Esteban Lorenzano <estebanlm(a)gmail.com> >To: Pharo-project(a)lists.gforge.inria.fr; dimitris chloupis <thekilon(a)yahoo.co.uk> >Sent: Sunday, 29 January 2012, 22:54 >Subject: Re: [Pharo-project] Trying to build CogVM in MacOSX 10.7 Lion > >if you have this one: i686-apple-darwin11-gcc-apple-4.2.1 >that should be the right one. > >Just create a symlink 'gcc' in /usr/bin and let's see what happens. > > > >El 29/01/2012, a las 5:50p.m., dimitris chloupis escribiÃ³: > >> it appears I was correct according to this >> >> http://ask.metafilter.com/200231/How-to-install-gcc-42-on-a-macbook-with-Xc… >> >> and a gazillion other results from google . It no longer ships with Xcode-4.2. I assume you have upgraded from 4.1 that is why you have it. >> >> Ok I am ready to try macports but how ? >> >> >> I have several gccs in macports >> >> gcc-apple-4.2 >> >> and >> >> i686-apple-darwin11-gcc-apple-4.2.1 >> >> which one and how ? >> >> From: Esteban Lorenzano <estebanlm(a)gmail.com> >> To: dimitris chloupis <thekilon(a)yahoo.co.uk> >> Sent: Sunday, 29 January 2012, 22:32 >> Subject: Re: [Pharo-project] Trying to build CogVM in MacOSX 10.7 Lion >> >> I really don't know... maybe Sean (who installed xcode from scratch recently) can confirm that. >> >> so... let's try with macports... :) >> >> best, >> Esteban >> >> El 29/01/2012, a las 5:30p.m., dimitris chloupis escribiÃ³: >> >>> in usr/bin I have i686-apple-darwin11-llvm-g++-4.2 and 686-apple-darwin11-llvm-gcc-4.2. Both are symlinks that point to the usr/llmv-gcc-4.2/bin and corresponding binaries. >>> >>> Dont know why, there is also a gcc binary in my home folder. Maybe I accidentally moved it there before the install. >>> >>> The install was sucessful as far I can tell, there were no errors. >>> >>> as I said the only thing non llvm is in macports folder which of course is not related to xcode install. I feel that I can bet serious money that the new xcode comes with only llvm compilers. Maybe I am wrong.Â >>> >>> From: Esteban Lorenzano <estebanlm(a)gmail.com> >>> To: Pharo-project(a)lists.gforge.inria.fr; dimitris chloupis <thekilon(a)yahoo.co.uk> >>> Sent: Sunday, 29 January 2012, 22:09 >>> Subject: Re: [Pharo-project] Trying to build CogVM in MacOSX 10.7 Lion >>> >>> he... connection problems... yeah, I know a lot about them :) >>> >>> well... after a successful install, I *think* you should have gcc and gcc-4.2... last one is also a symlink who points to: >>> >>> /usr/bin/i686-apple-darwin11-gcc-4.2.1 >>> >>> who should be there... is that the case? >>> >>> >>> >>> El 29/01/2012, a las 4:51p.m., dimitris chloupis escribiÃ³: >>> >>>> there is no gcc in usr/bin at all. Afterall your first command removed the only one ;) >>>> >>>> I have reinstalled XcodeÂ to be sure . My Xcode About box says its XCODE 4.2 build 4D199 >>>> >>>> no idea how to update cause I downloaded it via torrent, could not download from app store cause my connection is crapish and each time I disconnected it canceled my upload (no I could not resume, tried everything). So I had to install via torrent. >>>> >>>> >>>> >>>> From: Esteban Lorenzano <estebanlm(a)gmail.com> >>>> To: Pharo-project(a)lists.gforge.inria.fr; dimitris chloupis <thekilon(a)yahoo.co.uk> >>>> Sent: Sunday, 29 January 2012, 20:49 >>>> Subject: Re: [Pharo-project] Trying to build CogVM in MacOSX 10.7 Lion >>>> >>>> There is a problem there... if you have XCode 4.2.1 (latest), you should have that one... xcode just changed the default, it did not remove the gcc, AFAIK. >>>> >>>> which versions of gcc do you have in /usr/bin? >>>> >>>> oh, btw... is ln -s, not just ln (my mistake, but both should work) >>>> >>>> (symlink macport gcc should work, but I'm fearing there is something wrong with xcode instalation, and that's probably the reason it didn't compiled the first time, so, let's be sure about that before try the port) >>>> >>>> El 29/01/2012, a las 3:40p.m., dimitris chloupis escribiÃ³: >>>> >>>>> >>>>> >> sudo rm /usr/bin/gcc >>>>> >>>>> success ! >>>>> >>>>> >> sudo ln /usr/bin/gcc-4.2 gcc >>>>> >>>>> fail ! >>>>> >>>>> no such file >>>>> >>>>> there is a gcc symlink in developer/usr/bin that point to developer/usr/llvm-gcc-4.2/llvm-gcc-4.2 >>>>> >>>>> there is no gcc-4.2 in my Xcode folder or other folders except the gcc folder that I installed via macports following the previous tutorial that I have linked. Should I symlink macports gcc-4.2 ? >>>>> >>>>> Xcode is by default isntalled in the Developer folder >>>>> >>>>> I am open to suggestions and thanks for helping me.Â >>>>> >>>>>Â >>>>> >>>> >>>> >>>> >>> >>> >>> >> >> >> > > > >

1 0

Re: [Pharo-project] [squeak-dev] Smalltalk for small projects only?
by Dale Henrichs Jan. 29, 2012

Jan. 29, 2012

Karl, For the types of project that would employ a team of 200, you need to be able to reliably reproduce the state of an image, from scratch, 5 years after development has completed ... I invite you to read Allen Wirfs-Brock's paper on "Declarative Smalltalk"[1]. Here are some excerpts: Smalltalk does not include the concept of a program as a distinct entity. In practice, a Smalltalk program is the state of a virtual image when work is declared completed. Lack of a program definition in traditional Smalltalk environments leads to an undue reliance on the virtual image. Images can become obsolete or broken. Because the program is encoded in the image, the program is in danger of becoming inaccessible if the image becomes outmoded or corrupt. The manual and unreliable nature of the initialization of Smalltalk programs leads to a number of program errors. Especially prevalent after reconstruction of a program in a new image are errors where program elements have an initial value of nil instead of some other value as originally intended by the programmer. The use of a declarative specification model has little direct impact upon Smalltalk programmers. Even though Smalltalk has traditionally been implemented using an imperative program description model, the perception of most Smalltalk programmers is of a declarative model. This is because Smalltalk programmers typically create and edit programs using a browser that presents the classes that make up the program in a declarative style. Disclaimer: I worked with Allen Wirfs-Brock in the nineties (engineer on the Team/V team) while he was developing his ideas for Declarative Smalltalk, so I am somewhat biased in my thinking:) My opinion that being able to build images from scratch (easily and reproducibly) is a "requirement" to get in the door for mainstream projects... giving mainstream developers the opportunity to work in a image-based environment will set them free:) Dale [1] http://www.smalltalksystems.com/publications/_awss97/SSDCL1.HTM ----- Original Message ----- | From: "karl ramberg" <karlramberg(a)gmail.com> | To: "The general-purpose Squeak developers list" <squeak-dev(a)lists.squeakfoundation.org> | Cc: "VWNC" <vwnc(a)cs.uiuc.edu>, Pharo-project(a)lists.gforge.inria.fr | Sent: Saturday, January 28, 2012 11:39:22 AM | Subject: Re: [squeak-dev] Smalltalk for small projects only? | | On Sat, Jan 28, 2012 at 7:07 PM, Dale Henrichs < dhenrich(a)vmware.com | > wrote: | | You are talking about dealing with source code, but what about the | live objects in the image? Is there any work done on managing live | images with several developers ? This is where Smalltalk excels and | would be very interesting instead of falling back to the rebuild | from source strategy. | | Karl

7 8

Re: [Pharo-project] FSFileSystem: modification date
by Marcus Denker Jan. 29, 2012

Jan. 29, 2012

On Jan 27, 2012, at 9:42 PM, Camillo Bruni wrote: > Hi Deby, > > Open a bug report :) I think the memory FS should handle the modification / creation dates exactly as it would on disk... > There is a bug entry here already: http://code.google.com/p/pharo/issues/detail?id=3154 -- Marcus Denker -- http://marcusdenker.de

1 0