October 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Mysteries of the compiler

by Marcus Denker

> > > 1. sometimes the debugger can not inspect a single tempvar (list of all > temps is working) > 2. number of temp vars (in method header) is wrong: > > | a b c | > a := 1. > b := 2. > c := 3. > [[a asString] > on: Error > do: [:ex | a > value: a > value: b > value: c]. > c < 0] whileTrue. > > method header numtemps 1 > > | a b c | > a := 1. > b := 2. > c := 3. > c < 0 > ifTrue: [ > [ a asString ] > on: Error > do: [ :ex | a value: a value: b value: c ]. > c < 0 ]. > ^ a > > method header numtemps 3 > > both methods define a block with a nested block. > In the first method it is the receiver of #whileTrue: > the second method it is the argument to #ifTrue: > I think both blocks are optimized, but somehow the > block receiving the whileTrue: message makes the computation > for the number of tempvars wronng > What is happening is that the variables are wrongly put in a temp vector... in the case of loops. the one temp is this vector. this should be fixed.

Oct. 16, 2014

Re: [Pharo-dev] [Pharo4] Inspector View for Opal Scopes

by Tudor Girba

Keep the goodies coming :) Doru On Thu, Oct 16, 2014 at 4:04 PM, Clara Allende <clari.allende(a)gmail.com> wrote: > I love it :) Thanks ^^ > > 2014-10-16 15:39 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: > >> Hi, >> >> There is now a special view for semantic scopes in Opal: >> >> >> >> And these tools work outside of the Inspector, too: >> e.g. >> >> GTBytecodeBrowser openOn: (OrderedCollection>>#do:) >> >> >> > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 16, 2014

Re: [Pharo-dev] Tests around Pharo

by Ben Coman

mschepens wrote: > I finally managed the proxy problem by sending commits from my own web > connection. > So I put the issues to "Fix review needed". I had some problems while > importing Collections-Tests (Native part, for the FloatArrayTest) but > finally managed it too. > > I sent to Damien Cassou the "license agreements" filled and signed, I will > give him my copy of this paper next wednesday. > > Hope our tests will be helpful and will increase test coverage of pharo, Yes. They certainly will. Its the accumulation of small improvements that make a system great. > it was really interesting for us to work on this project, and we acquired > significant knowledges (about smalltalk but about opensource projects too). It rubs both ways. I had never noticed PharoUser before, and I learnt something new from reviewing your contribution. Opensource is as much learning from other people's code, as it is building a pool of good software. > We'll follow our commits evolution, The CI monkey spotted a few quality assurance items. I lead you through fixing them for issue 14222. Could you have a go at that for your three issues? > and again thanks to all of you for the time you gave us ! You are welcome. It can be a bit daunting breaking in, but like everything, the more you do, the easier it gets. Hope to see you back again when you use Pharo to implement your next idea to take over the world! :) cheers -ben > > > > -- > View this message in context: http://forum.world.st/Tests-around-Pharo-tp4777295p4784793.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

Oct. 16, 2014

Re: [Pharo-dev] [Pharo4] Inspector View for Opal Scopes

by Clara Allende

I love it :) Thanks ^^ 2014-10-16 15:39 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: > Hi, > > There is now a special view for semantic scopes in Opal: > > > > And these tools work outside of the Inspector, too: > e.g. > > GTBytecodeBrowser openOn: (OrderedCollection>>#do:) > > >

Oct. 16, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40309 Home: https://github.com/pharo-project/pharo-core

Oct. 16, 2014

[pharo-project/pharo-core] 4a8185: 40309

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 4a818514f3a4d113aea4fd664577e71dcd21bc3d https://github.com/pharo-project/pharo-core/commit/4a818514f3a4d113aea4fd66… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-16 (Thu, 16 Oct 2014) Changed paths: M Nautilus.package/AbstractNautilusUI.class/class/menu/classesMenu_.st A Nautilus.package/AbstractNautilusUI.class/instance/menus behavior/inspectMethod.st A Nautilus.package/AbstractNautilusUI.class/instance/menus behavior/inspectMethods.st M Nautilus.package/MethodWidget.class/class/menu/elementsMenu_.st M OpalCompiler-Core.package/OCAbstractScope.class/definition.st A OpalCompiler-Core.package/OCAbstractScope.class/instance/accessing/children.st A OpalCompiler-Core.package/OCAbstractScope.class/instance/initializing/addChild_.st M OpalCompiler-Core.package/OCAbstractScope.class/instance/initializing/outerScope_.st M OpalTools.package/GTBytecodeBrowser.class/README.md M OpalTools.package/GTBytecodeBrowser.class/instance/building/sourceIn_.st A OpalTools.package/GTOpalScopeBrowser.class/README.md A OpalTools.package/GTOpalScopeBrowser.class/definition.st A OpalTools.package/GTOpalScopeBrowser.class/instance/building/compose.st A OpalTools.package/GTOpalScopeBrowser.class/instance/building/sourceIn_.st A OpalTools.package/GTOpalScopeBrowser.class/instance/building/treeIn_.st A OpalTools.package/extension/OCAbstractScope/instance/gtInspectorSourceCodeIn_.st A OpalTools.package/extension/OCAbstractScope/instance/sourceInterval.st A OpalTools.package/extension/RBProgramNode/instance/gtInspectorSymbolicBytecodeIn_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script309.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40309.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Traits.package/TClassDescription.class/instance/compiling/compile_classified_withStamp_notifying_logSource_.st Log Message: ----------- 40309 14251 Add a scope browser: shows tree of scopes, corresponding source https://pharo.fogbugz.com/f/cases/14251 14243 tiny refactoring in #compile:classified:withStamp:notifying:logSource: https://pharo.fogbugz.com/f/cases/14243 14231 add "inspect method" to method menu in browser and everywhere https://pharo.fogbugz.com/f/cases/14231 http://files.pharo.org/image/40/40309.zip

Oct. 16, 2014

[Pharo4] Inspector View for Opal Scopes

by Marcus Denker

Hi, There is now a special view for semantic scopes in Opal: And these tools work outside of the Inspector, too: e.g. GTBytecodeBrowser openOn: (OrderedCollection>>#do:)

Oct. 16, 2014

Re: [Pharo-dev] OrderedDictionary and new tools, Seaside...

by Marcus Denker

> On 16 Oct 2014, at 14:55, phil(a)highoctane.be wrote: > > I am using OrderedDictionary in quite a few places. > > Now, I have to steam a lot of extra methods from Dictionary as the GTInspector doesn't display things properly, nor the WAInspector and its subclasses out of the box. > NeoJSON same story, as Ston etc. > > OrderPreservingDictionary is quite useful. > Yes, there is GRSmallDictionary but it also has the same issues. > > OrderPreservingDictionary is at least a Collection where GRSmallDictionary is a GRObject. > > What would be the best strategy here? > > We need such an ordered map all the time, it deserves a bit better. > > Opinions? > In Pharo4, I copied OrderPreservingDictionary to OrderedDictionary. (to have a default one in the image without disturbing clients of OrderPreservingDictionary) This should be improved if it something is missing. Marcus

Oct. 16, 2014

OrderedDictionary and new tools, Seaside...

by phil＠highoctane.be

I am using OrderedDictionary in quite a few places. Now, I have to steam a lot of extra methods from Dictionary as the GTInspector doesn't display things properly, nor the WAInspector and its subclasses out of the box. NeoJSON same story, as Ston etc. OrderPreservingDictionary is quite useful. Yes, there is GRSmallDictionary but it also has the same issues. OrderPreservingDictionary is at least a Collection where GRSmallDictionary is a GRObject. What would be the best strategy here? We need such an ordered map all the time, it deserves a bit better. Opinions? Phil

Oct. 16, 2014

Re: [Pharo-dev] compiled method inspector

by Marcus Denker

> On 16 Oct 2014, at 12:13, Nicolai Hess <nicolaihess(a)web.de> wrote: > > The new inspector extensions for compiled methods are GREAT. > :-) More to come. I have one for IR->Text and one for Opal Compiler Scopes. > I noticed some of them are in package GT-Inspector-Extensions-Core > and some are in OpalTools. > Yes, the reason is that GTTools has to run on Pharo3 for now, it follows the Moose release/develipment cycle (for now). This means that when moose goes to Pharo4 (in a week or three), this will be merged back. > With the symbolic bytecode tab the other bytecode tab is not needed anymore, right? > Yes! I will remove it when merging. Marcus

Oct. 16, 2014