May 2009 - Pharo-dev - lists.pharo.org

[Pharo-project] How to log in console in Windows

by Torsten Bergmann

You will find the file below. It just wraps the "OutputDebugStringA" Win32 API in a subclass of ExternalStructure. Note that "OutputDebugStringA" is the ANSI version, there is also "OutputDebugStringW" for wide strings. Have fun Torsten -------------------------------------------------------------------------- 'From Pharo0.1 of 16 May 2008 [Latest update: #10303] on 17 May 2009 at 8:20:45 pm'! ExternalStructure subclass: #Win32DebugConsole instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'FFI-Examples-Win32'! !Win32DebugConsole methodsFor: 'api calls' stamp: 'tbn 5/17/2009 20:20'! outputDebugString: aString <apicall: void 'OutputDebugStringA' (char*) module:'kernel32.dll'> ^self externalCallFailed! ! Win32DebugConsole compileFields! -- Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss fÃ¼r nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a

May 18, 2009

Re: [Pharo-project] How to log in console in Windows

by Schwab,Wilhelm K

Torstem, Is the attached change set corrjupt? All I am able to get is 'From Pharo0.1 of 16 May 2008 [Latest update: #10303] on 17 May 2009 at 8:20:45 pm'! Ironic that wer're talking about windows and sometihng like that happens :) Interestingly, I am taking some first steps (nothing irrevokable) that would be consistent with moving most of my work to Linux. Even if that is a stellar success, I might still run some things on Windows to take advantage of existing tech support. Of course, Andreas' "Linus or else warning" holds true, I might reverse even that. The fact is that I have to replace a LOT of code and culture (on my my end, so there is will to do it) in order for this to work. My interest in underscores is tied to it, are are overlapped calls, etc. Wish me luck, please. I really hope this works out. For the past couple of years, I have done all of my telecommuting (not all that much of my time, but significant just the same) via Ubuntu, and have not looked back. I am now increasing my reliance on Linux, and it's going really well. Another crucial factor is that the retail market has caught up with my needs for certain types of hardware that I was unable to buy until now. Here's hoping this works! If Linux/Pharo and the new products turn ot to be robust, my quality of life will improve, after some serious porting and redesign. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Torsten Bergmann Sent: Sunday, May 17, 2009 1:27 PM To: pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] How to log in console in Windows Hi Bill, if you are on Windows anyway why not use the windows logging tools like dbmon.exe (available in the windows SDK or from [1]). I learned about it from Smalltalk MT and its a nice way to log/debug (see [2]). Download the above dbmon.exe tool and start it. Then open pharo and load FFI (by evaluating "ScriptLoader loadFFI"). Then file in the attached file and evaluate: Win32DebugConsole new outputDebugString: 'Hello' to log something to the console. It's a nice way if you run headless images. Bye Torsten [1] http://www.genify.com/techniques/dbmon.exe [2] http://www.genify.com/techniques/debugging.htm -- Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss fÃ¼r nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a

May 18, 2009

[Pharo-project] Relicensing effort

by Gabriel Cotelli

Hi, I noticed in the ResultOfRelicensing list some methods that are part of the SUnitExtensions package on Squeak Source (the ones listed as Maximiliano Taborda who mades the Squeak port). I think this code is already MIT Licensed like Aconcagua and Chalten packages. Hernan can you confirm this?. Gabriel

May 17, 2009

Re: [Pharo-project] Couldn't find an icon so...

by Mariano Martinez Peck

> > The next question is more aggressive. Having free use of underscores would > be a huge help to me. There are external libraries that are littered with > them, and relational databases for which the most natural (leaving > aesthetics out of it - this is about simplicity). I have this exact problem when trying to port Glorp to Squeak. All the glorp methods like tableForXXX_YYY_ZZZ are very common. For each table have, suppose BANK_ACCOUNT you must to a method called tableForBANK_ACCOUNT . Glorp automatically searches the method for that table. I mean, there is a code convention here. So, porting GLORP to pharo is a bit complicated because of this. I am now trying to see what to do. Cheers, mariano > Is Gwenael's work to a point that it would be reasonable to hack it into my > own image? I probably don't want to take the chance, but might consider it > depending on how close the code is to be reading. I have to at least ask > the question. > > > Thanks, > > Bill > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 17, 2009

[Pharo-project] [ANN] 10309

by StÃ©phane Ducasse

- Issue 817: Chronology contansts.... seconds... can be safely removed - Issue 718: avoid full GC at startup time Check there is a WeakArray>> initialize... changes.

May 17, 2009

Re: [Pharo-project] Closure compiler

by Mariano Martinez Peck

Thanks adrian! On Sun, May 17, 2009 at 6:11 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > ok, I created an issue: > http://code.google.com/p/pharo/issues/detail?id=819 > > Adrian > > On May 17, 2009, at 23:04 , Lukas Renggli wrote: > > > #argumentCount is important, it is part of the ANSI standard. Seaside > > uses it and we had to add our own version up to now. > > > > Lukas > > > > On Sun, May 17, 2009 at 11:00 PM, Adrian Lienhard <adi(a)netstyle.ch> > > wrote: > >> > >> > >> On May 17, 2009, at 22:56 , StÃ©phane Ducasse wrote: > >> > >>> adrian > >>> may be we should add argumentCount to BlockClosure too. > >> > >> Yes, probably. > >> Adrian > >> > >>> > >>> > >>> Stef > >>> > >>> On May 17, 2009, at 10:20 PM, Adrian Lienhard wrote: > >>> > >>>> Hi Mariano > >>>> > >>>> BlockContext implemented #argumentCount (just delegating to > >>>> #numArgs) > >>>> but BlockClosure does not. > >>>> > >>>> You can change the sender in GLORP to #numArgs or implement > >>>> BlockClosure>>#argumentCount > >>>> > >>>> Cheers, > >>>> Adrian > >>>> > >>>> On May 17, 2009, at 22:06 , Mariano Martinez Peck wrote: > >>>> > >>>>> On Wed, Apr 8, 2009 at 8:52 AM, Lukas Renggli <renggli(a)gmail.com> > >>>>> wrote: > >>>>> > >>>>>> I noticed that #argumentCount is missing in the class > >>>>>> BlockClosure. > >>>>>> #argumentCount is part of ANSI and Seaside depends on it (for now > >>>>>> it > >>>>>> is part of Seaside-Closures). > >>>>>> > >>>>> > >>>>> I am trying to make GLORP work with Pharo and I get the same > >>>>> error: > >>>>> > >>>>> BlockClosure(Object)>>doesNotUnderstand: #argumentCount > >>>>> > >>>>> Actually, this is in Dialect #argumentCountFor: aBlock > >>>>> > >>>>> Do you know how should I fix this ? > >>>>> > >>>>> Thanks! > >>>>> > >>>>> Mariano > >>>>> > >>>>> > >>>>> > >>>>>> > >>>>>> Furthermore the following messages are missing #valueWithExit, > >>>>>> #valueSuppressingAllMessages, #valueWithEnoughArguments: on > >>>>>> BlockClosure, I guess these are used at various places within > >>>>>> Pharo. > >>>>>> > >>>>>> All the mentioned methods can be copied verbatim from > >>>>>> BlockContext. > >>>>>> > >>>>>> Lukas > >>>>>> > >>>>>> On Wed, Apr 8, 2009 at 1:45 PM, Lukas Renggli <renggli(a)gmail.com> > >>>>>> wrote: > >>>>>>>> lukas do you want that we produce a backward compatibility > >>>>>>>> layer > >>>>>>>> so > >>>>>>>> that old seaside code loads in pharo? > >>>>>>> > >>>>>>> Sorry, I probably misunderstood your previous mail. > >>>>>>> > >>>>>>> After loading Seaside with the script above load: > >>>>>>> > >>>>>>> - Seaside-Closures-lr.1 from the Seaside 2.9 repository > >>>>>>> > >>>>>>> - DynamicBindings-damiencassou.9 > >>>>>>> - KomHttpServer-damiencassou.47 from the Kom repository > >>>>>>> > >>>>>>> And then you should have a Seaside with closures. > >>>>>>> > >>>>>>> Note that two tests for partial continuations fail, because they > >>>>>>> assume the old Squeak block behavior. Ignore them, these tests > >>>>>>> are > >>>>>>> wrong. > >>>>>>> > >>>>>>> Lukas > >>>>>>> > >>>>>>> -- > >>>>>>> Lukas Renggli > >>>>>>> http://www.lukas-renggli.ch > >>>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> -- > >>>>>> Lukas Renggli > >>>>>> http://www.lukas-renggli.ch > >>>>>> > >>>>>> _______________________________________________ > >>>>>> 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 > >>>> > >>> > >>> > >>> _______________________________________________ > >>> 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 > >> > > > > > > > > -- > > Lukas Renggli > > http://www.lukas-renggli.ch > > > > _______________________________________________ > > 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 >

May 17, 2009

[Pharo-project] [ANN] 10308

by Adrian Lienhard

I started to go method by method through the EToys changesets and apply what is relevant for Pharo. This brought the list of dirty methods from 243 down to 164 (I updated the working list http://code.google.com/p/pharo/wiki/ResultofRelicensing?ts=1242594801) . EToys 2181basicRemoval.st - Remove BlobMorph - Remove SystemVersion class>>#setVersion - Remove Boolean>>#==> - EventRecorderMorph>>#service and #openTapeFromFile: - Remove SubpaneDividerMorph - Remove ArchiveViewer>>#initializeToStandAlone - Deprecated MethodDictionary>>#do: - Remove SystemWindow>>#allowReframeHandles: and #allowReframeHandles - Remove SoundRecorder>>#isActive - Remove XBMReadWriter EToys 2183removeScaleMorph.st - Remove ScaleMorph From EToys 2182basicRevert1.st - Reverted to previous version HandMorph>>#cursorBounds - Reverted to previous version MIDIScore>>#durationInTicks - Reverted to previous version SerialPort>>#openPort: - Reverted to previous version WatchMorph>>#createLabels From 2186revertJDL.st - Reverted to previous version PasteUpMorph>>#selectedRect - Reverted to previous version Reverted to previous version Sonogram>>#plotColumn: - Reverted to previous version SpeakerMorph>>#appendSample: - Reverted to previous version TableLayout>>#computeCellArrangement:... and other methods - Reverted to previous version TransformationMorph>>#scaleToMatch: Rewrote following methods from previous, license clean versions: - Rewrote SelectorBrowser>>#selectorMenu: - FileDirectory>>#assureExistence - Removed Object>>#veryDeepCopy and inlined senders ___________________ http://www.adrian-lienhard.ch/

May 17, 2009

Re: [Pharo-project] Closure compiler

by Adrian Lienhard

ok, I created an issue: http://code.google.com/p/pharo/issues/detail?id=819 Adrian On May 17, 2009, at 23:04 , Lukas Renggli wrote: > #argumentCount is important, it is part of the ANSI standard. Seaside > uses it and we had to add our own version up to now. > > Lukas > > On Sun, May 17, 2009 at 11:00 PM, Adrian Lienhard <adi(a)netstyle.ch> > wrote: >> >> >> On May 17, 2009, at 22:56 , StÃ©phane Ducasse wrote: >> >>> adrian >>> may be we should add argumentCount to BlockClosure too. >> >> Yes, probably. >> Adrian >> >>> >>> >>> Stef >>> >>> On May 17, 2009, at 10:20 PM, Adrian Lienhard wrote: >>> >>>> Hi Mariano >>>> >>>> BlockContext implemented #argumentCount (just delegating to >>>> #numArgs) >>>> but BlockClosure does not. >>>> >>>> You can change the sender in GLORP to #numArgs or implement >>>> BlockClosure>>#argumentCount >>>> >>>> Cheers, >>>> Adrian >>>> >>>> On May 17, 2009, at 22:06 , Mariano Martinez Peck wrote: >>>> >>>>> On Wed, Apr 8, 2009 at 8:52 AM, Lukas Renggli <renggli(a)gmail.com> >>>>> wrote: >>>>> >>>>>> I noticed that #argumentCount is missing in the class >>>>>> BlockClosure. >>>>>> #argumentCount is part of ANSI and Seaside depends on it (for now >>>>>> it >>>>>> is part of Seaside-Closures). >>>>>> >>>>> >>>>> I am trying to make GLORP work with Pharo and I get the same >>>>> error: >>>>> >>>>> BlockClosure(Object)>>doesNotUnderstand: #argumentCount >>>>> >>>>> Actually, this is in Dialect #argumentCountFor: aBlock >>>>> >>>>> Do you know how should I fix this ? >>>>> >>>>> Thanks! >>>>> >>>>> Mariano >>>>> >>>>> >>>>> >>>>>> >>>>>> Furthermore the following messages are missing #valueWithExit, >>>>>> #valueSuppressingAllMessages, #valueWithEnoughArguments: on >>>>>> BlockClosure, I guess these are used at various places within >>>>>> Pharo. >>>>>> >>>>>> All the mentioned methods can be copied verbatim from >>>>>> BlockContext. >>>>>> >>>>>> Lukas >>>>>> >>>>>> On Wed, Apr 8, 2009 at 1:45 PM, Lukas Renggli <renggli(a)gmail.com> >>>>>> wrote: >>>>>>>> lukas do you want that we produce a backward compatibility >>>>>>>> layer >>>>>>>> so >>>>>>>> that old seaside code loads in pharo? >>>>>>> >>>>>>> Sorry, I probably misunderstood your previous mail. >>>>>>> >>>>>>> After loading Seaside with the script above load: >>>>>>> >>>>>>> - Seaside-Closures-lr.1 from the Seaside 2.9 repository >>>>>>> >>>>>>> - DynamicBindings-damiencassou.9 >>>>>>> - KomHttpServer-damiencassou.47 from the Kom repository >>>>>>> >>>>>>> And then you should have a Seaside with closures. >>>>>>> >>>>>>> Note that two tests for partial continuations fail, because they >>>>>>> assume the old Squeak block behavior. Ignore them, these tests >>>>>>> are >>>>>>> wrong. >>>>>>> >>>>>>> Lukas >>>>>>> >>>>>>> -- >>>>>>> Lukas Renggli >>>>>>> http://www.lukas-renggli.ch >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Lukas Renggli >>>>>> http://www.lukas-renggli.ch >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>> >>> >>> >>> _______________________________________________ >>> 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 >> > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 17, 2009

Re: [Pharo-project] Closure compiler

by Lukas Renggli

#argumentCount is important, it is part of the ANSI standard. Seaside uses it and we had to add our own version up to now. Lukas On Sun, May 17, 2009 at 11:00 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > > > On May 17, 2009, at 22:56 , StÃ©phane Ducasse wrote: > >> adrian >> may be we should add argumentCount to BlockClosure too. > > Yes, probably. > Adrian > >> >> >> Stef >> >> On May 17, 2009, at 10:20 PM, Adrian Lienhard wrote: >> >>> Hi Mariano >>> >>> BlockContext implemented #argumentCount (just delegating to #numArgs) >>> but BlockClosure does not. >>> >>> You can change the sender in GLORP to #numArgs or implement >>> BlockClosure>>#argumentCount >>> >>> Cheers, >>> Adrian >>> >>> On May 17, 2009, at 22:06 , Mariano Martinez Peck wrote: >>> >>>> On Wed, Apr 8, 2009 at 8:52 AM, Lukas Renggli <renggli(a)gmail.com> >>>> wrote: >>>> >>>>> I noticed that #argumentCount is missing in the class BlockClosure. >>>>> #argumentCount is part of ANSI and Seaside depends on it (for now >>>>> it >>>>> is part of Seaside-Closures). >>>>> >>>> >>>> I am trying to make GLORP work with Pharo and I get the same error: >>>> >>>> BlockClosure(Object)>>doesNotUnderstand: #argumentCount >>>> >>>> Actually, this is in Dialect #argumentCountFor: aBlock >>>> >>>> Do you know how should I fix this ? >>>> >>>> Thanks! >>>> >>>> Mariano >>>> >>>> >>>> >>>>> >>>>> Furthermore the following messages are missing #valueWithExit, >>>>> #valueSuppressingAllMessages, #valueWithEnoughArguments: on >>>>> BlockClosure, I guess these are used at various places within >>>>> Pharo. >>>>> >>>>> All the mentioned methods can be copied verbatim from BlockContext. >>>>> >>>>> Lukas >>>>> >>>>> On Wed, Apr 8, 2009 at 1:45 PM, Lukas Renggli <renggli(a)gmail.com> >>>>> wrote: >>>>>>> lukas do you want that we produce a backward compatibility layer >>>>>>> so >>>>>>> that old seaside code loads in pharo? >>>>>> >>>>>> Sorry, I probably misunderstood your previous mail. >>>>>> >>>>>> After loading Seaside with the script above load: >>>>>> >>>>>> - Seaside-Closures-lr.1 from the Seaside 2.9 repository >>>>>> >>>>>> - DynamicBindings-damiencassou.9 >>>>>> - KomHttpServer-damiencassou.47 from the Kom repository >>>>>> >>>>>> And then you should have a Seaside with closures. >>>>>> >>>>>> Note that two tests for partial continuations fail, because they >>>>>> assume the old Squeak block behavior. Ignore them, these tests are >>>>>> wrong. >>>>>> >>>>>> Lukas >>>>>> >>>>>> -- >>>>>> Lukas Renggli >>>>>> http://www.lukas-renggli.ch >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Lukas Renggli >>>>> http://www.lukas-renggli.ch >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >> >> >> _______________________________________________ >> 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 > -- Lukas Renggli http://www.lukas-renggli.ch

May 17, 2009

Re: [Pharo-project] Closure compiler

by Mariano Martinez Peck

On Sun, May 17, 2009 at 5:56 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > adrian > may be we should add argumentCount to BlockClosure too. > Yes. That was actually my question. I saw Lukas said that, but I didn't know if I should add it in my code (as an extension) or if this should be part of BlockClosure in the Pharo core. Thanks! Mariano > > Stef > > On May 17, 2009, at 10:20 PM, Adrian Lienhard wrote: > > > Hi Mariano > > > > BlockContext implemented #argumentCount (just delegating to #numArgs) > > but BlockClosure does not. > > > > You can change the sender in GLORP to #numArgs or implement > > BlockClosure>>#argumentCount > > > > Cheers, > > Adrian > > > > On May 17, 2009, at 22:06 , Mariano Martinez Peck wrote: > > > >> On Wed, Apr 8, 2009 at 8:52 AM, Lukas Renggli <renggli(a)gmail.com> > >> wrote: > >> > >>> I noticed that #argumentCount is missing in the class BlockClosure. > >>> #argumentCount is part of ANSI and Seaside depends on it (for now it > >>> is part of Seaside-Closures). > >>> > >> > >> I am trying to make GLORP work with Pharo and I get the same error: > >> > >> BlockClosure(Object)>>doesNotUnderstand: #argumentCount > >> > >> Actually, this is in Dialect #argumentCountFor: aBlock > >> > >> Do you know how should I fix this ? > >> > >> Thanks! > >> > >> Mariano > >> > >> > >> > >>> > >>> Furthermore the following messages are missing #valueWithExit, > >>> #valueSuppressingAllMessages, #valueWithEnoughArguments: on > >>> BlockClosure, I guess these are used at various places within Pharo. > >>> > >>> All the mentioned methods can be copied verbatim from BlockContext. > >>> > >>> Lukas > >>> > >>> On Wed, Apr 8, 2009 at 1:45 PM, Lukas Renggli <renggli(a)gmail.com> > >>> wrote: > >>>>> lukas do you want that we produce a backward compatibility layer > >>>>> so > >>>>> that old seaside code loads in pharo? > >>>> > >>>> Sorry, I probably misunderstood your previous mail. > >>>> > >>>> After loading Seaside with the script above load: > >>>> > >>>> - Seaside-Closures-lr.1 from the Seaside 2.9 repository > >>>> > >>>> - DynamicBindings-damiencassou.9 > >>>> - KomHttpServer-damiencassou.47 from the Kom repository > >>>> > >>>> And then you should have a Seaside with closures. > >>>> > >>>> Note that two tests for partial continuations fail, because they > >>>> assume the old Squeak block behavior. Ignore them, these tests are > >>>> wrong. > >>>> > >>>> Lukas > >>>> > >>>> -- > >>>> Lukas Renggli > >>>> http://www.lukas-renggli.ch > >>>> > >>> > >>> > >>> > >>> -- > >>> Lukas Renggli > >>> http://www.lukas-renggli.ch > >>> > >>> _______________________________________________ > >>> 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 > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 17, 2009