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

[Pharo-project] Issue 3981 in pharo: #<= on SourcedMethodReference is very slow
by pharo＠googlecode.com April 16, 2011

April 16, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com New issue 3981 by marcus.d...(a)gmail.com: #<= on SourcedMethodReference is very slow http://code.google.com/p/pharo/issues/detail?id=3981 ... as it accesses the sources. (it slows down rendering "senders of" a lot. And there I wonder why we sort them for time at all?)

1 8

[Pharo-project] [update 1.3] #13159
by Marcus Denker April 16, 2011

April 16, 2011

13159 ----- Issue 4031: Remove Mail to list in ChangeSorter Issue 4030: defaultBackgroundColor should not use self theme Issue 3872: [Failing Test] 1.3 HttpUrlTest.testHttps Issue 3598: [Failing Test]Tests.Compiler.CompilerTest.testNotInteractiveInBlockTempArgumentShadowing Issue 3981: #<= on SourcedMethodReference is very slow -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3598 in pharo: [Failing Test]Tests.Compiler.CompilerTest.testNotInteractiveInBlockTempArgumentShadowing
by pharo＠googlecode.com April 16, 2011

April 16, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3598 by marcus.d...(a)gmail.com: [Failing Test]Tests.Compiler.CompilerTest.testNotInteractiveInBlockTempArgumentShadowing http://code.google.com/p/pharo/issues/detail?id=3598 Tests.Compiler.CompilerTest.testNotInteractiveInBlockTempArgumentShadowing - fix is simple : initialize the CompilerTest interactive ivar before running tests.

1 4

[Pharo-project] Issue 3872 in pharo: [Failing Test] 1.3 HttpUrlTest.testHttps
by pharo＠googlecode.com April 16, 2011

April 16, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3872 by marcus.d...(a)gmail.com: [Failing Test] 1.3 HttpUrlTest.testHttps http://code.google.com/p/pharo/issues/detail?id=3872 >>> NetworkTests.Url.HttpUrlTest.testHttps 0.0010 99

1 6

[Pharo-project] Issue 3587 in pharo: Clean up handling of WideStrings
by pharo＠googlecode.com April 16, 2011

April 16, 2011

Status: New Owner: ---- New issue 3587 by sean.p.d...(a)gmail.com: Clean up handling of WideStrings http://code.google.com/p/pharo/issues/detail?id=3587 Code in various places in the system query #isWideString followed by an ifTrue:ifFalse: The Smalltalk way would be to issue a command to the String, which is overridden in the wide subclasses. Attached is a changeset that makes some of these changes. All Collections and Morphic tests green in Pharo1.2rc1 Latest update: #12320 Attachments: Wide String cleanup.3.cs 6.1 KB

1 4

[Pharo-project] Issue 3341 in pharo: use #= for integer comparison instead of #==
by pharo＠googlecode.com April 16, 2011

April 16, 2011

Status: Accepted Owner: stephane.ducasse Labels: Milestone-1.3 Type-Squeak New issue 3341 by stephane.ducasse: use #= for integer comparison instead of #== http://code.google.com/p/pharo/issues/detail?id=3341 Please read the original statement of dan. http://bugs.squeak.org/view.php?id=2788 I think that this bunch of fixes are important. ==================== Summary ==================== Name: Collections-ul.406 Author: ul Time: 15 November 2010, 10:30:39.825 am UUID: 9cd8fc97-4673-3340-9ea2-2f3dbd5f38e3 Ancestors: Collections-cmm.405 - use #= for integer comparison instead of #== (http://bugs.squeak.org/view.php?id=2788 ) =============== Diff against Collections-cmm.405 =============== Item was changed: ----- Method: SequenceableCollection>>after:ifAbsent: (in category 'accessing') ----- after: target ifAbsent: exceptionBlock "Answer the element after target. Answer the result of evaluation the exceptionBlock if target is not in the receiver, or if there are no elements after it." | index | index := self indexOf: target. + ^ (index = 0 or: [index = self size]) - ^ (index == 0 or: [index = self size]) ifTrue: [exceptionBlock value] ifFalse: [self at: index + 1]! Item was changed: ----- Method: SequenceableCollection>>before:ifAbsent: (in category 'accessing') ----- before: target ifAbsent: exceptionBlock "Answer the receiver's element immediately before target. Answer the result of evaluating the exceptionBlock if target is not an element of the receiver, or if there are no elements before it." | index | index := self indexOf: target. + ^ (index = 0 or: [index = 1]) - ^ (index == 0 or: [index == 1]) ifTrue: [exceptionBlock value] ifFalse: [self at: index - 1]! Item was changed: ----- Method: String>>asIdentifier: (in category 'converting') ----- asIdentifier: shouldBeCapitalized "Return a legal identifier, with first character in upper case if shouldBeCapitalized is true, else lower case. This will always return a legal identifier, even for an empty string" | aString firstChar firstLetterPosition | aString := self select: [:el | el isAlphaNumeric]. firstLetterPosition := aString findFirst: [:ch | ch isLetter]. + aString := firstLetterPosition = 0 - aString := firstLetterPosition == 0 ifFalse: [aString copyFrom: firstLetterPosition to: aString size] ifTrue: ['a', aString]. firstChar := shouldBeCapitalized ifTrue: [aString first asUppercase] ifFalse: [aString first asLowercase]. ^ firstChar asString, (aString copyFrom: 2 to: aString size) " '234Fred987' asIdentifier: false '235Fred987' asIdentifier: true '' asIdentifier: true '()87234' asIdentifier: false '())z>=PPve889 U >' asIdentifier: false "! Item was changed: ----- Method: String>>initialIntegerOrNil (in category 'converting') ----- initialIntegerOrNil "Answer the integer represented by the leading digits of the receiver, or nil if the receiver does not begin with a digit" | firstNonDigit | + (self size = 0 or: [self first isDigit not]) ifTrue: [^ nil]. - (self size == 0 or: [self first isDigit not]) ifTrue: [^ nil]. firstNonDigit := (self findFirst: [:m | m isDigit not]). firstNonDigit = 0 ifTrue: [firstNonDigit := self size + 1]. ^ (self copyFrom: 1 to: (firstNonDigit - 1)) asNumber " '234Whoopie' initialIntegerOrNil 'wimpy' initialIntegerOrNil '234' initialIntegerOrNil '2N' initialIntegerOrNil '2' initialIntegerOrNil ' 89Ten ' initialIntegerOrNil '78 92' initialIntegerOrNil " ! Item was changed: ----- Method: String>>sansPeriodSuffix (in category 'converting') ----- sansPeriodSuffix "Return a copy of the receiver up to, but not including, the first period. If the receiver's *first* character is a period, then just return the entire receiver. " | likely | likely := self copyUpTo: $.. + ^ likely size = 0 - ^ likely size == 0 ifTrue: [self] ifFalse: [likely]! Item was changed: ----- Method: String>>utf8ToIso (in category 'internet') ----- utf8ToIso "Only UTF-8 characters that maps to 8-bit ISO-8559-1 values are converted. Others raises an error" | s i c v c2 v2 | s := WriteStream on: (String new: self size). i := 1. [i <= self size] whileTrue: [ c := self at: i. i:=i+1. v := c asciiValue. (v > 128) ifFalse: [ s nextPut: c ] + ifTrue: [((v bitAnd: 252) = 192) - ifTrue: [((v bitAnd: 252) == 192) ifFalse: [self error: 'illegal UTF-8 ISO character'] ifTrue: [ (i > self size) ifTrue: [ self error: 'illegal end-of-string, expected 2nd byte of UTF-8']. c2 := self at: i. i:=i+1. v2 := c2 asciiValue. ((v2 bitAnd: 192) = 128) ifFalse: [self error: 'illegal 2nd UTF-8 char']. s nextPut: ((v2 bitAnd: 63) bitOr: ((v << 6) bitAnd: 192)) asCharacter]]]. ^s contents. ! Item was changed: ----- Method: Symbol class>>selectorsContaining: (in category 'access') ----- selectorsContaining: aString "Answer a list of selectors that contain aString within them. Case-insensitive. Does return symbols that begin with a capital letter." | size selectorList ascii | selectorList := OrderedCollection new. (size := aString size) = 0 ifTrue: [^selectorList]. aString size = 1 ifTrue: [ ascii := aString first asciiValue. ascii < 128 ifTrue: [selectorList add: (OneCharacterSymbols at: ascii+1)] ]. (aString first isLetter or: [aString first isDigit]) ifFalse: [ + aString size = 2 ifTrue: - aString size == 2 ifTrue: [Symbol hasInterned: aString ifTrue: [:s | selectorList add: s]]. ^selectorList ]. selectorList := selectorList copyFrom: 2 to: selectorList size. self allSymbolTablesDo: [:each | each size >= size ifTrue: [(each findSubstring: aString in: each startingAt: 1 matchTable: CaseInsensitiveOrder) > 0 ifTrue: [selectorList add: each]]]. ^selectorList reject: [:each | "reject non-selectors, but keep ones that begin with an uppercase" each numArgs < 0 and: [each asString withFirstCharacterDownshifted numArgs < 0]]. "Symbol selectorsContaining: 'scon'"! Item was changed: ----- Method: Symbol>>isInfix (in category 'testing') ----- isInfix "Answer whether the receiver is an infix message selector." + ^ self precedence = 2! - ^ self precedence == 2! Item was changed: ----- Method: Symbol>>isKeyword (in category 'testing') ----- isKeyword "Answer whether the receiver is a message keyword." + ^ self precedence = 3! - ^ self precedence == 3! Item was changed: ----- Method: Symbol>>isUnary (in category 'testing') ----- isUnary "Answer whether the receiver is an unary message selector." + ^ self precedence = 1! - ^ self precedence == 1!

1 13

[Pharo-project] Issue 4030 in pharo: defaultBackgroundColor should not use self theme
by pharo＠googlecode.com April 16, 2011

April 16, 2011

Status: Accepted Owner: marianopeck New issue 4030 by marianopeck: defaultBackgroundColor should not use self theme http://code.google.com/p/pharo/issues/detail?id=4030 Object >> defaultBackgroundColor from *Tools-Base defaultBackgroundColor "Answer the color to be used as the base window color for a window whose model is an object of the receiver's class" ^ self theme windowColorFor: self But Object dnu #them. So...changed to: defaultBackgroundColor "Answer the color to be used as the base window color for a window whose model is an object of the receiver's class" "I don't want to do a self theme because otherwise I will need to implement it on Object" ^ UITheme current windowColorFor: self

1 2

[Pharo-project] Issue 4031 in pharo: Remove "Mail to list" in ChangeSorter
by pharo＠googlecode.com April 16, 2011

April 16, 2011

Status: FixProposed Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 4031 by marcus.d...(a)gmail.com: Remove "Mail to list" in ChangeSorter http://code.google.com/p/pharo/issues/detail?id=4031 ... not used anymore (we use this tracker instead) Attachments: CleanChangeSorte.2.cs 1.9 KB

1 2

[Pharo-project] DYLA @ TOOLS EUROPE'11
by Alexandre Bergel April 16, 2011

April 16, 2011

Hi! Dyla is a successful series of workshop on dynamic languages. As the previous year, It will be collocated with TOOLS EUROPE. The deadline is April 18 for a two-pages submission. http://scg.unibe.ch/wiki/events/dyla2011 Feel free to ask for more details. Regards, Alexandre --------- DYLA @ TOOLS EUROPE'11 July 1, 2011, ZÃ¼rich, Switzerland --------- The DYLA Workshop series focuses on the revival of dynamic languages. These days, dynamic languages (like Lisp, Ruby, Python, JavaScript, Lua, etc...) are getting ever more popular. This is a call to arms for academia! We need to explore the future of dynamic languages through its human aspects and technical issues. We also ought to look back and pick up solutions from existing dynamic languages (such as Scheme, Smalltalk, JRuby, Jython, Groovy, or Self) to be rediscovered and spread around. --------- Goal and Topics --------- The goal of this workshop is to act as a forum where we can discuss new advances in the design, implementation and application of dynamically typed languages that, sometimes radically, diverge from the statically typed class-based mainstream with limited reflective capabilities. Another objective of the workshop is to discuss new as well as older "forgotten" languages and features in this context. Topics of interest include, but are certainly not limited to: Human aspects of dynamic languages, for example... -empirical studies about the application of dynamic languages -best practices and patterns specific to dynamic languages -program correctness through unit testing (as opposed to types) -improved or novel IDE support for dynamic languages -use of dynamic features by library & framework developers -scripting of static application with dynamic languages -reverse engineering and analysis of dynamic applications Technical aspects of dynamic languages, for example... -what features make a language a dynamic one? -agents, actors, active object, distribution, concurrency and mobility -delegation, prototypes, mixins, traits -first-class closures, continuations, environments -reflection and meta-programming -(dynamic) aspects for dynamic languages -higher-order objects & messages -...other exotic dynamic features -multi-paradigm & static/dynamic-marriages -(concurrent/distributed/mobile/aspect) virtual machines -optimisation of dynamic languages -automated reasoning about programs written in dynamic languages - type systems for dynamic languages, pluggable types, partial typing, type reconstruction... And any topic relevant in applying and/or supporting dynamic languages: Smalltalk, Python, Ruby, Javascript, Scheme, Lisp, Self, ABCL, Prolog, Ioke, Clojure and many more... --------- Submissions --------- The workshop will have a demo-oriented style. The idea is to allow participants to demonstrate new and interesting features and discuss what they feel is relevant for the dynamic language community. Participants need to submit a 2-4 page position paper of their work in *ACM sig-alternate.cls>http://www.acm.org/sigs/publications/proceedings-templates* format. At the workshop, participants will be asked to give 10-minute "lightning demos" of their contributions. --------- Important dates --------- -Paper submission deadline: ''April 18, 2011'' -Paper acceptance notification: ''May 14, 2011'' -Camera ready of papers: ''May 31, 2011'' -Camera ready of Workshop Proceedings: ''July 1, 2011'' --------- Organizers --------- -*Alexandre Bergel>http://bergel.eu*, University of Chile, Santiago, Chile -*Carl Friedrich Bolz>http://cfbolz.de*, Heinrich-Heine-Universitaet, Duesseldorf, Germany -*Stephane Ducasse>http://stephane.ducasse.free.fr/*, RMoD Research group, INRIA Lille-Nord Europe, France -*Lukas Renggli>http://www.lukas-renggli.ch/*, Google, Switzerland -*Jorge Ressia>http://www.jorgeressia.com/*, University of Bern, Switzerland --------- Program committee (under construction) --------- -Gabriela Arevalo, University of La Plata, Argentina -Jean-Baptiste Arnaud, RMoD Team, INRIA Lille Nord Europe, France -Alexandre Bergel, University of Chile, Chile -Carl Friedrich Bolz, Heinrich-Heine-Universitaet, Germany -Stephane Ducasse, INRIA Lille Nord Europe, France -Tom van Cutsem, Vrije Universiteit Brussel, Belgium -Tom Dinkelaker, Technische Universitaet Darmstadt -Johan Fabry, University of Chile, chile -Roberto Ierusalimschy, Pontifical University in Rio de Janeiro -James Noble, Victoria University of Wellington, New Zealand -Lukas Renggli, Google, Switzerland -Jorge Ressia, SCG, University of Bern -David Schneider, Heinrich-Heine-Universitaet, Duesseldorf, Germany http://scg.unibe.ch/wiki/events/dyla2011 http://twitter.com/dyla11 -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

[Pharo-project] Order in the Hudson for CogVMs
by Mariano Martinez Peck April 16, 2011

April 16, 2011

Hi...I love what you are doing in Hudson, but the Cog part it is quite a mess right now. I would love to see some organization. 1) Not all VMs have both: the build and the sources. Example, https://pharo-ic.lille.inria.fr/hudson/view/Cog/job/Cog%20Mac%20Cocoa/ has only the sources. But https://pharo-ic.lille.inria.fr/hudson/view/Cog/job/Cog%20Mac%20Carbon/ has both. If someone follows this: http://code.google.com/p/cog/wiki/CMakeVMMaker then such info is incorrect. 2) We are mixing "Release" VMs from experiments. I would create two Hudson tabs 2.1) one for Cog, where we have the "release" VMs. This means, things like Cog Mac Carbon, Cog Mac Cocoa, Cog Unix, CogMT Mac Cocoa, MT Cog Unix, Stack VM Unix, StackVM Mac Carbon, StackVM Mac Cocoa, etc. 2.2) One for experiments, like: Check cogvm.unthinkable.org, Cog Git Tracker (cog-osx), Cog Git Tracker (sig-cog), Cog.FreeBSD.unthinkable,Sista Only if we do that, we will be able to use Hudson like a place to say to users to download a VM. Otherwise, we cannot. There are several targets and they are confusing. Cheers -- Mariano http://marianopeck.wordpress.com

1 0