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

Re: [Pharo-project] MC breakage in 1.1

by Julian Fitzell

On Tue, Jun 15, 2010 at 12:12 AM, Julian Fitzell <jfitzell(a)gmail.com> wrote: > It seems that in Pharo 1.1 MC no longer displays the Version window > after a failed commit attempt (due to missing authentication for > example). As a result, cannot easily resubmit the version after fixing > the credentials. > > In fact, as I look further, it's worse than that. Let's say I had > version 1 and changed two methods. After the failed commit the > following seems to be the situation: > > - The ancestor of my working copy is 2 instead of 1 (confirmed with History) > - The working copy is dirty > - The Changes button shows the same two modified methods that I was > trying to save into 2 > - The diff between 1 and 2 shows the two modified methods > - The diff between 2 and my image (as selected from the History > window) shows no changes Actually, most of the additional points are ok. The Changes button is, of course, relative to the selected repository (I say of course, not because that's necessarily intuitive but because I was previously aware of it) so that's why it showed the changes still. The ancestry information is all correct and opening up the package-cache to resubmit the version did get me back in business. I still think digging into the package cache to find it is not an optimum solution to this fairly common problem, though. Julian

June 14, 2010

[Pharo-project] MC breakage in 1.1

by Julian Fitzell

It seems that in Pharo 1.1 MC no longer displays the Version window after a failed commit attempt (due to missing authentication for example). As a result, cannot easily resubmit the version after fixing the credentials. In fact, as I look further, it's worse than that. Let's say I had version 1 and changed two methods. After the failed commit the following seems to be the situation: - The ancestor of my working copy is 2 instead of 1 (confirmed with History) - The working copy is dirty - The Changes button shows the same two modified methods that I was trying to save into 2 - The diff between 1 and 2 shows the two modified methods - The diff between 2 and my image (as selected from the History window) shows no changes Eek! Julian

June 14, 2010

Re: [Pharo-project] SmaCC

by Alexandre Bergel

> I started reading about Moose (esp Meta-environment and executable > meta-language using smalltalk) and it was all about languages with > introspection. SAS has no such ability, and is not even object > oriented. So it didn't seem like a good fit. Have I misunderstood--for > example, are the remarks directed more at smalltalk as an implementation > language for Moose? As soon as you provide a parser and a meta-model for your language, then moose is your friend. Independently if your language is object-oriented or not. I build an importer for C for Moose. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 14, 2010

Re: [Pharo-project] SmaCC

by Ross Boylan

On Mon, 2010-06-14 at 18:31 -0400, Alexandre Bergel wrote: > Hi Ross, > > > Thanks for the pointer, and for making it. I'm going to try it (I'm > > building a SAS parser). > > It would be very cool if your parser can be part of Moose (http://moosetechnology.org) > By doing your metamodel as an extension of FAMIX, you will have tons of tools for navigation and visualization that comes for free. > > Cheers, > Alexandre I started reading about Moose (esp Meta-environment and executable meta-language using smalltalk) and it was all about languages with introspection. SAS has no such ability, and is not even object oriented. So it didn't seem like a good fit. Have I misunderstood--for example, are the remarks directed more at smalltalk as an implementation language for Moose? In other ways some kind of preexisting framework would be helpful. I'm making the parser because I want to understand where a particular dataset, and then a particular variable in the dataset, came from. Ross

June 14, 2010

[Pharo-project] PetitParser

by Ross Boylan

http://www.lukas-renggli.ch/blog/petitparser-1 says The class side of PPPredicateParser provides a lot of other factory methods that can be used to build more complex terminal parsers. The class side is empty. Has the material perhaps moved to PPPredicateObjectParser, which has lots of stuff? Ross

June 14, 2010

Re: [Pharo-project] SmaCC

by Alexandre Bergel

Hi Ross, > Thanks for the pointer, and for making it. I'm going to try it (I'm > building a SAS parser). It would be very cool if your parser can be part of Moose (http://moosetechnology.org) By doing your metamodel as an extension of FAMIX, you will have tons of tools for navigation and visualization that comes for free. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 14, 2010

Re: [Pharo-project] SmaCC

by Ross Boylan

On Mon, 2010-06-14 at 23:33 +0200, Lukas Renggli wrote: > > If you are looking for SmaCC execute the following Gofer scripts. > Seriously, if you are looking at SmaCC you should have a look at > PetitParser first <http://www.lukas-renggli.ch/blog/petitparser-1> :-) Thanks for the pointer, and for making it. I'm going to try it (I'm building a SAS parser). BTW I loaded PetitGui, but when I do PPBrowser open there's a reference to the class GLMTabulator, which is not in my image. I had previously loaded moose, but it seems very tightly coupled to smalltalk, so I tossed it. Ross

June 14, 2010

Re: [Pharo-project] SmaCC

by Lukas Renggli

> I would appreciate help on any or all of figuring out how to use SmaCC, > loading SmaCCDev (or any other packages) and info about package > management in Pharo. If you are looking for SmaCC execute the following Gofer scripts. Seriously, if you are looking at SmaCC you should have a look at PetitParser first <http://www.lukas-renggli.ch/blog/petitparser-1> :-) " Prerequisites " Gofer new squeaksource: 'rb'; package: 'AST-Core'; package: 'Refactoring-Core'; load. " SmaCC runtime and development tools " Gofer new squeaksource: 'SmaccDevelopment'; package: 'SmaCC'; package: 'SmaCCDev'; load. Lukas -- Lukas Renggli www.lukas-renggli.ch

June 14, 2010

Re: [Pharo-project] Unwind errors: worse in 1.1?

by Schwab,Wilhelm K

Ok, I'll give it a try. Fortunately, I am not seeing it with every notifier like in the one image. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Chris Muller Sent: Monday, June 14, 2010 4:08 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Unwind errors: worse in 1.1? I don't know what causees those either, but if you just want to dismiss the debugger window, try Proceed. On Sat, Jun 12, 2010 at 5:11 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > I have long intermittently seen errors with walkbacks titled "Unwind error during termination." Â They might be more common in 1.1, and worse, I am now unable to close the offending notifiers/debuggers. Â I also tried "close all debuggers" without success. > > Bill > > _______________________________________________ > 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

June 14, 2010

Re: [Pharo-project] Unwind errors: worse in 1.1?

by Chris Muller

I don't know what causees those either, but if you just want to dismiss the debugger window, try Proceed. On Sat, Jun 12, 2010 at 5:11 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > I have long intermittently seen errors with walkbacks titled "Unwind error during termination." Â They might be more common in 1.1, and worse, I am now unable to close the offending notifiers/debuggers. Â I also tried "close all debuggers" without success. > > Bill > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 14, 2010