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

Re: [Pharo-project] Error getting parseTree formattedCode

by Damien Cassou

2009/10/10 Gabriel Brunstein <gaboto(a)gmail.com>: > I think there is a bug when you try to get the formattedCode of a parseTree. > Try this for example: > (Set >> #add:) parseTree formattedCode > I'm sure it worked correctly in previous versions of pharo. > Any idea? Works on the not yet published 09.10.2. Please wait later today for its announcement. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Oct. 11, 2009

Re: [Pharo-project] Error getting parseTree formattedCode

by StÃ©phane Ducasse

I do not know. We should check version prior eliot fixes. stef On Oct 11, 2009, at 12:18 PM, Adrian Lienhard wrote: > The most recent Pharo-core image I has no methods #parseTree and > #formattedCode. What do I miss? > > Adrian > > On Oct 10, 2009, at 22:33 , Gabriel Brunstein wrote: > >> I think there is a bug when you try to get the formattedCode of a >> parseTree. >> Try this for example: >> (Set >> #add:) parseTree formattedCode >> I'm sure it worked correctly in previous versions of pharo. >> Any idea? >> _______________________________________________ >> 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

Oct. 11, 2009

Re: [Pharo-project] Error getting parseTree formattedCode

by Adrian Lienhard

The most recent Pharo-core image I has no methods #parseTree and #formattedCode. What do I miss? Adrian On Oct 10, 2009, at 22:33 , Gabriel Brunstein wrote: > I think there is a bug when you try to get the formattedCode of a > parseTree. > Try this for example: > (Set >> #add:) parseTree formattedCode > I'm sure it worked correctly in previous versions of pharo. > Any idea? > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 11, 2009

Re: [Pharo-project] Pretty print doesn't work on Traits with OB Package Browser

by StÃ©phane Ducasse

I checked and lukas merge AST to get back the PriomitiveNode and Traits. so if you want to get a new pharo-dev here is the script. but it crashed. I did a Smalltalk condenseChanges but it crashed.... I do not know what to do and I have to fix my house now. Stef On Oct 9, 2009, at 9:45 PM, Mariano Martinez Peck wrote: > I forgot to said the fix is the same that is already attached by > damien. It just need to be integrated again :) (I think) > > Cheers, > > mariano > > On Fri, Oct 9, 2009 at 4:39 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > > wrote: > thanks mariano > > Stef > > > This bug is present again :( > > > > http://code.google.com/p/pharo/issues/detail?id=1076 > > > > > > > > On Fri, Aug 21, 2009 at 2:42 PM, Mariano Martinez Peck <marianopeck(a)gmail.com > > > wrote: > > Yep. It is already fixed now. See http://code.google.com/p/pharo/issues/detail?id=1076 > > > > No need to integrate as it is in AST package (it will be integrated > > in next Pharo image I guess). > > > > Best, > > > > Mariano > > > > > > On Fri, Aug 21, 2009 at 3:40 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > > > wrote: > > Do you have the solution to this problem? > > > > Stef > > > > On Aug 20, 2009, at 8:10 PM, Alexandre Bergel wrote: > > > > > Well spotted. I think the Traits package should be updated. No > > need of > > > class extension for this. > > > > > > Cheers, > > > Alexandre > > > > > > > > > On 19 Aug 2009, at 14:23, Mariano Martinez Peck wrote: > > > > > >> Hi! I opened this ticket: http://code.google.com/p/pharo/issues/detail?id=1076 > > >> > > >> This happens when using the OB Package Browser. I am using 10414. > > >> To reproduce: > > >> > > >> 1) Browse any Trait, for example TBehaviorCategorization > > >> 2) Select a method, right button, pretty print > > >> 3) You will get a Trait DNU #formatterClass > > >> > > >> The fix is easy: > > >> > > >> Crate in Trait a instance side method: > > >> > > >> formatterClass > > >> > > >> ^self class formatterClass > > >> > > >> > > >> The thing is that I don't know in which package should this be > > >> commited. AST? > > >> > > >> Best, > > >> > > >> Mariano > > >> > > >> ps: the bug report and fix is thanks to Marcelo Cortez > > >> > > >> > > >> _______________________________________________ > > >> Pharo-project mailing list > > >> Pharo-project(a)lists.gforge.inria.fr > > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > -- > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > Alexandre Bergel http://www.bergel.eu > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > 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

Oct. 11, 2009

Re: [Pharo-project] Preparing the sprint

by Schwab,Wilhelm K

Keith, I used ScriptLoader to get the latest version from squeak source. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of keith Sent: Saturday, October 10, 2009 6:57 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Preparing the sprint On 10 Oct 2009, at 22:50, Schwab,Wilhelm K wrote: > Stef, > > Rio and non-core packages reminds me of #newForWin32, which is > missing a #new, so it answers the class instead of an instance. > This breaks the installation on Windows, and it also leads to a broken > image on Windows if it is not corrected on another OS. > > I _think_ I reported it. > > Bill You would be using an ancient version of Rio, I think I zeroed out the latest of the old packages to prevent people loading them. Both Universes and Sake/Packages have the correct definitions as to which package to load. Keith _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 11, 2009

Re: [Pharo-project] [Seaside] Re: [squeak-dev] [ANN] New SqueakDBX release and good news!!!

by Mariano Martinez Peck

On Sun, Oct 4, 2009 at 7:41 PM, Mariano Martinez Peck <marianopeck(a)gmail.com > wrote: > Thanks for the comments!!! and thanks Damien for the hint. It is fixed now. > > BTW, www.squeakdbx.org is now alive!!!! > > We have a few problems with some ISP and the DNS. If the site is down for you, what you can do temporally is to edit the hosts file ( /etc/hosts/ or c:/windows/system32/hosts) and put this line: 67.205.74.232 www.squeakdbx.org The IP is static, so, there is no problem. Best, Mariano > cheers, > > Mariano > > 2009/10/3 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> > > El sÃ¡b, 03-10-2009 a las 19:09 -0300, Mariano Martinez Peck escribiÃ³: >> > Hi folks! We have a couple of things to announce. >> >> Congratulations. Very good news. >> >> Saludos >> -- >> Miguel CobÃ¡ >> http://miguel.leugim.com.mx >> >> _______________________________________________ >> seaside mailing list >> seaside(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> > >

Oct. 11, 2009

Re: [Pharo-project] Preparing the sprint

by keith

On 10 Oct 2009, at 22:50, Schwab,Wilhelm K wrote: > Stef, > > Rio and non-core packages reminds me of #newForWin32, which is > missing a #new, so it answers the class instead of an instance. > This breaks the installation on Windows, and it also leads to a > broken image on Windows if it is not corrected on another OS. > > I _think_ I reported it. > > Bill You would be using an ancient version of Rio, I think I zeroed out the latest of the old packages to prevent people loading them. Both Universes and Sake/Packages have the correct definitions as to which package to load. Keith

Oct. 10, 2009

Re: [Pharo-project] Preparing the sprint

by Schwab,Wilhelm K

Stef, Rio and non-core packages reminds me of #newForWin32, which is missing a #new, so it answers the class instead of an instance. This breaks the installation on Windows, and it also leads to a broken image on Windows if it is not corrected on another OS. I _think_ I reported it. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse Sent: Saturday, October 10, 2009 3:02 AM To: Pharo Development Subject: [Pharo-project] Preparing the sprint Hi guys I would like to have several kinds of tasks so that people can pick up Now let me know if you have other points - fixing stuff for 1.0 - integrating pending for 1.1 - OB related UI - fixing more elaborated points for 1.1 - package structure - improving the system (smalllint?) - Popup discard - TextEditor from Squeak/CUIS - ToolBuilder changes - checking squeak fixes - Preparing release candidate - fixing _ - free fonts - Dreaming about the future - filesystem? Rio/ - newcompiler - true package - management of noncore packages - browsers - release/integration process BTW what is costing me most of my time is cleaning the inbox. Can we script that because moving these files is a pain. Syeg _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 10, 2009

Re: [Pharo-project] os process crash

by Schwab,Wilhelm K

Just for completeness, which OS are you using? I had an ugly time with the 09.3 web image crashing out from under ODBC; that was on Linux, though if I get that working, I can also test it on Windows. I was distracted with Polymorph, deploying an image for a "release" build of a home-grown utility of mine that now runs on Linux (another small crack in a Redmond sidewalk), and initial porting of more of my software to Pharo. That's a long way around to the point, which is that I am hanging my head in shame for not following up on the ODBC crash :) A beer at a future meeting says that our two respective problems are related. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Michael Roberts Sent: Saturday, October 10, 2009 4:12 PM To: Pharo-project Subject: [Pharo-project] os process crash folks, i'm trying to load OS Process into the latest pharo-core on my mac. it crashes the image when i try and run the tests. Does anyone have sucess on a recent pharo-core? thanks, Mike _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 10, 2009

Re: [Pharo-project] All debugger variables are now quoted

by StÃ©phane Ducasse

Ok we should check that. This week I will run a conference and got some house problems so my time will be counted. Stef On Oct 10, 2009, at 5:21 PM, Michael Roberts wrote: > In a recent image all debugger stack variables are now quoted. e.g > 'nil'. > > I think the fix to issue 987 perhaps had an unintended side-effect but > we will need to check. > http://code.google.com/p/pharo/issues/detail?id=987 > > If we confirm it's this one we can reopen it, or make a new one. > > thanks, > Mike > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 10, 2009