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

Re: [Pharo-project] Cross-fork Metacello configurations

by Miguel Enrique CobÃ¡ Martinez

El dom, 23-05-2010 a las 09:39 +0200, Nicolas Cellier escribiÃ³: > Miguel, > It sounds like a defensive attitude. What good can emerge from sharing > such mood? > You don't deliver any technical argumentation, but "I think it's > wrong" and "it upsets me". > I'm sure you have more rational reasons to dislike squeak usage, that > would be interesting to expose. I don't dislike Squeak usage but changing a emerging technology that is being used in a given way and that appears to be working (I've done the Magma configuration and I tested it worked on Squeak and Pharo) but this new Squeak usage of Metacello really discourages to try to keep the Magma for other distros than Pharo. It really is a gratuitous change and I don't really have the time to sync two ways to use the same technology. > Squeak people are not going to rape your wife nor kill your children. Again, is not the people, is the gratuitous change for a perceived problem with Metacello current usage. > Qu'un sang impur abreuve nos sillons No sÃ© que significa pero supongo que es relevante en esta discusiÃ³n. Cheers > > Nicolas > > 2010/5/22 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com>: > > But, but... > > > > One thing that I really don't understand is this: > > > > Squeak people hasn't used the current Metacello "use-case". > > Squeak people without use it and see if really has problems (nothing > > that can't be solved when it appears) > > Squeak people proposed a new way to use Metacello, completly different > > than the one is being used > > Squeak arguments were about some potential problems with having > > configurations outside the image > > Squeak arguments were abouth the potential advantages of having a > > browser that browses locally (but as Mariano said, it must be updated > > from net before having the very last package tested to work available in > > the browser) instead of going to the network for the list. > > > > So, this, hey look what I found, they use it this way, but I think that > > we should use it that other way, no matter if it is really a problem to > > use it the way the other people use it really upsets me. > > > > Heck, Pharo even build the released dev images with Metacello. That is a > > "real" world usage and not words. > > > > > > El vie, 21-05-2010 a las 16:17 -0700, Dale Henrichs escribiÃ³: > >> I had suggested that they not use the ConfigurationOf prefix for the Squeak configuration package so that cross platform configurations could continue to be used ... I would hope that folks continue to to create cross platform packages ... the onus on copying shouldn't be on the developer, but the folks that want a managed list of configs:) > >> > >> I would think that the managed list could be harvested from the ConfigurationOf configs without any direct developer involvement...afterall computers should be used for the things they are good at:) > >> > >> It will be interesting to see how the managed list idea evolves... > >> > >> Dale > >> ________________________________________ > >> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Miguel Enrique CobÃ¡ Martinez [miguel.coba(a)gmail.com] > >> Sent: Friday, May 21, 2010 10:42 AM > >> To: Pharo-project(a)lists.gforge.inria.fr > >> Subject: Re: [Pharo-project] Cross-fork Metacello configurations > >> > >> El vie, 21-05-2010 a las 09:13 -0700, Sean P. DeNigris escribiÃ³: > >> > I created a Squeak/Pharo SSpec, which puts the fork-specific world menu code > >> > into a Platform package. > >> > > >> > As I work on the config, I came up against Pharo using Object as a subclass, > >> > but the Squeak Inbox requiring (because of the browser tool) > >> > MetacelloConfiguration. > >> > > >> > What would be the best/easiest way to deal with this? > >> > > >> > If the configs have to be forked, then Metacello really loses value (i.e. > >> > #squeak and #pharo). And, I do a lot of work in both forks, so it would be > >> > a shame to pick one to upload to and not share work that has already been > >> > done with half the users. > >> > >> That was one of the problems of the Configuration Package proposed by > >> Andreas. Promotes copy&paste of configurations (bad bad) and in the long > >> term forks and completely rework to create configurations for Squeak and > >> a different (although similar) for Pharo. > >> As you say, it doesn't matter that Metacello is capable of installing > >> cross-platform packages. With independently created configurations for > >> the same packages, is has been stole of its usefulness and is > >> discouraging Pharo users that have developed ConfigurationOfXXX that > >> worked both in Squeak and Pharo in the past. > >> > >> > >> > >> > > >> > Thanks. > >> > Sean > >> > > >> > >> -- > >> Miguel CobÃ¡ > >> http://miguel.leugim.com.mx > >> > >> > >> _______________________________________________ > >> 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 > > > > -- > > Miguel CobÃ¡ > > http://miguel.leugim.com.mx > > > > > > _______________________________________________ > > 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 -- Miguel CobÃ¡ http://miguel.leugim.com.mx

May 23, 2010

Re: [Pharo-project] [BUG] VM crash during debbuging some code by Through button with Transcript>>show: in deepest inner methods

by Denis Kudriashov

I found more bad cases with code simulation. And I think any manipulations with context (errors signals, simaphore, ...) not work in simulation mode. Transcript printing failed because of simaphore accessing (for thread safety) I create CodeSimulationTests (see attachement) with some tests which not work and which crash VM. Maybe this tests not correct. But I hope it helps to indicate and solve issues 2010/5/23 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Thanks! > > Stef > > On May 23, 2010, at 11:13 AM, Denis Kudriashov wrote: > > > And If you replace Transcript code with > > > > self halt. > > > > You will see that debugging with through button does not work. Code > simulation failure raised (but without VM crash) > > > > 2010/5/23 Denis Kudriashov <dionisiydk(a)gmail.com> > > I has Pharo1.0 one click, Windows 7. > > I attach class ClassWithTranscriptPrinting. > > see class side method #debug > > > > > > > > > > > > 2010/5/23 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > > > Hi denis > > > > can you report clearly your bug > > - image > > - vm > > - os > > - scenario > > > > I could not compile > > Transcript>>show:'something' > > > > so I do not know how you did it. > > > > > > > > On May 23, 2010, at 10:11 AM, Denis Kudriashov wrote: > > > > > Hello > > > > > > Just insert > > > Transcript>>show:'something' > > > at any method begin. > > > > > > Now debug sender of your method by debugger Through button. > > > > > > If no Transcript opened VM will crash! > > > _______________________________________________ > > > 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 23, 2010

Re: [Pharo-project] ClassTestCase

by Mariano Abel Coca

There are few now, but it was done yesterday in a few hours. We will keep adding new tests to that suites, so suggestions are welcome :). Actually there are only 3 tests there: - One that checks that all the methods in the image are categorized - One that checks that never redefine #doesNotUnderstand: without redefining #respondsTo: and vice versa. - And one that checks that never sent = nil, ==nil, nil =, or nil ==, ~= nil, etc. as suggested in issue 1594 (Actually, after reading this issue is that we started with this idea). Cheers, Mariano. On Sun, May 23, 2010 at 4:53 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Sounds exciting can you tell us a bit more? > > On May 23, 2010, at 2:54 AM, Mariano Abel Coca wrote: > > > If anyone want, can take a look at: > > > > http://www.squeaksource.com/CodeQualityTests > > http://www.squeaksource.com/CodeStandardsTests > > > > And run the tests before committing the next version of their packages. > > > > We will try to help to pass the tests as soon as possible. > > > > Cheers, > > > > Mariano. > > > > > > On Sat, May 22, 2010 at 8:06 PM, Francisco Ortiz PeÃ±aloza < > patchinko(a)gmail.com> wrote: > > We're working on it, making small changes and creating code standards > > tests and code quality tests. > > > > It would be great to have a way of tracking the results of these tests > > in a distant future and make them mandatory before integrate new > > things into the image. > > > > Francisco > > > > On Sat, May 22, 2010 at 7:17 PM, StÃ©phane Ducasse > > <stephane.ducasse(a)inria.fr> wrote: > > > What I was thinking mariano is that we could move one class at a time > in classTests and make the tests green. > > > This way we do not have red tests and still make progress > > > Stef > > > > > > > > > On May 22, 2010, at 8:06 PM, Mariano Abel Coca wrote: > > > > > >> It is a must. We have to got all the tests in green. But actually that > isn't tested. > > >> > > >> I'll make the tests, I'll fix them, and then I'll send the whole > changes to merge in the baseline. > > >> > > >> Cheers, > > >> > > >> Mariano. > > >> > > >> > > >> On Sat, May 22, 2010 at 2:58 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > > >> the key point is that we would like to avoid to have red tests all the > time > > >> so fixing the as yet unclassified should be done before. > > >> > > >> > > >> BTW Does anybody use > > >> BadEqualer > > >> HashTester > > >> PrototypeTester > > >> > > >> because so far I do not see anybody user of them. > > >> They look like experiment code to me. > > >> > > >> Stef > > >> > > >> On May 22, 2010, at 7:31 PM, Mariano Abel Coca wrote: > > >> > > >> > Hi, I want to make global the checks included in ClassTestCase, and > remove it. That is because actually it's only being tested for it's > subclasses. And also, it's declaring that a subclass will be a class test > instead of just a test, but no one of it's subclasses actually test the > class, but the instances, therefore is a TestCase, not a ClassTestCase. See > TimespanTest as an example. > > >> > > > >> > What Im saying is that I'm trying to force a run of a suit of Code > Standards and Code Quality tests before sending something to merge to a > baseline of a project. > > >> > > > >> > What do you think? Are you agree with that? > > >> > > > >> > Cheers, > > >> > > > >> > Mariano. > > >> > _______________________________________________ > > >> > 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 23, 2010

Re: [Pharo-project] [BUG] VM crash during debbuging some code by Through button with Transcript>>show: in deepest inner methods

by StÃ©phane Ducasse

Thanks! Stef On May 23, 2010, at 11:13 AM, Denis Kudriashov wrote: > And If you replace Transcript code with > > self halt. > > You will see that debugging with through button does not work. Code simulation failure raised (but without VM crash) > > 2010/5/23 Denis Kudriashov <dionisiydk(a)gmail.com> > I has Pharo1.0 one click, Windows 7. > I attach class ClassWithTranscriptPrinting. > see class side method #debug > > > > > > 2010/5/23 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > Hi denis > > can you report clearly your bug > - image > - vm > - os > - scenario > > I could not compile > Transcript>>show:'something' > > so I do not know how you did it. > > > > On May 23, 2010, at 10:11 AM, Denis Kudriashov wrote: > > > Hello > > > > Just insert > > Transcript>>show:'something' > > at any method begin. > > > > Now debug sender of your method by debugger Through button. > > > > If no Transcript opened VM will crash! > > _______________________________________________ > > 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 23, 2010

Re: [Pharo-project] [BUG] VM crash during debbuging some code by Through button with Transcript>>show: in deepest inner methods

by Denis Kudriashov

And If you replace Transcript code with self halt. You will see that debugging with through button does not work. Code simulation failure raised (but without VM crash) 2010/5/23 Denis Kudriashov <dionisiydk(a)gmail.com> > I has Pharo1.0 one click, Windows 7. > I attach class ClassWithTranscriptPrinting. > see class side method #debug > > > > > > 2010/5/23 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > Hi denis >> >> can you report clearly your bug >> - image >> - vm >> - os >> - scenario >> >> I could not compile >> Transcript>>show:'something' >> >> so I do not know how you did it. >> >> >> >> On May 23, 2010, at 10:11 AM, Denis Kudriashov wrote: >> >> > Hello >> > >> > Just insert >> > Transcript>>show:'something' >> > at any method begin. >> > >> > Now debug sender of your method by debugger Through button. >> > >> > If no Transcript opened VM will crash! >> > _______________________________________________ >> > 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 23, 2010

Re: [Pharo-project] [BUG] VM crash during debbuging some code by Through button with Transcript>>show: in deepest inner methods

by Denis Kudriashov

I has Pharo1.0 one click, Windows 7. I attach class ClassWithTranscriptPrinting. see class side method #debug 2010/5/23 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Hi denis > > can you report clearly your bug > - image > - vm > - os > - scenario > > I could not compile > Transcript>>show:'something' > > so I do not know how you did it. > > > > On May 23, 2010, at 10:11 AM, Denis Kudriashov wrote: > > > Hello > > > > Just insert > > Transcript>>show:'something' > > at any method begin. > > > > Now debug sender of your method by debugger Through button. > > > > If no Transcript opened VM will crash! > > _______________________________________________ > > 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 23, 2010

Re: [Pharo-project] [BUG] VM crash during debbuging some code by Through button with Transcript>>show: in deepest inner methods

by StÃ©phane Ducasse

Hi denis can you report clearly your bug - image - vm - os - scenario I could not compile Transcript>>show:'something' so I do not know how you did it. On May 23, 2010, at 10:11 AM, Denis Kudriashov wrote: > Hello > > Just insert > Transcript>>show:'something' > at any method begin. > > Now debug sender of your method by debugger Through button. > > If no Transcript opened VM will crash! > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 23, 2010

[Pharo-project] [BUG] VM crash during debbuging some code by Through button with Transcript>>show: in deepest inner methods

by Denis Kudriashov

Hello Just insert Transcript>>show:'something' at any method begin. Now debug sender of your method by debugger Through button. If no Transcript opened VM will crash!

May 23, 2010

Re: [Pharo-project] ClassTestCase

by StÃ©phane Ducasse

Sounds exciting can you tell us a bit more? On May 23, 2010, at 2:54 AM, Mariano Abel Coca wrote: > If anyone want, can take a look at: > > http://www.squeaksource.com/CodeQualityTests > http://www.squeaksource.com/CodeStandardsTests > > And run the tests before committing the next version of their packages. > > We will try to help to pass the tests as soon as possible. > > Cheers, > > Mariano. > > > On Sat, May 22, 2010 at 8:06 PM, Francisco Ortiz PeÃ±aloza <patchinko(a)gmail.com> wrote: > We're working on it, making small changes and creating code standards > tests and code quality tests. > > It would be great to have a way of tracking the results of these tests > in a distant future and make them mandatory before integrate new > things into the image. > > Francisco > > On Sat, May 22, 2010 at 7:17 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: > > What I was thinking mariano is that we could move one class at a time in classTests and make the tests green. > > This way we do not have red tests and still make progress > > Stef > > > > > > On May 22, 2010, at 8:06 PM, Mariano Abel Coca wrote: > > > >> It is a must. We have to got all the tests in green. But actually that isn't tested. > >> > >> I'll make the tests, I'll fix them, and then I'll send the whole changes to merge in the baseline. > >> > >> Cheers, > >> > >> Mariano. > >> > >> > >> On Sat, May 22, 2010 at 2:58 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> the key point is that we would like to avoid to have red tests all the time > >> so fixing the as yet unclassified should be done before. > >> > >> > >> BTW Does anybody use > >> BadEqualer > >> HashTester > >> PrototypeTester > >> > >> because so far I do not see anybody user of them. > >> They look like experiment code to me. > >> > >> Stef > >> > >> On May 22, 2010, at 7:31 PM, Mariano Abel Coca wrote: > >> > >> > Hi, I want to make global the checks included in ClassTestCase, and remove it. That is because actually it's only being tested for it's subclasses. And also, it's declaring that a subclass will be a class test instead of just a test, but no one of it's subclasses actually test the class, but the instances, therefore is a TestCase, not a ClassTestCase. See TimespanTest as an example. > >> > > >> > What Im saying is that I'm trying to force a run of a suit of Code Standards and Code Quality tests before sending something to merge to a baseline of a project. > >> > > >> > What do you think? Are you agree with that? > >> > > >> > Cheers, > >> > > >> > Mariano. > >> > _______________________________________________ > >> > 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 23, 2010

Re: [Pharo-project] ClassTestCase

by StÃ©phane Ducasse

> We're working on it, making small changes and creating code standards > tests and code quality tests. > > It would be great to have a way of tracking the results of these tests > in a distant future and make them mandatory before integrate new > things into the image. Francisco Three points: - I agree on the principle. Normally I read all the code that is integrated - now we should pay attention. I prefer to put code that make progress but is not perfect versus doing nothing and waiting for a better one - then people can comment on the submission made on the tracker but really few do it. So what is the solution let the code rot there? And kill our good energy. So you see nothing is simple. This is clear that having a nice bunch of SmallLint rules should not hurt :) Stef > > Francisco > > On Sat, May 22, 2010 at 7:17 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> What I was thinking mariano is that we could move one class at a time in classTests and make the tests green. >> This way we do not have red tests and still make progress >> Stef >> >> >> On May 22, 2010, at 8:06 PM, Mariano Abel Coca wrote: >> >>> It is a must. We have to got all the tests in green. But actually that isn't tested. >>> >>> I'll make the tests, I'll fix them, and then I'll send the whole changes to merge in the baseline. >>> >>> Cheers, >>> >>> Mariano. >>> >>> >>> On Sat, May 22, 2010 at 2:58 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> the key point is that we would like to avoid to have red tests all the time >>> so fixing the as yet unclassified should be done before. >>> >>> >>> BTW Does anybody use >>> BadEqualer >>> HashTester >>> PrototypeTester >>> >>> because so far I do not see anybody user of them. >>> They look like experiment code to me. >>> >>> Stef >>> >>> On May 22, 2010, at 7:31 PM, Mariano Abel Coca wrote: >>> >>>> Hi, I want to make global the checks included in ClassTestCase, and remove it. That is because actually it's only being tested for it's subclasses. And also, it's declaring that a subclass will be a class test instead of just a test, but no one of it's subclasses actually test the class, but the instances, therefore is a TestCase, not a ClassTestCase. See TimespanTest as an example. >>>> >>>> What Im saying is that I'm trying to force a run of a suit of Code Standards and Code Quality tests before sending something to merge to a baseline of a project. >>>> >>>> What do you think? Are you agree with that? >>>> >>>> Cheers, >>>> >>>> Mariano. >>>> _______________________________________________ >>>> 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 23, 2010