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

[Pharo-project] Reload Job reloaded

by Pavel Krivanek

The CI job that recreates the Pharo image from Pharo Kernel is working again. It is still not very stable and it needs some actions. But please have it on mind and check if you patch doesn't break it. Cheers, -- Pavel

March 8, 2012

Re: [Pharo-project] Pharo Core 1.3 - Build # 19 - Unstable!

by Sven Van Caekenberghe

On 08 Mar 2012, at 17:20, jenkins-pharo.ci.inria.fr(a)jenkins-server.lille.inria.fr wrote: > BUILD UNSTABLE > Build URL https://ci.lille.inria.fr/pharo/job/Pharo%20Core%201.3/19/ > Project: Pharo Core 1.3 > Date of build: Thu, 08 Mar 2012 17:16:29 +0100 > Build duration: 3 mn 48 s > > CHANGES > No Changes > > BUILD ARTIFACTS > â¢ PharoCore-1.3.changes > â¢ PharoCore-1.3.image > â¢ PharoCore-1.3.zip > > JUnit Tests > Name: Announcements.Tests.Core Failed: 0 test(s), Passed: 27 test(s), Skipped: 0 test(s), Total: 27 test(s) > Name: Balloon.Collections.Tests Failed: 0 test(s), Passed: 34 test(s), Skipped: 0 test(s), Total: 34 test(s) > Name: CollectionsTests.Arrayed Failed: 0 test(s), Passed: 560 test(s), Skipped: 0 test(s), Total: 560 test(s) > Name: CollectionsTests.Atomic Failed: 0 test(s), Passed: 12 test(s), Skipped: 0 test(s), Total: 12 test(s) > Name: CollectionsTests.Sequenceable Failed: 0 test(s), Passed: 912 test(s), Skipped: 0 test(s), Total: 912 test(s) > Name: CollectionsTests.SplitJoin Failed: 0 test(s), Passed: 27 test(s), Skipped: 0 test(s), Total: 27 test(s) > Name: CollectionsTests.Stack Failed: 0 test(s), Passed: 16 test(s), Skipped: 0 test(s), Total: 16 test(s) > Name: CollectionsTests.Streams Failed: 0 test(s), Passed: 25 test(s), Skipped: 0 test(s), Total: 25 test(s) > Name: CollectionsTests.Strings Failed: 0 test(s), Passed: 590 test(s), Skipped: 0 test(s), Total: 590 test(s) > Name: CollectionsTests.Support Failed: 0 test(s), Passed: 12 test(s), Skipped: 0 test(s), Total: 12 test(s) > Name: CollectionsTests.Text Failed: 0 test(s), Passed: 40 test(s), Skipped: 0 test(s), Total: 40 test(s) > Name: CollectionsTests.Unordered Failed: 0 test(s), Passed: 1976 test(s), Skipped: 0 test(s), Total: 1976 test(s) > Name: CollectionsTests.Weak Failed: 0 test(s), Passed: 751 test(s), Skipped: 0 test(s), Total: 751 test(s) > Name: CompilerTests Failed: 0 test(s), Passed: 30 test(s), Skipped: 0 test(s), Total: 30 test(s) > Name: CompressionTests.Archive Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s) > Name: Finder.Tests Failed: 0 test(s), Passed: 9 test(s), Skipped: 0 test(s), Total: 9 test(s) > Name: FreeTypeTests.cache Failed: 0 test(s), Passed: 23 test(s), Skipped: 0 test(s), Total: 23 test(s) > Name: Gofer.Tests Failed: 0 test(s), Passed: 45 test(s), Skipped: 0 test(s), Total: 45 test(s) > Name: Graphics.Tests.Files Failed: 0 test(s), Passed: 47 test(s), Skipped: 0 test(s), Total: 47 test(s) > Name: Graphics.Tests.Primitives Failed: 0 test(s), Passed: 57 test(s), Skipped: 0 test(s), Total: 57 test(s) > Name: Graphics.Tests.Text Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s) > Name: HelpSystem.Tests.Builders Failed: 0 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 5 test(s) > Name: HelpSystem.Tests.Core.Model Failed: 0 test(s), Passed: 4 test(s), Skipped: 0 test(s), Total: 4 test(s) > Name: HelpSystem.Tests.Core.UI Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s) > Name: HelpSystem.Tests.Core.Utilities Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s) > Name: KernelTests.Chronology Failed: 0 test(s), Passed: 575 test(s), Skipped: 0 test(s), Total: 575 test(s) > Name: KernelTests.Classes Failed: 0 test(s), Passed: 60 test(s), Skipped: 0 test(s), Total: 60 test(s) > Name: KernelTests.Exception Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s) > Name: KernelTests.Methods Failed: 1 test(s), Passed: 187 test(s), Skipped: 0 test(s), Total: 188 test(s) > â¢ Failed: KernelTests.Methods.MethodContextTest.testClosureRestart > Name: KernelTests.Numbers Failed: 0 test(s), Passed: 220 test(s), Skipped: 0 test(s), Total: 220 test(s) > Name: KernelTests.Objects Failed: 0 test(s), Passed: 84 test(s), Skipped: 0 test(s), Total: 84 test(s) > Name: KernelTests.Pragmas Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s) > Name: KernelTests.Processes Failed: 0 test(s), Passed: 22 test(s), Skipped: 0 test(s), Total: 22 test(s) > Name: MorphicTests.Basic Failed: 0 test(s), Passed: 16 test(s), Skipped: 0 test(s), Total: 16 test(s) > Name: MorphicTests.Kernel Failed: 0 test(s), Passed: 8 test(s), Skipped: 0 test(s), Total: 8 test(s) > Name: MorphicTests.Text Support Failed: 0 test(s), Passed: 14 test(s), Skipped: 0 test(s), Total: 14 test(s) > Name: MorphicTests.Widgets Failed: 0 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 5 test(s) > Name: MorphicTests.WindowNotification Failed: 0 test(s), Passed: 7 test(s), Skipped: 0 test(s), Total: 7 test(s) > Name: Multilingual.Tests.TextConversion Failed: 0 test(s), Passed: 7 test(s), Skipped: 0 test(s), Total: 7 test(s) > Name: NetworkTests.Kernel Failed: 0 test(s), Passed: 31 test(s), Skipped: 0 test(s), Total: 31 test(s) > Name: NetworkTests.MailMessage Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s) > Name: NetworkTests.Protocols Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s) > Name: NetworkTests.RFC822 Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s) > Name: NetworkTests.URI Failed: 0 test(s), Passed: 105 test(s), Skipped: 0 test(s), Total: 105 test(s) > Name: NetworkTests.UUID Failed: 0 test(s), Passed: 11 test(s), Skipped: 0 test(s), Total: 11 test(s) > Name: NetworkTests.Url Failed: 0 test(s), Passed: 42 test(s), Skipped: 0 test(s), Total: 42 test(s) > Name: Regex.Tests.Core Failed: 0 test(s), Passed: 188 test(s), Skipped: 0 test(s), Total: 188 test(s) > Name: SUnit.Core.Extensions Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s) > Name: SUnit.Core.Utilities Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s) > Name: SUnit.Tests.Core Failed: 0 test(s), Passed: 77 test(s), Skipped: 0 test(s), Total: 77 test(s) > Name: StratifiedProxy.Tests Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s) > Name: Tests.Browser Failed: 0 test(s), Passed: 7 test(s), Skipped: 0 test(s), Total: 7 test(s) > Name: Tests.Bugs Failed: 0 test(s), Passed: 60 test(s), Skipped: 0 test(s), Total: 60 test(s) > Name: Tests.Compiler Failed: 0 test(s), Passed: 71 test(s), Skipped: 0 test(s), Total: 71 test(s) > Name: Tests.Compression Failed: 0 test(s), Passed: 9 test(s), Skipped: 0 test(s), Total: 9 test(s) > Name: Tests.Digital Signatures Failed: 0 test(s), Passed: 8 test(s), Skipped: 0 test(s), Total: 8 test(s) > Name: Tests.Exceptions Failed: 0 test(s), Passed: 28 test(s), Skipped: 0 test(s), Total: 28 test(s) > Name: Tests.Files Failed: 1 test(s), Passed: 54 test(s), Skipped: 0 test(s), Total: 55 test(s) > â¢ Failed: Tests.Files.FileStreamTest.testPositionPastEndIsAtEnd > Name: Tests.Finalization Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s) > Name: Tests.Localization Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s) > Name: Tests.Monticello Failed: 0 test(s), Passed: 120 test(s), Skipped: 0 test(s), Total: 120 test(s) > Name: Tests.Multilingual Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s) > Name: Tests.Object Events Failed: 0 test(s), Passed: 24 test(s), Skipped: 0 test(s), Total: 24 test(s) > Name: Tests.ObjectsAsMethods Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s) > Name: Tests.PackageInfo Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s) > Name: Tests.Polymorph.Widgets Failed: 0 test(s), Passed: 9 test(s), Skipped: 0 test(s), Total: 9 test(s) > Name: Tests.Release Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s) > Name: Tests.ScriptLoader Failed: 0 test(s), Passed: 4 test(s), Skipped: 0 test(s), Total: 4 test(s) > Name: Tests.System Failed: 0 test(s), Passed: 298 test(s), Skipped: 0 test(s), Total: 298 test(s) > Name: Tests.SystemChangeNotification Failed: 0 test(s), Passed: 37 test(s), Skipped: 0 test(s), Total: 37 test(s) > Name: Tests.SystemHistory Failed: 0 test(s), Passed: 14 test(s), Skipped: 0 test(s), Total: 14 test(s) > Name: Tests.SystemSupport Failed: 0 test(s), Passed: 9 test(s), Skipped: 0 test(s), Total: 9 test(s) > Name: Tests.TextEditors Failed: 0 test(s), Passed: 7 test(s), Skipped: 0 test(s), Total: 7 test(s) > Name: Tests.Traits Failed: 0 test(s), Passed: 60 test(s), Skipped: 0 test(s), Total: 60 test(s) > Name: Tests.Traits.MOP Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s) > Name: Tests.VM Failed: 0 test(s), Passed: 10 test(s), Skipped: 0 test(s), Total: 10 test(s) > Name: ToolsTest.Debugger Failed: 0 test(s), Passed: 10 test(s), Skipped: 0 test(s), Total: 10 test(s) > Name: ToolsTest.Inspector Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s) > Name: ToolsTest.MessageTally Failed: 0 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 5 test(s) > Name: ToolsTest.PointerFinder Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s) > Name: Zinc.Tests Failed: 18 test(s), Passed: 183 test(s), Skipped: 0 test(s), Total: 201 test(s) > â¢ Failed: Zinc.Tests.ZnClientTests.testRelativeRedirect > â¢ Failed: Zinc.Tests.ZnClientTests.testTimeout > â¢ Failed: Zinc.Tests.ZnCredentialTests.testBasicAuthorization > â¢ Failed: Zinc.Tests.ZnCredentialTests.testBasicAuthorizationFailure > â¢ Failed: Zinc.Tests.ZnCredentialTests.testDigestAuthorization > â¢ Failed: Zinc.Tests.ZnCredentialTests.testDigestAuthorizationFailure > â¢ Failed: Zinc.Tests.ZnCredentialTests.testFindHandlerFor > â¢ Failed: Zinc.Tests.ZnCredentialTests.testFindRealmFor > â¢ Failed: Zinc.Tests.ZnCredentialTests.testZnServerBasicAuthRealm > â¢ Failed: Zinc.Tests.ZnDispatcherDelegateTest.testDispatcherDelegate > â¢ Failed: Zinc.Tests.ZnEasyTests.testDelete > â¢ Failed: Zinc.Tests.ZnEasyTests.testPost > â¢ Failed: Zinc.Tests.ZnEasyTests.testPostUnicodeUtf8 > â¢ Failed: Zinc.Tests.ZnEasyTests.testPut > â¢ Failed: Zinc.Tests.ZnEasyTests.testTimeout > â¢ Failed: Zinc.Tests.ZnHttpClientTests.testBasicAuthorization > â¢ Failed: Zinc.Tests.ZnHttpClientTests.testBasicAuthorizationFailure > â¢ Failed: Zinc.Tests.ZnServerTests.testAuthorizationFailed All Zn tests pass, on my machine/VM, as they do/did at http://jenkins.lukas-renggli.ch/job/Zinc/ I think they are alll failing because a test server could not be started properly, most probably because the port is already in use. Could these tests be running more than once on the same machine ? Will this test run/build be attempted again automatically ? Sven

March 8, 2012

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

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

March 8, 2012

[Pharo-project] [update 1.4] #14384

by Marcus Denker

14385 ----- The following changes have been integrated: Issue 5442: FSFilesystem should continue to provide onDisk and inMemory http://code.google.com/p/pharo/issues/detail?id=5442

March 8, 2012

Re: [Pharo-project] GSoC: ARM jitter for Squeak VM

by Esteban Lorenzano

I would really like to co-mentor something like this... but I presume I have more things to learn than to teach :) anyway, if there is a place to help, count me in. Esteban El 08/03/2012, a las 8:07a.m., Nick Ager escribiÃ³: > Here's hoping that in a similar way to Yanni and the ePUB proposal and someone will jump in and say that they are already working on this. > > Quoting Eliot: > > It's not overambitious for someone good. And I'd love to see it happen. But finding time to be a mentor has proven difficult for me in the past. I'd happily be part-mentor, but I need someone to at least help in the GSoC process... > > > so if there is anyone out there that can help Eliot and Igor with mentoring or the GSoC process, jump in and offer support. > > The proposal: > > ----- > > Name: ARM jitter for Squeak VM > Level: Advanced > Possible mentor: Eliot Miranda > Possible second mentor: Igor Stasenko > > Description > The Squeak VM is the dynamic virtual machine used for many open-source software projects such as Scratch [1], eToys [2], Pharo [3], the Newspeak language [4], the innovative web framework Seaside [5] and many others. CogVM [6] is a development of the Squeak VM which adds a powerful Intel x86 JITer [7]. The CogVM JIT has significantly improved the performance of the open-source Smalltalk projects which have adapted to use it. > Increasingly low cost highly capable ARM hardware such as the Raspberry Pi [8] and the Beagle Board [9] have become widely available. In addition the new version of the one-laptop-per-child is based on the ARM platform [10]. The Squeak VM compiles for ARM platforms, but currently there is no JIT on ARM platforms, significantly decreasing the performance of popular software on ARM. The goal of this project is to add simple ARM JITTing capability to the CogVM. > > [1] http://scratch.mit.edu/ > [2] http://www.squeakland.org/about/intro/ > [3] http://www.pharo-project.org > [4] http://newspeaklanguage.org/ > [5] http://seaside.st/ > [6] http://gitorious.org/cogvm > [7] http://en.wikipedia.org/wiki/Just-in-time_compilation > [8] http://www.raspberrypi.org/ > [9] http://beagleboard.org/bone > [10] http://one.laptop.org/about/xo-3 > > Technical Details > The work would require a interest in virtual machine optimisation, some knowledge of Intel x86 and ARM assembler and knowledge of C and dynamic languages. > The Squeak and Cog VM are written in a simplified subset of Smalltalk known as slang [11] - which then generates C output and forms the basis of the VM. > As the Squeak VM is a Smalltalk program, it is developed in Smalltalk, and the Cog JIT is no exception. The VM, including the JIT, is written in Smalltalk and run in the context of the Smalltalk IDE, but the JIT still generates machine-code that must be evaluated within the Smalltalk environment. On x86 is done by interfacing to an x86 simulator library derived from the Bochs x86/x86-64 PC simulator, written in C++. Implementing the ARM port should be no different. The first task will be to choose and interface to a suitable ARM simualtor/emulator. Once this is working, the ARM code generator can be incrementally developed within Smalltalk. Finally once the simulator is fully functional one can get down and dirty with an actual physical ARM machine - such as the Raspberry Pi or Beagle Board. > [11] http://wiki.squeak.org/squeak/2267 > > > Benefits to the Student > The student will gain an in-depth knowledge of virtual machine optimisation, working in a productive innovative environment - it's > great fun to be able to implement a JIT in a safe high-level dynamic language, instead of the traditional route of developing in C/C++ and debugging in GDB. > The student will have the satisfaction of seeing performance gains for a range of high-profile projects which use the Squeak VM on ARM. > > Benefits to the Community > The Smalltalk community will gain an initial implementation of an ARM Jitter which can then be further developed along-side the x86 dynamic translation work. An ARM Jitter for the CogVM will improve the performance of many notable open-source projects on low-cost ARM hardware, bringing innovative software and development environments to wider community. > > ---- > > Cheers > > Nick

March 8, 2012

Re: [Pharo-project] GSoC: ARM jitter for Squeak VM

by S Krish

Let me know if I can help in any way.. on this.. On 3/8/12, Nick Ager <nick.ager(a)gmail.com> wrote: > Here's hoping that in a similar way to Yanni and the ePUB proposal and > someone will jump in and say that they are already working on this. > > Quoting Eliot: > > It's not overambitious for someone good. And I'd love to see it happen. >> But finding time to be a mentor has proven difficult for me in the past. >> I'd happily be part-mentor, but I need someone to at least help in the >> GSoC process... > > > > so if there is anyone out there that can help Eliot and Igor with mentoring > or the GSoC process, jump in and offer support. > > The proposal: > > ----- > > Name: ARM jitter for Squeak VM > Level: Advanced > Possible mentor: Eliot Miranda > Possible second mentor: Igor Stasenko > > Description > The Squeak VM is the dynamic virtual machine used for many open-source > software projects such as Scratch [1], eToys [2], Pharo [3], the Newspeak > language [4], the innovative web framework Seaside [5] and many others. > CogVM [6] is a development of the Squeak VM which adds a powerful Intel x86 > JITer [7]. The CogVM JIT has significantly improved the performance of the > open-source Smalltalk projects which have adapted to use it. > Increasingly low cost highly capable ARM hardware such as the Raspberry Pi > [8] and the Beagle Board [9] have become widely available. In addition the > new version of the one-laptop-per-child is based on the ARM platform [10]. > The Squeak VM compiles for ARM platforms, but currently there is no JIT on > ARM platforms, significantly decreasing the performance of popular software > on ARM. The goal of this project is to add simple ARM JITTing capability to > the CogVM. > > [1] http://scratch.mit.edu/ > [2] http://www.squeakland.org/about/intro/ > [3] http://www.pharo-project.org > [4] http://newspeaklanguage.org/ > [5] http://seaside.st/ > [6] http://gitorious.org/cogvm > [7] http://en.wikipedia.org/wiki/Just-in-time_compilation > [8] http://www.raspberrypi.org/ > [9] http://beagleboard.org/bone > [10] http://one.laptop.org/about/xo-3 > > Technical Details > The work would require a interest in virtual machine optimisation, some > knowledge of Intel x86 and ARM assembler and knowledge of C and dynamic > languages. > The Squeak and Cog VM are written in a simplified subset of Smalltalk known > as slang [11] - which then generates C output and forms the basis of the VM. > As the Squeak VM is a Smalltalk program, it is developed in Smalltalk, and > the Cog JIT is no exception. The VM, including the JIT, is written in > Smalltalk and run in the context of the Smalltalk IDE, but the JIT still > generates machine-code that must be evaluated within the Smalltalk > environment. On x86 is done by interfacing to an x86 simulator library > derived from the Bochs x86/x86-64 PC simulator, written in C++. > Implementing the ARM port should be no different. The first task will be > to choose and interface to a suitable ARM simualtor/emulator. Once this is > working, the ARM code generator can be incrementally developed within > Smalltalk. Finally once the simulator is fully functional one can get down > and dirty with an actual physical ARM machine - such as the Raspberry Pi or > Beagle Board. > [11] http://wiki.squeak.org/squeak/2267 > > > Benefits to the Student > The student will gain an in-depth knowledge of virtual machine > optimisation, working in a productive innovative environment - it's > great fun to be able to implement a JIT in a safe high-level dynamic > language, instead of the traditional route of developing in C/C++ and > debugging in GDB. > The student will have the satisfaction of seeing performance gains for a > range of high-profile projects which use the Squeak VM on ARM. > > Benefits to the Community > The Smalltalk community will gain an initial implementation of an ARM > Jitter which can then be further developed along-side the x86 dynamic > translation work. An ARM Jitter for the CogVM will improve the performance > of many notable open-source projects on low-cost ARM hardware, bringing > innovative software and development environments to wider community. > > ---- > > Cheers > > Nick >

March 8, 2012

Re: [Pharo-project] EPUB view for Pier Books

by Yanni Chiu

On 08/03/12 2:58 AM, Nick Ager wrote: > Have you had any luck viewing the output ePUB file with iBooks on iOS? I > tried with my iPhone but it wouldn't open. I also noticed that the > section link wasn't numbered - any thoughts? I don't have iBooks, iOS, iPhone to try, but I'll try the dev simulator on MacOSX. I'm not sure what is meant by section link number. The EPUB standard appeared to be a maze of other standards and some now deprecated specs. So rather than decipher the spec, I unzipped a few example EPUB books, and gleaned a small subset to implement. Here's my plan: 1. Add my test Pier book as a TestCase 2. Add a way to include a .css stylesheet 3. Fix bugs reported on different platforms

March 8, 2012

Re: [Pharo-project] [update 1.4] #14383

by Esteban Lorenzano

+1 El 08/03/2012, a las 11:00a.m., Tudor Girba escribiÃ³: > This sounds excellent! > > Doru > > On Thu, Mar 8, 2012 at 2:49 PM, Sven Van Caekenberghe <sven(a)beta9.be> wrote: >> >> On 08 Mar 2012, at 14:43, Benjamin wrote: >> >>> Now, to integrate a fix a generate a new Pharo version, they just have to execute on script which take the issues number as parameter :) >>> >>> And then, everything is fully automatic (even running the tests ;) ) >> >> Cool. >> >> Now even the smallest child could to do it - Duckingâ¦. ;-) >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

March 8, 2012

[Pharo-project] Pharo 1.3 - Build # 20 - Still Unstable!

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

March 8, 2012

Re: [Pharo-project] Adding a statement programmatically

by Norbert Hartl

Am 08.03.2012 um 17:08 schrieb Sean P. DeNigris: > > Marcus Denker-4 wrote >> >> -> Compile the code to an RB AST, this then has all the interfaces needed >> to replace nodes or add nodes. >> You can then pretty print it back to source. >> > > Thanks Marcus. That's what I was trying to do. I got the AST and created the > node: > body := (AbstractSound>>#initialize) parseTree body. > body addNode: (RBParser parseExpression: 'envelopes := nil'). > > But then I couldn't figure out how to get the source back... > > "These both returned the statements without the header" > body formattedCode. > body newSource. > > "This returned the full method, but without the added node" > body source > Sean, you extracted the body first and operate on it. So you only have the body. Try method := (AbstractSound>>#initialize) parseTree. method body addNode: (RBParser parseExpression: 'envelopes := nil'). method formattedCode Norbert

March 8, 2012