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

Re: [Pharo-dev] Compiling a method with a new iv raises DNU

by Yuriy Tymchuk

Hi Stef. Can you tell me in which class do you add this? Because it does not happen for every class. There was an issue that one on the rules destroying ASTs, but we solved it about a month ago. Uko > On 04 Sep 2015, at 10:45, stepharo <stepharo(a)free.fr> wrote: > > Apparently there is something wrong in the ASTCache. > The only solution I found to continue to work was to remove the QAPlugin. > > > Le 4/9/15 10:21, stepharo a Ã©crit : >> Here is the scenario >> >> I added the method >> >> comment >> >> ^ comment >> >> and I get now a DNU >> >> doSemanticAnalysisIn: >> >> >> at: aCompiledMethod >> ^ self >> at: aCompiledMethod >> ifAbsentPut: [ >> aCompiledMethod parseTree doSemanticAnalysisIn: aCompiledMethod methodClass ] >> >> >> where aCompiledMethod is StoreBlessing>>#comment >> >> but the parseTree is nil :( >> >> How this behavior can happen? >> >> Stef >> >> > >

Sept. 4, 2015

Re: [Pharo-dev] Compiling a method with a new iv raises DNU

by stepharo

Apparently there is something wrong in the ASTCache. The only solution I found to continue to work was to remove the QAPlugin. Le 4/9/15 10:21, stepharo a Ã©crit : > Here is the scenario > > I added the method > > comment > > ^ comment > > and I get now a DNU > > doSemanticAnalysisIn: > > > at: aCompiledMethod > ^ self > at: aCompiledMethod > ifAbsentPut: [ > aCompiledMethod parseTree doSemanticAnalysisIn: > aCompiledMethod methodClass ] > > > where aCompiledMethod is StoreBlessing>>#comment > > but the parseTree is nil :( > > How this behavior can happen? > > Stef > >

Sept. 4, 2015

Re: [Pharo-dev] [Pharo5] Improvements for Anonymous classes

by stepharo

in my 99 JOOP paper :) Le 21/8/15 08:34, Yuriy Tymchuk a Ã©crit : > Hi, where can I read more about anonymous classes. They look like amazing stuff to be used in tests. > > Uko > > >> On 21 Aug 2015, at 08:38, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> Hi, >> >> Besides cleaning for the bootstrap, another thing we did yesterday was improving handling of >> Anonymous classes. >> >> 1) you can now browse methods of anonymous classes with nautilus *if* they inherit from Object (the main case) >> >> myClass := Object newAnonymousSubclass. myClass compile: 'test ^5'. myClass browse >> >> 2) #classInstaller for anonymous classes now returns an AnonymousClassInstaller >> >> 3) class builder name checking was fixed to not raise an error for the ânamesâ used for Anonymous classes >> >> ==> you can use #addSlot: on anonymous classes. >> >> >> To improve: >> >> - browser should show some kind of class definition so one can see the superclass >> - it would be nice to be able to browse "Behavior newâ, but in most cases people use >> anon subclasses of existing classes, so not that important. >> >> Marcus > >

Sept. 4, 2015

Re: [Pharo-dev] Announcements in Nautilus

by stepharo

I will not reply publicly on the true reason of that situation :) Now what we should do is to continue to simplify the code of Nautilus (we made great steps with Franck). And yuriy if you have some fixes please let us know. Stef Le 4/9/15 09:22, Yuriy Tymchuk a Ã©crit : > Hi, > > I find announcements in Nautilus a bit strange. I guess you are familiar with QualityAssistant. To display the critics about the currently selected entity I need to know which one is selected. There is NautilusMethodSelected and NautilusClassSelected announcements. But here is a small detail, if you select a method, both of them are fired i.e. for the methodâs class and the method itself. For me it does not make any sense because I need to show critics only for currently selected source code. > > Moreover if I need to show something about the class while a method is selected, I can just ask the method for its class, right? > > Does anybody need this double announcing? (Maybe it is quadruple, I havenât checked for a package and protocol) > > Cheers! > Uko >

Sept. 4, 2015

Compiling a method with a new iv raises DNU

by stepharo

Here is the scenario I added the method comment ^ comment and I get now a DNU doSemanticAnalysisIn: at: aCompiledMethod ^ self at: aCompiledMethod ifAbsentPut: [ aCompiledMethod parseTree doSemanticAnalysisIn: aCompiledMethod methodClass ] where aCompiledMethod is StoreBlessing>>#comment but the parseTree is nil :( How this behavior can happen? Stef

Sept. 4, 2015

Re: [Pharo-dev] Announcements in Nautilus

by Nicolai Hess

Another related issue: 12535 <https://pharo.fogbugz.com/f/cases/12535/To-many-updates-on-the-methods-list> To many updates on the methods list (changes aren't applicable anymore, because to many things had changed). Sometimes I am working on this and try to solve this. But I failed so far. The way Nautilus holds the current selection (model and UI) and how it propagate changes (selectX, selectXwithoutChangingSelection, select silenty ...) doesn't really work good ( or I just don't understand it). (And with rubric as TextModel, this is getting even more complicated). 2015-09-04 9:34 GMT+02:00 Christophe Demarey <Christophe.Demarey(a)inria.fr>: > > Le 4 sept. 2015 Ã 09:22, Yuriy Tymchuk a Ã©crit : > > > Hi, > > > > I find announcements in Nautilus a bit strange. I guess you are familiar > with QualityAssistant. To display the critics about the currently selected > entity I need to know which one is selected. There is > NautilusMethodSelected and NautilusClassSelected announcements. But here is > a small detail, if you select a method, both of them are fired i.e. for the > methodâs class and the method itself. > > > Does anybody need this double announcing? (Maybe it is quadruple, I > havenât checked for a package and protocol) > > > And the best is that the UI is refreshed for each announcement. Then you > understand why Nautilus is slow. > Franck did some improvements but Nautilus still refresh itself far too > much (there was 12 refresh calls for the source code panel ...). > > It looks like a design flaw: there should be only one announcement for a > selection change. You could define PackageSelectionChanged, > ClassSelectionChanged, ProtocolSelectionChanged, MethodSelectionChanged, > each one with more or less info (I mean method will have the protocol, > class, and package).

Sept. 4, 2015

Re: [Pharo-dev] Need a decision on subString: vs substring:

by Thierry Goubier

2015-09-04 9:39 GMT+02:00 Christophe Demarey <Christophe.Demarey(a)inria.fr>: > I don't like so much compatibility packages because people will not update > their code and expect the compatibility package to always work. > Why not just use what Marcus did for deprecations? Create a rule to > transform ANSI Smalltalk to Pharo "magicly'? > An extension package with a set of rewrite rules that we can use to: - port code for old Pharo versions to new Pharo versions (in some areas of Pharo, many things disappear/are renamed without deprecation between versions) - port non-Pharo code to Pharo. It would be really great if those rules could be applied when loading the package via MC or FileIn, not when the package is already loaded, otherwise you need both a compatibility layer, and the rewriting rules. Probably a lot easier to do by, say, replacing the MC code model by the RB code model. Or, when loading a package, loading it through a MC defintion, convert it to RB model, apply rules, convert to Ring, compile Ring... I like simple things :) Thierry > > Le 3 sept. 2015 Ã 22:44, Gabriel Cotelli a Ã©crit : > > I've second Sven here. In case anybody wants the old method put it in some > ANSICompatibility package to ease porting packages from ANSI-compliant > Smalltalks. > > On Thu, Sep 3, 2015 at 4:54 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > >> We went through a lot of effort/pain to move to substring, I think for >> good reasons. >> >> > On 03 Sep 2015, at 21:31, Dimitris Chloupis <kilon.alios(a)gmail.com> >> wrote: >> > >> > why not both ? >> >> Because the proper English spelling is with lowercase >> >> https://duckduckgo.com/?q=define%3A+substring&ia=definition >> >> > On Thu, Sep 3, 2015 at 9:45 PM stepharo <stepharo(a)free.fr> wrote: >> > *) It appears that Pharo is removing subString: in favor of >> > substring:. The ANSI standard defines subString:. >> > >> > I was not aware of it. In fact ANSI is bad and totally incomplete >> > (for example we studies strings and this is a mess and totally >> > incomplete). >> > Now we should probably add it. I will send the mail to the >> > mailing-list and let people decide. >> > >> > >> > >> > >> >> >> > >

Sept. 4, 2015

Re: [Pharo-dev] Need a decision on subString: vs substring:

by Christophe Demarey

I don't like so much compatibility packages because people will not update their code and expect the compatibility package to always work. Why not just use what Marcus did for deprecations? Create a rule to transform ANSI Smalltalk to Pharo "magicly'? Le 3 sept. 2015 Ã 22:44, Gabriel Cotelli a Ã©crit : > I've second Sven here. In case anybody wants the old method put it in some ANSICompatibility package to ease porting packages from ANSI-compliant Smalltalks. > > On Thu, Sep 3, 2015 at 4:54 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > We went through a lot of effort/pain to move to substring, I think for good reasons. > > > On 03 Sep 2015, at 21:31, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > > > why not both ? > > Because the proper English spelling is with lowercase > > https://duckduckgo.com/?q=define%3A+substring&ia=definition > > > On Thu, Sep 3, 2015 at 9:45 PM stepharo <stepharo(a)free.fr> wrote: > > *) It appears that Pharo is removing subString: in favor of > > substring:. The ANSI standard defines subString:. > > > > I was not aware of it. In fact ANSI is bad and totally incomplete > > (for example we studies strings and this is a mess and totally > > incomplete). > > Now we should probably add it. I will send the mail to the > > mailing-list and let people decide. > > > > > > > > > > >

Sept. 4, 2015

Re: [Pharo-dev] Announcements in Nautilus

by Christophe Demarey

Le 4 sept. 2015 Ã 09:22, Yuriy Tymchuk a Ã©crit : > Hi, > > I find announcements in Nautilus a bit strange. I guess you are familiar with QualityAssistant. To display the critics about the currently selected entity I need to know which one is selected. There is NautilusMethodSelected and NautilusClassSelected announcements. But here is a small detail, if you select a method, both of them are fired i.e. for the methodâs class and the method itself. > Does anybody need this double announcing? (Maybe it is quadruple, I havenât checked for a package and protocol) And the best is that the UI is refreshed for each announcement. Then you understand why Nautilus is slow. Franck did some improvements but Nautilus still refresh itself far too much (there was 12 refresh calls for the source code panel ...). It looks like a design flaw: there should be only one announcement for a selection change. You could define PackageSelectionChanged, ClassSelectionChanged, ProtocolSelectionChanged, MethodSelectionChanged, each one with more or less info (I mean method will have the protocol, class, and package).

Sept. 4, 2015

Announcements in Nautilus

by Yuriy Tymchuk

Hi, I find announcements in Nautilus a bit strange. I guess you are familiar with QualityAssistant. To display the critics about the currently selected entity I need to know which one is selected. There is NautilusMethodSelected and NautilusClassSelected announcements. But here is a small detail, if you select a method, both of them are fired i.e. for the methodâs class and the method itself. For me it does not make any sense because I need to show critics only for currently selected source code. Moreover if I need to show something about the class while a method is selected, I can just ask the method for its class, right? Does anybody need this double announcing? (Maybe it is quadruple, I havenât checked for a package and protocol) Cheers! Uko

Sept. 4, 2015