October 2008 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] About trait mop

by Adrian Lienhard

On Oct 11, 2008, at 09:39 , Marcus Denker wrote: > On 10.10.2008, at 14:30, StÃ©phane Ducasse wrote: > >>> I had a look and I like it, so I'll try to make your tests pass ;). >>> >>> I don't agree with the following, though: >>> >>>> self assert: (D>>#c3) origin = D. "this is a question because it >>>> could be " >>> >>> here I think it should be Trait2, not D. The alias c3->c2 does not >>> redefine the method in the class; the method still originates in >>> Trait2. >> >> >> Not really :) >> we discussed a lot with and I think that I have a point :) >> the point is that since Compiled Method are copied > > But even non-aliased methods are copied... > >> so c3 is really different from c2 >> and c3 is not defined in Trait2 but this is realy because there is >> D that C3 exists. >> so tell me what you think. > > The problem with making the origin D is that then the relationship > "all methods that have the origin class D are local methdos in class > D" is not true anymore. > marcus > I think it is more important to have this true for classes then for > Traits. I agree with Marcus. The origin of a method for me means the behavior (trait or class) in which a method is originally defined. That is, if I want to modify the method without overriding it, this is the place to do it. Therefore, even though D introduces a new name for the method, the method still originates in Trait2. Adrian

Oct. 11, 2008

[Pharo-project] [MC] Adding a constraint when declaring a required package

by Alexandre Bergel

Maybe we should forbid a package XXX-YYY to be required for a package named XXX What do you think? A simple check will do it... Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Oct. 11, 2008

[Pharo-project] DependencyBrowser

by Alexandre Bergel

Dear List, I tried DependencyBrowser, it is intuitive and easy to use. I think this tool deserve to have an entry in ScriptLoader Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Oct. 11, 2008

[Pharo-project] Pharo Harvesting Infrastructure

by Matthew Fulmer

Hi. I found a bug in Pharo, and I started wondering how to determine where it came from. I checked a few methods in the debugger to see if they had recently been modified, but that was no help. I checked the change sorter to see if it had any idea what had been recently installed, but it was choked by Monticello updates. Then I opened a new Pharo Image in order to try each update one by one (whatever Monticello you guys use to load your changes is *really* slow. I gotta fix you guys up with MC1.6). But before I did that, I noticed on the right of the screen is something that looks like a change log. And at the bottom, it said: (full list of changes: print "ScriptLoader new logContents") So I tried it in my 10091 image, and sure enough, it printed up a changelog. So I went to see what this mysterious class ScriptLoader is. I found a whole lot of methods. Some looked auto-generated. Some seemed to be convenience methods for loading MC packages from Pharo and PharoInbox. It looks kind of like Installer, which I am more familiar with. I'm rather curious now about how you manage Pharo. I took a look at http://code.google.com/p/pharo/wiki/HowToContribute and wondered what happens after that. I now imagine it involves ScriptBuilder building the update, and then something uploading it. What is the mechanism? How is Pharo tested? is it regularly tested by someone using TestRunner, or something fancier? What are all the auto-generated methods in ScriptLoader for? How do you typically trace a bug from image to problem package to update to issue? I'm interested because keith and I are building a build server that is able to build images, build packages, load packages, run tests, build VM's and such, all automated and with an easy interface. So far, we have the easy interface (Installer), but are still working on making it do more. So I'm interested in learning how it works here, so that we can at least end up with something as good as this -- Matthew Fulmer -- http://mtfulmer.wordpress.com/

Oct. 11, 2008

Re: [Pharo-project] About trait mop

by Marcus Denker

On 10.10.2008, at 14:30, StÃ©phane Ducasse wrote: >> >> >> I had a look and I like it, so I'll try to make your tests pass ;). >> >> I don't agree with the following, though: >> >>> self assert: (D>>#c3) origin = D. "this is a question because it >>> could be " >> >> here I think it should be Trait2, not D. The alias c3->c2 does not >> redefine the method in the class; the method still originates in >> Trait2. > > > Not really :) > we discussed a lot with marcus and I think that I have a point :) > the point is that since Compiled Method are copied But even non-aliased methods are copied... > so c3 is really different from c2 > and c3 is not defined in Trait2 but this is realy because there is D > that C3 exists. > so tell me what you think. The problem with making the origin D is that then the relationship "all methods that have the origin class D are local methdos in class D" is not true anymore. I think it is more important to have this true for classes then for Traits. Marcus -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Oct. 11, 2008

Re: [Pharo-project] Re: Universe Browser - search

by Dan Corneanu

I would too, but completion is not working in the dev image :) Has the shortcut changed? I use CTRL-Space. On Tue, Oct 7, 2008 at 11:40 AM, Simon Kirk <simon(a)pinesoft.co.uk> wrote: > Sorry Damian: I would, but I'm afraid I don't understand what the fix > actually is as described in that mantis bug. > > Cheers, > Simon > > On 7 Oct 2008, at 06:44, Damien Cassou wrote: > >> On Mon, Oct 6, 2008 at 9:40 PM, Dan Corneanu <dan.corneanu(a)gmail.com> >> wrote: >>>> >>>> It has a search, but the last time I tried it it didn't actually find >>>> anything for any given string (perhaps I just had a bad experience) >>> >>> Neither did I :) >> >> Would you mind trying the following fix and tell me if it works? >> http://bugs.squeak.org/view.php?id=6798 >> >> -- >> Damien Cassou >> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good >> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > ****************************************************************************************************************************************** > This email is from Pinesoft Limited. Its contents are confidential to the > intended recipient(s) at the email address(es) to which it has been > addressed. It may not be disclosed to or used by anyone other than the > addressee(s), nor may it be copied in anyway. If received in error, please > contact the sender, then delete it from your system. Although this email and > attachments are believed to be free of virus, or any other defect which > might affect any computer or IT system into which they are received and > opened, it is the responsibility of the recipient to ensure that they are > virus free and no responsibility is accepted by Pinesoft for any loss or > damage arising in any way from receipt or use thereof. > ******************************************************************************************************************************************* > > > Pinesoft Limited are registered in England, Registered number: 2914825. > Registered office: 266-268 High Street, Waltham Cross, Herts, EN8 7EA > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 10, 2008

[Pharo-project] Re: #2

by nicolas cellier

nicolas cellier <ncellier@...> writes: > > Anyway, even with NewCompiler, #isLiteralSymbol: and also #numArgs need fixes. > These two are probably related to alternate syntax experiments. > Google this one: > alternate syntax site:lists.squeakfoundation.org > > Since bugs are hanging around for too long, it is high time to correct. > > http://lists.squeakfoundation.org/pipermail/squeak-dev/2000-April/005341.ht… > http://lists.squeakfoundation.org/pipermail/squeak-dev/2004-March/075166.ht… > http://lists.squeakfoundation.org/pipermail/squeak-dev/2007-May/117145.html > > and also: > http://lists.squeakfoundation.org/pipermail/squeak-dev/2007-July/119095.html > > Pharo is the ideal place to commit these changes. > I will give it a try. > For #isLiteralSymbol: See issue http://code.google.com/p/pharo/issues/detail?id=236 For test and patch see PharoInbox Compiler-nice.73 Nicolas

Oct. 10, 2008

[Pharo-project] Re: #2

by nicolas cellier

nicolas cellier <ncellier@...> writes: > > ## is questionable: we can accept such a syntax, but what for exactly? > > If no valuable reason, shouldn't we better enforce syntaxic check in Parser and > signal malformed statements as an error as would any other Smalltalk? > > Quite sure that NewCompiler already fix all this stuff. > What are the plans about its integration? > Waiting for Eliot's COG? > Anyway, even with NewCompiler, #isLiteralSymbol: and also #numArgs need fixes. These two are probably related to alternate syntax experiments. Google this one: alternate syntax site:lists.squeakfoundation.org Since bugs are hanging around for too long, it is high time to correct. http://lists.squeakfoundation.org/pipermail/squeak-dev/2000-April/005341.ht… http://lists.squeakfoundation.org/pipermail/squeak-dev/2004-March/075166.ht… http://lists.squeakfoundation.org/pipermail/squeak-dev/2007-May/117145.html and also: http://lists.squeakfoundation.org/pipermail/squeak-dev/2007-July/119095.html Pharo is the ideal place to commit these changes. I will give it a try.

Oct. 10, 2008

Re: [Pharo-project] Monticello 1.6 or 2.0?

by StÃ©phane Ducasse

1 and 1.6 are the same so there is no 3 mc but two. for 20 we will see when we can use repositories and what are the patterns. So for now the most important aspect is to have a robust MC 1.x with atomic loading and trait support. Stef On Oct 10, 2008, at 8:37 PM, Janko MivÅ¡ek wrote: > Hello, > > We have now three Monticellos: 1, 1.6 and 2.0. What is the Pharo > plans here, to go to 1.6 then to 2.0? How to migrate old > repositories like SqueakSource? When to migrate? How to persuade all > Squeakers to upgrade MC in their images? > > That questions which are raising in my mind for a while... > > Janko > > > -- > Janko MivÅ¡ek > AIDA/Web > Smalltalk Web Application Server > http://www.aidaweb.si > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 10, 2008

[Pharo-project] Monticello 1.6 or 2.0?

by Janko MivÅ¡ek

Hello, We have now three Monticellos: 1, 1.6 and 2.0. What is the Pharo plans here, to go to 1.6 then to 2.0? How to migrate old repositories like SqueakSource? When to migrate? How to persuade all Squeakers to upgrade MC in their images? That questions which are raising in my mind for a while... Janko -- Janko MivÅ¡ek AIDA/Web Smalltalk Web Application Server http://www.aidaweb.si

Oct. 10, 2008