April 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] Issue 3677 in pharo: A to:do: loop cannot modify the limit inside the block
by pharo＠googlecode.com April 1, 2011

April 1, 2011

Status: FixedWaitingToBePharoed Owner: stephane...(a)gmail.com Labels: Milestone-1.3 Type-Squeak New issue 3677 by stephane...(a)gmail.com: A to:do: loop cannot modify the limit inside the block http://code.google.com/p/pharo/issues/detail?id=3677 Nicolas Cellier uploaded a new version of Compiler to project The Trunk: http://source.squeak.org/trunk/Compiler-nice.184.mcz ==================== Summary ==================== Name: Compiler-nice.184 Author: nice Time: 12 January 2011, 10:09:27.038 pm UUID: ba12fb9c-6c57-429b-b415-1188e1faba8b Ancestors: Compiler-nice.183 Fix DecompilerTests>>#testDecompileLoopWithMovingLimit A to:do: loop cannot modify the limit inside the block =============== Diff against Compiler-nice.183 =============== Item was changed: ----- Method: MessageNode>>toDoFromWhileWithInit: (in category 'macro transformations') ----- toDoFromWhileWithInit: initStmt "Return nil, or a to:do: expression equivalent to this whileTrue:" | variable increment limit toDoBlock body test | (selector key == #whileTrue: and: [initStmt isAssignmentNode and: [initStmt variable isTemp]]) ifFalse: [^nil]. body := arguments last statements. variable := initStmt variable. increment := body last toDoIncrement: variable. (increment == nil or: [receiver statements size ~= 1]) ifTrue: [^nil]. test := receiver statements first. "Note: test chould really be checked that <= or >= comparison jibes with the sign of the (constant) increment" (test isMessageNode and: [(limit := test toDoLimit: variable) notNil]) ifFalse: [^nil]. + "The block must not overwrite the limit" + (limit isVariableNode and: [body anySatisfy: [:e | e isAssignmentNode and: [e variable = limit]]]) + ifTrue: [^nil]. toDoBlock := BlockNode statements: body allButLast returns: false. toDoBlock arguments: (Array with: variable). variable scope: -1. variable beBlockArg. ^MessageNode new receiver: initStmt value selector: (SelectorNode new key: #to:by:do: code: #macro) arguments: (Array with: limit with: increment with: toDoBlock) precedence: precedence!

1 2

Re: [Pharo-project] Issue 432 in pharo: CollectionExtensions
by pharo＠googlecode.com April 1, 2011

April 1, 2011

Updates: Status: Closed Comment #16 on issue 432 by marcus.d...(a)gmail.com: CollectionExtensions http://code.google.com/p/pharo/issues/detail?id=432 I added to the wishlist: http://code.google.com/p/pharo/wiki/IdeasToImplement "evaluate extension of moose for inclusions in pharo base library"

1 0

[Pharo-project] Regarding SimpleMorphic
by Torsten Bergmann April 1, 2011

April 1, 2011

>> Model >> TextModel >> Workspace >> PluggableTextModel >> TextProvider >> CodeProvider >> Browser >> HierarchyBrowser >> Debugger >> Inspector > > For me, this hierarchy is bad. > Workspace is not a model, it's a view basically. Take care not to confuse things here. If you think as "Workspace" as the window that is popping up when you open a workspace then you are on the wrong track. What you see is just one (morphic) view on a model/workspace instance. Workspace, Inspector, Browser - all these ARE models and you can have different looking views on it or open one or more views on the same model. Try |browserModel | browserModel := Browser new. Browser openBrowserView: (browserModel openEditString: nil) label: 'View 1'. Browser openBrowserView: (browserModel openEditString: nil) label: 'View 2'. Evaluate it, show the windows side by side and then click in one: two views on the same model and the changes are propagated to all dependent views. So they ARE MODELS: Take a browser for example. It should know about which class is selected, which methods to display, ... it's a code holder and manager thing. Nothing more ... it doesnt even need a UI. But it's "view parts" could be (one or more) real windows layouted in either morphic or a view in Squeaks old MVC or browser on a Seaside webpage (actually Seaside really has an HTML based browser). The browser model does for instance care if you are working on the instance or class side (see #metaClassIndicated and senders) - but it doesnt care if you switch either using buttons or radio buttons or whatever ... thats up to the view/presentation layer. In general you should be able to also drive this model without ever really having to open a view ... So that even the tools are models (although most people think of them as windows) is a major difference in Smalltalk's UI design compared to most UI frameworks in other languages. VisualWorks uses a special class ApplicationModel to subclass for tools and application windows to make this more clear. Java's Swing (written by people who designed VisualWorks UI first) has a similar but more excessive model design JButton -> ButtonModel, ... The other extreme is VB6/Delphi where you dont have a model at all and have to write an own if you want separation ;) Nothing said about the code quality of the current implementation in Pharo... Bye T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

4 7

[Pharo-project] [update 1.3] #13125
by Marcus Denker April 1, 2011

April 1, 2011

13125 ----- Issue 3922: Add ClassHierarchy Checks Issue 3920: String has extension for *graphics Issue 3896: 1.3 core has wrong theme enabled Issue 3769: Printing an object depends on #isKindOf: -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3769 in pharo: Printing an object depends on #isKindOf:
by pharo＠googlecode.com April 1, 2011

April 1, 2011

Status: Accepted Owner: Benjamin...(a)gmail.com New issue 3769 by Benjamin...(a)gmail.com: Printing an object depends on #isKindOf: http://code.google.com/p/pharo/issues/detail?id=3769 Due to the method: SmalltalkEditor>>#printIt "Treat the current text selection as an expression; evaluate it. Insert the description of the result of evaluation after the selection and then make this description the new text selection." | result | result := self evaluateSelection. ((result isKindOf: FakeClassPool) or: [result == #failedDoit]) ifTrue: [morph flash] ifFalse: [self afterSelectionInsertAndSelect: result printString] So when trying to print an object which is an instance of a class which directly inherits from ProtoObject, it raises an error

1 4

[Pharo-project] MC dependency issue
by Camillo Bruni April 1, 2011

April 1, 2011

Hhere is my problem. v169 has (v165 and v168) as ancestors. BUT v165 does no longer exist, locally nor on the squeaksource server. Is there way to manually fix this? Due to this I am currently unable to load any future versions... ~(x_x)~ camillo

1 0

[Pharo-project] Issue 3896 in pharo: 1.3 core has wrong theme enabled
by pharo＠googlecode.com April 1, 2011

April 1, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3896 by marcus.d...(a)gmail.com: 1.3 core has wrong theme enabled http://code.google.com/p/pharo/issues/detail?id=3896 ... should turn on Glamour theme

1 2

[Pharo-project] Issue 3920 in pharo: String has extension for *graphics
by pharo＠googlecode.com April 1, 2011

April 1, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com New issue 3920 by marcus.d...(a)gmail.com: String has extension for *graphics http://code.google.com/p/pharo/issues/detail?id=3920 String has extension for *graphics this package does not exist.

1 2

[Pharo-project] Issue 3922 in pharo: Add ClassHierarchy Checks
by pharo＠googlecode.com April 1, 2011

April 1, 2011

Status: New Owner: ---- New issue 3922 by camillob...(a)gmail.com: Add ClassHierarchy Checks http://code.google.com/p/pharo/issues/detail?id=3922 Verify all the classes in the system that superclass and subclass are set correctly: Attachments: ClassHierarchyTest.st 908 bytes

1 3

[Pharo-project] Dynamic Languages Symposium 2011: call for participation
by Theo D'Hondt April 1, 2011

April 1, 2011

Dynamic Languages Symposium 2011 Co-located with SPLASH 2011 In association with ACM SIGPLAN Portland, Oregon, USA, October 24, 2011 http://www.dynamic-languages-symposium.org/dls-11/ *** Call for papers *** The 7th Dynamic Languages Symposium (DLS) at SPLASH 2011 is a forum for discussion of dynamic languages, their implementation and application. While mature dynamic languages including Smalltalk, Lisp, Scheme, Self, Prolog, and APL continue to grow and inspire new converts, a new generation of dynamic scripting languages such as Python, Ruby, PHP, Tcl, Lua, and JavaScript are successful in a wide range of applications. DLS provides a place for researchers and practitioners to come together and share their knowledge, experience, and ideas for future research and development. DLS 2011 invites high quality papers reporting original research, innovative contributions or experience related to dynamic languages, their implementation and application. Accepted Papers will be published in the ACM Digital Library. Areas of interest include but are not limited to: - Innovative language features and implementation techniques - Development and platform support, tools - Interesting applications - Domain-oriented programming - Very late binding, dynamic composition, and runtime adaptation - Reflection and meta-programming - Software evolution - Language symbiosis and multi-paradigm languages - Dynamic optimization - Hardware support - Experience reports and case studies - Educational approaches and perspectives - Object-oriented, aspect-oriented, and context-oriented programming * Submissions and proceedings * We invite original contributions that neither have been published previously nor are under review by other refereed events or publications. Research papers should describe work that advances the current state of the art. Experience papers should be of broad interest and should describe insights gained from substantive practical applications. The program committee will evaluate each contributed paper based on its relevance, significance, clarity, and originality. Accepted papers will be published in the ACM Digital Library. Papers are to be submitted electronically at http://www.easychair.org/conferences?conf=dls2011 in PDF format. Submissions must not exceed 12 pages and need to use the ACM format, templates for which can be found at http://www.acm.org/sigs/pubs/proceed/template.html. * Important dates * Submission of papers: June 17, 2011 (hard deadline) Author notification: July 19, 2011 Final versions due: August 19, 2011 DLS 2011: October 24, 2011 SPLASH 2011: October 22-27, 2011 * Program chair * Theo D'Hondt, Software Languages Lab, Vrije Universiteit Brussel, Belgium * Program committee * Andrew Black, Portland State University, USA William R. Cook, University of Texas at Austin, USA Marc Feeley, University of Montreal, Canada Roberto Ierusalimschy, PUC-Rio, Brazil Michele Lanza, University of Lugano, Switzerland Hidehiko Masuhara, University of Tokyo, Japan Mira Mezini, University of Darmstadt, Germany Mark Miller, Google, USA Manuel Serrano, INRIA Nice, France Laurence Tratt, Middlesex University, UK David Ungar, IBM, USA Didier Verna, EPITA Research and Development Laboratory, France ________________ Theo D'Hondt tjdhondt(a)vub.ac.be

1 0