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

Re: [Pharo-project] Closure compiler

by Adrian Lienhard

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

May 17, 2009

Re: [Pharo-project] [ANN] 10307

by Adrian Lienhard

WAIT, please, I'm working on another update right now. Adrian On May 17, 2009, at 22:55 , StÃ©phane Ducasse wrote: > Cool > I just integrated some changes so I will do 10398 :) > > Stef > On May 17, 2009, at 9:04 PM, Adrian Lienhard wrote: > >> [816] MIT replacement for ScaledDecimal (thanks Nicolas!) >> http://code.google.com/p/pharo/issues/detail?id=816 >> >> >> First step towards a license clean Pharo... >> >> Adrian >> ___________________ >> http://www.adrian-lienhard.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

Re: [Pharo-project] Helping getting pharo license-clean

by StÃ©phane Ducasse

On May 17, 2009, at 10:28 PM, Yoshiki Ohshima wrote: > At Sat, 16 May 2009 10:14:48 +0200, > StÃ©phane Ducasse wrote: >> >> Hi yoshiki >> >> What did you do with code of people that passed away. >> It is obvious that they gave the code for squeak. > > For Russel Swan, re removed his code. For Jerry Archibald, we > contacted his daughter and she signed the relicencing agreement with > us. For Henrik, we removed most of them and rewrite the remaining. > >> Now removing this code >> is like if we do not consider their contribution because they are >> dead. > > I feel the same way and two of the people heirs we managed to > contact with felt the same way. Especially since henrik slept at my place.... > > >> I feel that this license process is a huge shit. > > It pretty much is. > > -- Yoshiki > > > _______________________________________________ > 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] Helping getting pharo license-clean

by StÃ©phane Ducasse

tx! Stef On May 17, 2009, at 10:36 PM, Yoshiki Ohshima wrote: > At Sun, 17 May 2009 11:18:09 +0200, > StÃ©phane Ducasse wrote: >> >> I do not know >> Frankly I do not like this issue. >> May be yoshiki can bring some light. >> I just run his scripts. > > Any methods that existed in 1.1 (1.1x, I forgot), are covered by > Apple. > > -- Yoshiki > > > _______________________________________________ > 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] Helping getting pharo license-clean

by StÃ©phane Ducasse

Pleaseeeeeee! Stef On May 17, 2009, at 9:26 PM, Bryce Kampjes wrote: > I can send in a licence agreement. > > Bryce > > On Sun, 2009-05-17 at 19:46 +0200, Adrian Lienhard wrote: >> I merged in the additional authors of this repository and I updated >> the working list on the Wiki [1]. >> >> We currently have a total of 243 dirty methods. >> >> Does anybody recognize an author on the list that could be contacted? >> (one method of Bryce Kampjes is on the list but should not (will fix >> in the next version)). >> >> Cheers, >> Adrian >> >> [1] http://code.google.com/p/pharo/wiki/ResultofRelicensing?ts=1242581939 >> >> On May 17, 2009, at 16:02 , StÃ©phane Ducasse wrote: >> >>> >>> On May 17, 2 >>>> Well, this mail was not really helpful in getting there but I >>>> eventually managed (after an hour or two :(). >>> >>> Ok sorry >>> This is a copy of the mail I got from matthew and it worked for me >>> So I thought it was precise enough. >>> >>>> So that others can produce the audit list more easily I added >>>> instructions at http://code.google.com/p/pharo/wiki/LicenseCleanEffort?ts=1242566822 >>> >>> Yes I did that. >>> Now you should pay attention that matthew indicated that there are >>> more recent >>> author list available at: >>> >>> The most up-to-date list of ok contributors is at >>> http://www.squeaksource.com/311/MethodAuthorship-kph.17.mcz >>> See the class-side methods in Authorship, category data >>> >>>> As mentioned there, I created a new version of Methodauthorships >>>> and >>>> stored it in the PharoTaskForces repository. I added all authors >>>> that >>>> were previously missing but that signed the Pharo license, or that >>>> Stef identified to be his own changes but with wrong initials. >>>> >>>> With this I produced an updated list and added it to: >>>> >>>> http://code.google.com/p/pharo/wiki/ResultofRelicensing?ts=1242567420 >>>> >>>> >>>> So now we can start working and we need *your* help! >>>> >>>> Nicolas did a first step by implementing a new ScaledDecimal. >>>> Various >>>> stuff can be removed (e.g., the ScaleMorph). >>>> >>>> The following may help: >>>> - in the zip file (see instructions mentioned above) there are >>>> changesets from EToys >>>> - http://bugs.squeak.org/view.php?id=6989 >>>> >>>> Cheers, >>>> Adrian >>>> >>>> >>>>> Stef >>>>> >>>>> On May 16, 2009, at 6:01 PM, Adrian Lienhard wrote: >>>>> >>>>>> Hi Stef, >>>>>> >>>>>> How did you produce the list of methods you put on the wiki page? >>>>>> >>>>>> It seems this will be some work, but its certainly doable. Stuff >>>>>> like >>>>>> ScaleMorph, BlobMorph, SkipList, and ScaledDecimal do not need to >>>>>> be >>>>>> in the core anyway. We can extract them into external packages. >>>>>> >>>>>> I suggest that when we have an up to date list that takes >>>>>> Pharaoers >>>>>> into account, we start working through it and tag each method >>>>>> that >>>>>> is >>>>>> fixed. Changesets can be gathered in a single task in the >>>>>> tracker. >>>>>> >>>>>> Adrian >>>>>> >>>>>> On May 16, 2009, at 09:22 , StÃ©phane Ducasse wrote: >>>>>> >>>>>>> Hi all >>>>>>> >>>>>>> I'm going over the list of authors that did not sign and will >>>>>>> produce >>>>>>> a list of actions. >>>>>>> >>>>>>> http://code.google.com/p/pharo/wiki/ResultofRelicensing >>>>>>> >>>>>>> We will have probably to update the authorlist with the one of >>>>>>> pharo. >>>>>>> >>>>>>> Stef >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >> >> >> _______________________________________________ >> 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

Re: [Pharo-project] Closure compiler

by StÃ©phane Ducasse

adrian may be we should add argumentCount to BlockClosure too. 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 >

May 17, 2009

Re: [Pharo-project] invalid utf8 input detected

by StÃ©phane Ducasse

On May 17, 2009, at 9:42 PM, Nicolas Cellier wrote: > Just to remind my change was not a fix, just a workaround. > We have to discover why these non UTF-8 sources got into the change > file and cure the problem. Otherwise we might suffer a plague of > decompiled code spreading in our browsers :( Yes! Stef

May 17, 2009

Re: [Pharo-project] [ANN] 10307

by StÃ©phane Ducasse

Cool I just integrated some changes so I will do 10398 :) Stef On May 17, 2009, at 9:04 PM, Adrian Lienhard wrote: > [816] MIT replacement for ScaledDecimal (thanks Nicolas!) > http://code.google.com/p/pharo/issues/detail?id=816 > > > First step towards a license clean Pharo... > > Adrian > ___________________ > http://www.adrian-lienhard.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] Helping getting pharo license-clean

by Yoshiki Ohshima

At Sun, 17 May 2009 11:18:09 +0200, StÃ©phane Ducasse wrote: > > I do not know > Frankly I do not like this issue. > May be yoshiki can bring some light. > I just run his scripts. Any methods that existed in 1.1 (1.1x, I forgot), are covered by Apple. -- Yoshiki

May 17, 2009

Re: [Pharo-project] Helping getting pharo license-clean

by Yoshiki Ohshima

At Sat, 16 May 2009 10:14:48 +0200, StÃ©phane Ducasse wrote: > > Hi yoshiki > > What did you do with code of people that passed away. > It is obvious that they gave the code for squeak. For Russel Swan, re removed his code. For Jerry Archibald, we contacted his daughter and she signed the relicencing agreement with us. For Henrik, we removed most of them and rewrite the remaining. > Now removing this code > is like if we do not consider their contribution because they are dead. I feel the same way and two of the people heirs we managed to contact with felt the same way. > I feel that this license process is a huge shit. It pretty much is. -- Yoshiki

May 17, 2009