- Pharo-dev - lists.pharo.org

dual screen - was Re: vm fixes

by btc＠openinworld.com

May 16, 2013

Re: [Pharo-dev] Monkey Validation

by btc＠openinworld.com

ClÃ©ment Bera wrote: > Camillo we should really spend some time updating the plots in the jenkins > job : https://ci.inria.fr/pharo/job/Pharo-3.0-CodeCritics-Beta/ . > > What is "JSHint Trend" on the graph heading? Are you advertising something to do with Javascript? :) (Sorry, its just the first thing that popped into my head looking at it.)

May 16, 2013

Re: [Pharo-dev] Making ASTInterpreter work with opal bindings

by Marcus Denker

On May 15, 2013, at 4:42 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On May 15, 2013, at 3:41 PM, ClÃ©ment Bera <clement.bera(a)inria.fr> wrote: > >> Sorry with the strike and no metro I cannot be at INRIA today. I'm at Marcus right now we will have a look at your slice now :) >> > > So we lookedâ¦ and there is a problem with No! We found it! The code showing the error (in the testEnsureTricky) it this: (String streamContents: [:s | [ [s nextPutAll: 1 printString. 1/0] ensure: [s nextPutAll: 2 printString] ] on: Error do: [s nextPutAll: 3 printString] ]) asInteger The problem is that the scope of the second "s" is wrong, it should the block with the [:s |, but it is just the block one outer. And the reason is this: The ASTClosureAnalyzer, the visitor that analyses if a variable is to be put in a tempVector or is a copied var, does this: visitVariableNode: aVariableNode "re-lookup the temorary variables..." | var | aVariableNode isTemp ifFalse: [^self]. var := scope lookupVar: aVariableNode name. aVariableNode ocBinding: var. var isTempVectorTemp ifTrue: [scope addCopyingTempToAllScopesUpToDefVector: var vectorName]. var isCopying ifTrue: [scope addCopyingTempToAllScopesUpToDefTemp: var]. If it seems a copying temp, it puts copied vars in all scopes until it finds the definition: addCopyingTempToAllScopesUpToDefTemp: aVar (self hasCopyingTempNamed: aVar name) ifFalse: [self addCopyingTemp: aVar]. tempVars at: aVar name ifPresent: [:v | ^ self]. ^ self outerScope addCopyingTempToAllScopesUpToDefTemp: aVar. Now for the second "s", the visit will call var := scope lookupVar: aVariableNode name. again, but this lookup will find the *copy* in the outer scope and returns this.. so this is clearly wrong. (but for Opal this is not a problem, as it just compiles a local access to the copying temp and does not care that it has a copy...). Now how to fix it... Marcus

May 16, 2013

[update 3.0] #30137

by Marcus Denker

30137 ----- 10547 Do not run CommandLineHandlers on the existing stack https://pharo.fogbugz.com/f/cases/10547 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Support-MarcusDenker.8… http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-CommandLine-MarcusDenk… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-MarcusDenker.1453.diff

May 16, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=wi… 2 regressions found. CollectionsTests.Strings.ByteSymbolTest.testReadFromString CollectionsTests.Strings.SymbolTest.testReadFrom

May 16, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=ma… 2 regressions found. CollectionsTests.Strings.ByteSymbolTest.testReadFromString CollectionsTests.Strings.SymbolTest.testReadFrom

May 16, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=li… 2 regressions found. CollectionsTests.Strings.ByteSymbolTest.testReadFromString CollectionsTests.Strings.SymbolTest.testReadFrom

May 16, 2013

[update 3.0] #30136

by Marcus Denker

May 16, 2013

Re: [Pharo-dev] Making ASTInterpreter work with opal bindings

by ClÃ©ment Bera

We are movin AST-interpreter project from dh83 to mate team so you can write on it Guille. 2013/5/16 Marcus Denker <marcus.denker(a)inria.fr> > > On May 14, 2013, at 2:09 PM, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > > Right now, in the image there exist two ways to annotate an AST: > > - the Opal way > > - the RB Way > > > > We should simplify that by having only one. So far, the only user of the > RB bindings is the ASTInterpreter + the RB tests. > > > > So, I prepared a slice and issue [1], with the following details > > > > - annotate ast using opal annotator > > - extended OCBindings to read and write from an AST interpreter > > - not yet made a difference between arg nodes with a different class > (just put an if) > > I think it might be a good idea to add thatâ¦ what I will do first is to > cleanup the OCTemp vars a bit > (there is an index variable that is used to sort them at the end, a > leftover from back before the closures > when there was simple temp=index mapping). > > > - i didnt add inst vars into the opal bindings for the binding->node > relation as in RB, I send the node as a parameter > > We need to check this, back pointers are always interesting (but I am not > sure if we have a new semantic variable or > if we reuse it for multiple nodes?) > > > - I had to adapt the #compile: into ASTInterpreter because > > - opal does not annotate other than method nodes > Yes, this is because when compiling an expression we transform it do the > doIt method before. > Expressions can not be compiled standalone. > > > - undeclared variables raised warnings, not errors > > > Yes, the idea is that in interactive mode it does user=interaction, while > in non-interactive it compiled an Undeclared. (so that the code stays > loadable). > > Maybe the interpreter could do the same an fall back to Undeclared, that > it, undeclared > vars are just treated as nil. > > Marcus > -- ClÃ©ment BÃ©ra Mate Virtual Machine Engineer BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq*

May 16, 2013

Re: [Pharo-dev] TxTextLayout

by Camillo Bruni

On 2013-05-16, at 13:04, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hello. > > 2013/5/16 Camillo Bruni <camillobruni(a)gmail.com> > >> I have a question concerning the new TxText layout. >> How hard is it support inline non-text nodes (aka inline morphs) in a text >> layout? >> > > Do you mean supporting "TxMorphSpan" objects from text model at text layout > level? > I think it is is not hard. Main issue here is supporting such kind of spans > at text model level. But I think it is not difficult too, > I should look at code to answer in detail (can't do it now). > > >> >> My dream is still to be able to drag and drop an "instance" from an >> inspector to a workspace and do some operations on it using standard >> smalltalk. > > > +1 > And I want drag and drop objects between inspectors and between workspaces. > > >> The only difference here would be instead of using a variable or >> expression to get an instance of something I would have a textual/visual >> node directly representing an instance! >> > > I'm not understand it. > By dropping some object to workspace It can create named variable and then > you can use it for scripting inside workspace. > But what you suggest here? Can you explan deeply? Indeed I am not very clear (as usual :). a) I want to have a morph representing an object b) I want to embed these morphs into text c) I want to interact with these morphs and the text Let's say [Set] is the morph representing a set and I have the following source code with this morph inside: [Set] includes: #a Then this would be equivalent to the following: Smalltalk at: #MySetInstance put Set new. MySetInstance includes: #a However [Set] is not just text but a real morph I can drag around, right click and get a decent, instance specific menu on... and so forth :) is that more clear?

May 16, 2013