- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Installing trait blow the method def in hierarchy

by Yuriy Tymchuk

> On 13 May 2015, at 09:25, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > 2015-05-12 12:06 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: > Hi, > > Iâve noticed that if you install a trait on a class and a trait defines explicit requirement method, and this method is defined in a super class, it is being looked up during execution through #explicitRequirement method. It was slowing down my execution by almost 20%. Is there a special way to use a Trait to avoid that, or itâs work-in-progress solution? > > I find this behavior questionable, when did this change? ( I thought self explicitRequirement always signals an error and does not try to find the method in the superclass chain). > Anyway, if you want to use the super class method, you can just remove the method from the trait usage. > > ASuperClass subclass: #MySubclass > uses: ATrait - {#theMethodDefinedInSuperclassAndTrait } > instanceVariableNames: '' > classVariableNames: '' > category: â' Good to know, thanks. I donât know the philosophy behind this case, but from my point of view - trait requires a method, and the class has it, itâs just that the method is defined higher in the hierarchy. Uko > > > regards > Nicolai > > > Uko >

May 13, 2015

Re: [Pharo-dev] Code generation for ASTs with syntax errors

by Damien Pollet

On 13 May 2015 at 08:35, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Only three methods are needed to allow generating executable methods from > such an AST: the SyntaxErrorNotification > is raised at runtime instead of compile time. > I can hear the noise of eyebrows raising in the compiler community :) Syntax errors shouldn't require immediate fixing during compilation per se, but there should be a way to deal with them "at compile time" âwhatever that means for us. For instance, faulty methods could have a flashy icon in the browser; I think I'd even color the whole package-class-protocol-selector in red if either of them contain faulty methods. -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

May 13, 2015

Re: [Pharo-dev] Installing trait blow the method def in hierarchy

by Nicolai Hess

2015-05-12 12:06 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Hi, > > Iâve noticed that if you install a trait on a class and a trait defines > explicit requirement method, and this method is defined in a super class, > it is being looked up during execution through #explicitRequirement method. > It was slowing down my execution by almost 20%. Is there a special way to > use a Trait to avoid that, or itâs work-in-progress solution? > I find this behavior questionable, when did this change? ( I thought self explicitRequirement always signals an error and does not try to find the method in the superclass chain). Anyway, if you want to use the super class method, you can just remove the method from the trait usage. ASuperClass subclass: #MySubclass uses: ATrait - {#theMethodDefinedInSuperclassAndTrait } instanceVariableNames: '' classVariableNames: '' category: '' regards Nicolai > > Uko >

May 13, 2015

Code generation for ASTs with syntax errors

by Marcus Denker

We can parse code with syntax errors: it generates partial ASTs with the faulty part of the input as a RBParseErrorNode. Only three methods are needed to allow generating executable methods from such an AST: the SyntaxErrorNotification is raised at runtime instead of compile time. testEvalSimpleMethodWithError | ast cm | ast := OpalCompiler new source: 'method 3+'; useFaultyForParsing: true; parse. self assert: ast isMethod. self assert: ast isFaulty. cm := ast compiledMethod. self should: [cm valueWithReceiver: nil arguments: #()] raise: SyntaxErrorNotification The syntax error instance is compiled in via a literal variable, in the end the only thing needed was: visitParseErrorNode: anErrorNode methodBuilder pushLiteralVariable: #error -> anErrorNode asSyntaxErrorNotification; send: #signal. This is in #50044. Future work: introduce a RuntimeSyntaxError that can be turned off per error and globally. Marcus

May 13, 2015

Re: [Pharo-dev] Transcript needs your love

by Alain Rastoul

Le 12/05/2015 19:02, Alain Rastoul a Ã©crit : > Le 08/05/2015 11:34, stepharo a Ã©crit : >> Hi guys >> >> the Transcript in Pharo is that it's not asynchronous so I can't use it >> in VM development to show the current progress of the simulation. For >> example: >> 1 to: 100 do: [ :i | >> 0.1 seconds asDelay wait. >> Transcript show: 'x'. ] >> => on Squeak, this shows a x every 0.1 second in the Transcript >> => on Pharo, nothing happens during 10 seconds then all the x are shown. >> >> https://pharo.fogbugz.com/default.asp?15515 >> >> > Hi, > I updated the fogbugz entry with a changeset containing the sources Stef > already put here, so that it should be easy for anybody to load > CuisTranscript into a Pharo image and have a look. > > IMHO another solution has to be found, or a big review of this has to be > done. > see details in fogbugz entry. > A very ugly but simple workaround could be ThreadSafeTranscript>>endEntry: accessSemaphore critical: [ deferredEndEntry := true . " is Synchronous coudl be a setting" self isSynchronous ifTrue: [ self stepGlobal . "handles appendEntry" World displayWorldSafely "redraw now" ] ]. with a setings for isSynchronous ugly but works, -- Regards, Alain

May 12, 2015

Re: [Pharo-dev] Trying to use Rubric in Nautilus ....

by stepharo

For fun I put the following trace in sourceCodeFrom: aTextMorph Transcript show: '.'. ^ self sourceCode And in general this method is invoked three times instead of one :) > > Before asking we read all the examples and I saw that selector: is > used to communicate and update the code pane. > > (UIManager default newAutoAcceptTextEntryFor: self > get: #selector > set: #selector: > class: String > getEnabled: #haveClassName > help: 'Enter a selector' translated > entryCompletion: entryCompletion) > acceptOnCR: false; > ghostText: 'Selector'; > withDropListButton; > > > I think this is only for the drop down list. What I meant is that I could use set: and pass the selector to be invoked by the dropdown when the drop down is selected. And it will notify self with the selector: selector. So we could sepcify any selector (ie I can register to the drop box and say call me once you are set). > In RubMethodEditingExample>>#selector: > it calls the update explicit > self updateCodeWith: (cls sourceCodeAt: selector) > and updateCodeWith: sets the text on the text model. > > > > Now my problem (and may be there is not solution) is how can I > connect from a pluggableListMorph to a RubScrollText > when the list does not generate announcement. > This is why I tried to pass via dependents or something like that. > > I will try to generate announcements but this is a lot more work > and I do not know if it will work. > > Stef > >

May 12, 2015

Re: [Pharo-dev] Trying to use Rubric in Nautilus ....

by Nicolai Hess

2015-05-12 21:44 GMT+02:00 stepharo <stepharo(a)free.fr>: > Thanks alain > > > Before asking we read all the examples and I saw that selector: is used to > communicate and update the code pane. > > (UIManager default newAutoAcceptTextEntryFor: self > get: #selector > set: #selector: > class: String > getEnabled: #haveClassName > help: 'Enter a selector' translated > entryCompletion: entryCompletion) > acceptOnCR: false; > ghostText: 'Selector'; > withDropListButton; > > I think this is only for the drop down list. In RubMethodEditingExample>>#selector: it calls the update explicit self updateCodeWith: (cls sourceCodeAt: selector) and updateCodeWith: sets the text on the text model. > Now my problem (and may be there is not solution) is how can I connect > from a pluggableListMorph to a RubScrollText > when the list does not generate announcement. > This is why I tried to pass via dependents or something like that. > > I will try to generate announcements but this is a lot more work and I do > not know if it will work. > > Stef > >

May 12, 2015

Re : Re: [Pharo-dev] Trying to use Rubric in Nautilus ....

by Alain Plantec

Ok i see. It is possible to code an adapter with the pluggabletexmorph protocol. I will try to do it tomorrow.Â Cheers Alain De:"stepharo" <stepharo(a)free.fr> Date:mar j mai PM Ã 21:44 Objet:Re: [Pharo-dev] Trying to use Rubric in Nautilus .... Thanks alain Before asking we read all the examples and I saw that selector: is used to communicate and update the code pane. (UIManager default newAutoAcceptTextEntryFor: self Â Â Â Â Â Â get: #selector Â Â Â Â Â Â set: #selector: Â Â Â Â Â Â class: String Â Â Â Â Â Â getEnabled: #haveClassName Â Â Â Â Â Â help: 'Enter a selector' translated Â Â Â Â Â Â entryCompletion: entryCompletion) Â Â Â Â Â Â Â Â acceptOnCR: false; Â Â Â Â Â Â Â Â ghostText: 'Selector'; Â Â Â Â Â Â Â Â withDropListButton; Now my problem (and may be there is not solution) is how can I connect from a pluggableListMorph to a RubScrollText when the list does not generate announcement. This is why I tried to pass via dependents or something like that. I will try to generate announcements but this is a lot more work and I do not know if it will work. Stef

May 12, 2015

Re: [Pharo-dev] Trying to use Rubric in Nautilus ....

by Nicolai Hess

2015-05-12 21:40 GMT+02:00 stepharo <stepharo(a)free.fr>: > But nicolai I know announcement. Now the widgets of Nautilus do not use > announcement so I do not know if I > can simply replace self changed: #sourceCodeFrom: > I do not know the implication of removing sourceCodeFrom: > OK, I just thought rubric uses announcement in place of self changed: So, and now? Replace all self changed... with self sourceCodeArea setText ? > > Le 12/5/15 17:41, Nicolai Hess a Ã©crit : > > Announcements! > > replace > self changed: #sourceCodeFrom:. > with something like > self announcer announce:RubTextSetInModel. > > ( I am not sure what RubXXAnouncement to use) > > > > > > 2015-05-12 17:14 GMT+02:00 stepharo <stepharo(a)free.fr>: > >> We tried all kind of combinations.... >> >> >> modelEditor := (RubSmalltalkMethodEditorModel new client: self). >> widget := modelEditor newScrolledText. >> >> >> widget >> on: self >> text: #sourceCodeFrom: >> accept: #compileSource:notifying: >> readSelection: #contentsSelectionFrom: >> menu: #sourceCodeMenu:shifted:. >> >> self addDependent: modelEditor. >> self when: #sourceCodeFrom: send: #setText: to: modelEditor. >> >> widget >> beWrapped; >> beForSmalltalkCode; >> withLineNumbers; >> setText: self sourceCode; >> setTextSelector: #halt. >> ^ widget >> >> >> But we cannot get the editor or the widget to be invoked when the list >> changes. >> So we spent three hours on it so we should stop. We are missing just this >> bit. >> >> Stef >> >> > >

May 12, 2015

Re: [Pharo-dev] Trying to use Rubric in Nautilus ....

by stepharo

Thanks alain Before asking we read all the examples and I saw that selector: is used to communicate and update the code pane. (UIManager default newAutoAcceptTextEntryFor: self get: #selector set: #selector: class: String getEnabled: #haveClassName help: 'Enter a selector' translated entryCompletion: entryCompletion) acceptOnCR: false; ghostText: 'Selector'; withDropListButton; Now my problem (and may be there is not solution) is how can I connect from a pluggableListMorph to a RubScrollText when the list does not generate announcement. This is why I tried to pass via dependents or something like that. I will try to generate announcements but this is a lot more work and I do not know if it will work. Stef

May 12, 2015