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

[Pharo-project] Feature request for Opal
by Igor Stasenko Sept. 29, 2010

Sept. 29, 2010

I want an API for easy plugging in an arbitrary pragma handler, which could then either completely intercept parser/compiler output or modify output. This is userful for things like clean implementation of FFI pragmas, without patching the Parser as well as for scenarios like: myMethod: myArg <myLanguage> foo|<bar**baz so, once pragma <myLanguage> parsed, and handled, an input source stream redirected to completely different parser/compier pair which, of course, should produce a compiled method as a result, but may use any syntax. -- Best regards, Igor Stasenko AKA sig.

4 5

Re: [Pharo-project] After loading a package...all changes with "revision changed"
by StÃ©phane Ducasse Sept. 29, 2010

Sept. 29, 2010

it would be nice to have a simple case that we can reproduce. Stef On Sep 27, 2010, at 10:42 PM, Mariano Martinez Peck wrote: > > > 2010/9/26 Javier PimÃ¡s <elpochodelagente(a)gmail.com> > We had a similar problem in squeaknos package, but just for some kind of classes. It was caused by having an initialize class method in classes derived from ExternalStructure, maybe it's because of the same reason? look there, you may get some answers. > > > Thanks. It is good to know I am not the only one. This bug is REAAAAALY annoying since you cannot see your changes. > > I've checked and I have no #initialize at class level :( > > The only thing I found is class side #new implementd something like: > > new > > ^super new initialize. > > can this be the problem? > > where could I put a halt to see the problem ? > > thanks in advance > > mariano > > > regards, > javier. > > 2010/9/26 Norbert Hartl <norbert(a)hartl.name> > > FYI I encountered the same problem in gemstone. The only thing I know is that all loaded packages were created in pharo that showed this behaviour. It didn't show up in a reproducable manner and some packages were clean again after a few package updates. And for some month now I didn't see it. > > Norbert > > > Am 25.09.2010 um 21:12 schrieb Mariano Martinez Peck <marianopeck(a)gmail.com>: > >> >> >> On Sat, Sep 25, 2010 at 9:02 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> On Sep 25, 2010, at 8:25 PM, Mariano Martinez Peck wrote: >> >> > Hi. I am having a probem with Glorp and I really have no idea what can be. The problem is that I load the package Glorp and just after loading, I do a "changes" in the MC Browser and I see a lot of classes with a lot of changes and all of them like "revison changed". This is annoying since it doesn't let me easily see what I have really changed. >> > >> > To reproduce: >> > >> > - Load the package "Glorp" from http://www.squeaksource.com/SqueakDBX >> > - Open a MC Browser, select Glorp package and press the "Changes" button agains the ss repo. And you will see :) >> >> May be the image used to save the package got a problem and changed the timestamp of the methods. >> So when you merge you get changed methods. >> >> I've just tried commiting and load them in a clean image...same problem. >> >> And if it were what you say...is there a solution? >> >> thanks >> >> mariano >> >> >> > >> > Any help is really appreaciated. >> > >> > Thanks >> > >> > 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 > > > > -- > Javier PimÃ¡s > Ciudad de Buenos Aires > > _______________________________________________ > 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

2 1

[Pharo-project] [update 1.2] #12152
by Marcus Denker Sept. 28, 2010

Sept. 28, 2010

12152 ----- Issue 3000: StandardFileStream >> recategorization of browser plugin supporting methods Issue 2952: Shift-selection in new TextEditor Issue 2947: SmalltalkEditor doent handle ESC key Issue 2553: SystemVersion lost its state in 1.2 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

Re: [Pharo-project] Settings for Shout syntax highlighting
by Simon Denier Sept. 28, 2010

Sept. 28, 2010

On 28 sept. 2010, at 23:08, Mariano Martinez Peck wrote: > Simon, we could review/integrate this during the Sprint on Friday Unfortunately I will be on the road Friday. Anyway it's already integrated in the squeaksource repo. > > 2010/9/14 Simon Denier <Simon.Denier(a)inria.fr> > Following some hints from Alain, a new version (it just removes a method extension) > > Settings-Shout-simon_denier.2 > in PharoInbox > > > On 13 sept. 2010, at 11:00, Simon Denier wrote: > >> Hi >> >> A new package Settings-Shout in the Pharo Inbox for issue 1611 >> >> SLICE-Issue-1611-ShoutSettings-simon_denier.1 >> >> You can now set how (for example), instance variables, selector patterns, class references appears in the Shout pane. >> One point is that Shout comes with a list of hundred token types which can be individually customized, some of which I have no idea what they represent (externalCallTypePointerIndicator?). To keep things manageable, I defined some groups of logically related token types (like the gorup 'selector patterns' for token types patternKeyword, patternBinary, patternUnary). >> >> "Class SHGroupStyle manages settings for the Shout syntax highlighting. Token types are organized in logical groups which will share the same style. Currently, only color and emphasis can be edited through Shout settings. Text font and size are managed through the more general appearance setting. Changing a style setting on a SHGroupStyle automatically applies the style. >> >> Groups are defined in the class-side method initializeGroups. Alternatively, one can set its own style table using Shout tokens by calling #customStyleTable (see SHTextStylerST80 class>>defaultStyleTable for the format)." >> >> >> Help needed: >> 1) code review >> 2) review group definition, because I made some groups based partly on my intuition, partly on styling difference in the current difference: there may be a better partition of token types. >> 3) review description for group, setting organization... >> >> >> Thanks to Alain for helping with settings and especially polymorph widgets. >> >> -- >> Simon >> >> >> > > -- > Simon > > > > > _______________________________________________ > 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 -- Simon

1 0

[Pharo-project] Settings for Shout syntax highlighting
by Simon Denier Sept. 28, 2010

Sept. 28, 2010

Hi A new package Settings-Shout in the Pharo Inbox for issue 1611 SLICE-Issue-1611-ShoutSettings-simon_denier.1 You can now set how (for example), instance variables, selector patterns, class references appears in the Shout pane. One point is that Shout comes with a list of hundred token types which can be individually customized, some of which I have no idea what they represent (externalCallTypePointerIndicator?). To keep things manageable, I defined some groups of logically related token types (like the gorup 'selector patterns' for token types patternKeyword, patternBinary, patternUnary). "Class SHGroupStyle manages settings for the Shout syntax highlighting. Token types are organized in logical groups which will share the same style. Currently, only color and emphasis can be edited through Shout settings. Text font and size are managed through the more general appearance setting. Changing a style setting on a SHGroupStyle automatically applies the style. Groups are defined in the class-side method initializeGroups. Alternatively, one can set its own style table using Shout tokens by calling #customStyleTable (see SHTextStylerST80 class>>defaultStyleTable for the format)." Help needed: 1) code review 2) review group definition, because I made some groups based partly on my intuition, partly on styling difference in the current difference: there may be a better partition of token types. 3) review description for group, setting organization... Thanks to Alain for helping with settings and especially polymorph widgets. -- Simon

5 7

Re: [Pharo-project] pharo sprint at lille
by Marcus Denker Sept. 28, 2010

Sept. 28, 2010

On Sep 28, 2010, at 10:44 PM, Johan Brichau wrote: > Did you guys move? > No... even though it gets very crowded at the RMOD office (which is in the LIFL building of the university: http://www.lifl.fr/ ) We have to wait until the new INRIA building is constructed before moving. And that will take a while. At least there is now a sign at the construction site. That's a start. (the new building will be just accross the street of the current INRIA building) Marcus > On 28 Sep 2010, at 21:42, Marcus Denker wrote: > >> >> On Sep 28, 2010, at 9:31 PM, Mariano Martinez Peck wrote: >> >>> Does someone know how to go there? which metro station is better? google map ? >>> >> It's in the main INRIA building. >> >> http://www.inria.fr/lille/CRI-en/Howtogetthere >> >> This is just "behind" the university campus in a science/industry campus ("Parc Scientifique de la Haute Borne") >> >> Best station is "4 Cantons" (the last one). >> >> From the station, walk along the tracks of the metro (the one where the metro >> car goes empty) until the big street. The go to the left along the street. >> After the CNRS IRCICA building you will see the INRIA building. (see map). >> >>> what time does it start? >>> >> >> I guess someone will be there at 9:00... or even earlier if needed. >> >>> thanks >>> >>> mariano >>> >>> >>> 2010/9/28 stephane ducasse <stephane.ducasse(a)free.fr> >>> Hi guys >>> >>> I reserved a nice room for the sprint it is in the inria building. salle du conseil. >>> We will code like crazy :) >>> >>> Stef >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> _______________________________________________ >> 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 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] pharo sprint at lille
by Marcus Denker Sept. 28, 2010

Sept. 28, 2010

On Sep 28, 2010, at 9:31 PM, Mariano Martinez Peck wrote: > Does someone know how to go there? which metro station is better? google map ? > It's in the main INRIA building. http://www.inria.fr/lille/CRI-en/Howtogetthere This is just "behind" the university campus in a science/industry campus ("Parc Scientifique de la Haute Borne") Best station is "4 Cantons" (the last one). >From the station, walk along the tracks of the metro (the one where the metro car goes empty) until the big street. The go to the left along the street. After the CNRS IRCICA building you will see the INRIA building. (see map). > what time does it start? > I guess someone will be there at 9:00... or even earlier if needed. > thanks > > mariano > > > 2010/9/28 stephane ducasse <stephane.ducasse(a)free.fr> > Hi guys > > I reserved a nice room for the sprint it is in the inria building. salle du conseil. > We will code like crazy :) > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

Sept. 28, 2010

On Sep 28, 2010, at 4:39 PM, Johan Brichau wrote: > Perhaps the discussion I wanted to raise is not about the use of '==' but about the fact that equal string literals in the same method body are optimized to be the same object. > Without immutability, such optimization is just plain wrong. In addition, it does not even seem to be a particularly useful optimization. Yes this is true. :) We will fix it with Opal. Stef > > The use of '==' in the exercise is exactly about the reflective semantics, btw. > > Johan > > On 28 Sep 2010, at 10:05, Niko Schwarz wrote: > >> But that's the point, there should be no business semantics to '=='. >> Only reflective semantics. The reflective semantics are ok. >> >> Niko >> >> On Mon, Sep 27, 2010 at 11:51 AM, Johan Brichau <johan(a)inceptive.be> wrote: >>> >>> On 27 Sep 2010, at 11:28, Igor Stasenko wrote: >>> >>>> On 27 September 2010 11:54, Johan Brichau <johan(a)inceptive.be> wrote: >>>>> >>>>> On 27 Sep 2010, at 10:38, Lukas Renggli wrote: >>>>> >>>>>>> Am I wrong? >>>>>> >>>>>> Yes, almost always one should probably use #= instead of #==. >>>>> >>>>> I will add that to the exercise :-) >>>>> The exercise actually makes students aware of the difference between strings and symbols (which should be pointer-equal) >>>>> >>>> >>>> I think you can avoid using 'equal' word when describing a #== comparison. >>>> It can be explained as 'test whether comparands are same object or not' >>>> while #= is test whether two objects equal or not. >>> >>> Yes, this is exactly what the exercise is doing. >>> I want them to be aware that equal _symbols_ are the same objects, but that equal _strings_ are not, which is why I let them evaluate: >>> >>> a := #foobar. >>> b := #foobar. >>> a == b. >>> >>> a := 'foobar'. >>> b := 'foobar'. >>> a == b >>> >>> The problem is that evaluating the second snippet also yields true in Pharo/Squeak, so I cannot illustrate it using these snippets (which works fine in Visualworks, btw). >>> >>> Yes, this is a compiler optimization and, yes, people should use #= instead of #== normally. But imho the optimization yields a wrong semantics, which is why I posted the email. >>> >>> I have absolutely no clue if it can be changed (I am not familiar with the compiler implementation *at all*), but I would be happy to look over the shoulder of an experienced compiler hacker during the next sprint to learn ;-) >>> >>> cheers >>> Johan >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> >> -- >> http://scg.unibe.ch/staff/Schwarz >> twitter.com/nes1983 >> Tel: +41 076 235 8683 >> >> _______________________________________________ >> 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

1 0

[Pharo-project] ('a' == 'a') == true ?
by Johan Brichau Sept. 28, 2010

Sept. 28, 2010

I convinced the teacher who will be taking over my Smalltalk courses at UCLouvain (starting this week) to use Pharo :-) One of the introductory exercises in these courses shows the difference between '==' and '='. However, in Pharo (&Squeak) the following goes wrong imho: 'a' == 'a' -> true $a asString == $a asString -> false It seems that when you evaluate the expression, the (semantically identical) strings are represented as the same literal in the compiled block. For example, try to evaluate the following code by evaluating each statement in a separate doit. Then do it again as a single block... |a b| a := 'a'. b := 'a'. a == b inspect Do I make it an issue? Is there already an issue? (did not find one) Am I wrong? Johan

14 30

Re: [Pharo-project] [Pharo-Project] Issue 3010 and 3011. Debugger's Create button does not work when doing StepInto and StepOver
by StÃ©phane Ducasse Sept. 28, 2010

Sept. 28, 2010

Thanks! Stef On Sep 28, 2010, at 6:42 PM, Hernan Wilkinson wrote: > Hi, I opened two errors: > > 3010: Create button of debugger does not appear when doing step into and step over > 3011: Create button fails when the doesNotUnderstand: context is not selected > > I uploaded the fixes to PharoInbox with slice: SLICE-Issue-3010-CreateButtonWorksWithStepIntoAndStepOver-HernanWilkinson.2 > > Bye, > Hernan > > -- > HernÃ¡n Wilkinson > Agile Software Development, Teaching & Coaching > Mobile: +54 - 911 - 4470 - 7207 > email: hernan.wilkinson(a)10Pines.com > site: http://www.10Pines.com > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0