March 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Fwd: Amber git repo moved to the amber organisation

by phil＠highoctane.be

BTW, is there a way of having an '--all--' kind of protocol in the Amber browser? Phil 2013/3/3 Nicolas Petton <petton.nicolas(a)gmail.com>: > > > Begin forwarded message: > >> From: Nicolas Petton <petton.nicolas(a)gmail.com> >> Subject: Amber git repo moved to the amber organisation >> Date: March 3, 2013 6:42:52 PM GMT+01:00 >> To: Amber ML <amber-lang(a)googlegroups.com> >> >> Hi guys, >> >> amber has moved to https://github.com/amber-smalltalk/amber >> Update your git repo ;) >> >> Cheers, >> Nico > > -- > Nicolas Petton > http://www.nicolas-petton.fr > >

March 3, 2013

Re: [Pharo-project] Fwd: Amber git repo moved to the amber organisation

by phil＠highoctane.be

Because of the move? In Javascript console on http://amber-lang.net/ : GET https://assets.github.com/img/bec6c51521dcc8148146135149fe06a9cc737577?repo… 404 (Not Found) amber-lang.net:29 Phil 2013/3/3 Nicolas Petton <petton.nicolas(a)gmail.com>: > > > Begin forwarded message: > >> From: Nicolas Petton <petton.nicolas(a)gmail.com> >> Subject: Amber git repo moved to the amber organisation >> Date: March 3, 2013 6:42:52 PM GMT+01:00 >> To: Amber ML <amber-lang(a)googlegroups.com> >> >> Hi guys, >> >> amber has moved to https://github.com/amber-smalltalk/amber >> Update your git repo ;) >> >> Cheers, >> Nico > > -- > Nicolas Petton > http://www.nicolas-petton.fr > >

March 3, 2013

Re: [Pharo-project] about run tests from nautilus

by Camillo Bruni

On 2013-03-03, at 15:38, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > pfffff can we stop such kind of mess. > I frankly do not see the value of Think about the error messages here. > self should not be = $a Error message will be something like: Got 'adsfasdfasd' instead of $a > vs > self assert: self = $a and here? Assertion failed AKA 0 contextual information. Now it gets even worse when doing things like #should:raise: and friends. You have to fully restart the test case to even when debugging it just because you don't have decent error messages. Now this is what Phexample brings, 10 clicks less per failed assertion. I want that in 3.0. Besides in most cases a tree rewrite will do the proper transformation, so 0 effort for nice error messages. > I looked and most of the tests in Moose do not gain anything to rely on phExample. > And now such change break nautilus. they don't break nautilus if the test in nautilus were implemented as I said before.

March 3, 2013

[Pharo-project] Fwd: Amber git repo moved to the amber organisation

by Nicolas Petton

Begin forwarded message: > From: Nicolas Petton <petton.nicolas(a)gmail.com> > Subject: Amber git repo moved to the amber organisation > Date: March 3, 2013 6:42:52 PM GMT+01:00 > To: Amber ML <amber-lang(a)googlegroups.com> > > Hi guys, > > amber has moved to https://github.com/amber-smalltalk/amber > Update your git repo ;) > > Cheers, > Nico -- Nicolas Petton http://www.nicolas-petton.fr

March 3, 2013

[Pharo-project] about method lookup

by StÃ©phane Ducasse

Hi I'm rethinking about my objvlisp lecture. In this lecture I'm talking about building the objVlisp kernel in Smalltalk. Now everything is working well except the error handling when a method is not found with different arguments than the original. Methods are represented with blocks having different number of arguments. I have several send messages (I should simplify this in the future) ------------------------------------------ binarySend: selector with: argument "send the message whose selector is <selector> to the receiver. The arguments of the messages are an <argument>. The method is lookep up in the class of the receiver. self is an objObject or a objClass." | ans | ans := (self objClass lookup: selector for: self) value: self value: argument. ^ ans send: selector withArguments: arguments "send the message whose selector is <selector> to the receiver. The arguments of the messages are an array <arguments>. The method is lookep up in the class of the receiver. self is an objObject or a objClass." | ans | ans := (self objClass lookup: selector for: self) valueWithArguments: (Array with: self) , arguments. ^ ans lookup is as simple as ------------------------------ lookup: selector for: anObjObject "look for the method named <selector> starting in the receiver. The lookup is done for a message sent to <anObjObject>. self is an objClass" ^(self doesUnderstand: selector) ifTrue: [ self bodyOfMethod: selector] ifFalse: [self objName = #ObjObject ifFalse: [ (Obj giveClassNamed: self objSuperclassId) lookup: selector for: anObjObject.] ifTrue: [ anObjObject objClass lookup: #error for: anObjObject]] Now the problem is that error redefinition only works if the same number of arguments are used and this is not nice. For example error redefinition works: --------------------------------------------------- testErrorRedefinition "(self run: #testErrorRedefinition)" self should: [aPoint unarySend: #zork] raise: Error. (pointClass at: pointClass offsetForMethodDict) at: #error put: ([ :superClassOfClassDefiningTheMethod | [:objself | 33]] value: objectClass). self assert: (aPoint unarySend: #zork) = 33. I could use cull: or something like that to be able to execute the block representing the error message But I have the impression that I need a way to say that the lookup failed and that the arguments should be packed in a message object. I looked in the StackVM to see how the arguments were handled: how do we go some lookupMethodInClass: class | currentClass dictionary found | ... currentClass := class. [currentClass ~= objectMemory nilObject] whileTrue: [dictionary := objectMemory fetchPointer: MethodDictionaryIndex ofObject: currentClass. ... found := self lookupMethodInDictionary: dictionary. found ifTrue: [^currentClass]. currentClass := self superclassOf: currentClass]. ... "Cound not find a normal message -- raise exception #doesNotUnderstand:" self createActualMessageTo: class. messageSelector := objectMemory splObj: SelectorDoesNotUnderstand. ^self lookupMethodInClass: class Am I correct to believe that createActualMessageTo: eats up the call args and does basically what I would like to do Stef

March 3, 2013

Re: [Pharo-project] about run tests from nautilus

by Benjamin

If you want locally that your "should'* methods are seen as test by Nautilus, you should create a class inheriting from AbstractMethodIconAction and more or less copy the behaviour of MethodIsTestAction Ben On Mar 3, 2013, at 3:59 PM, Stefan Marr <smalltalk(a)stefan-marr.de> wrote: > Hi Benjamin: > > On 03 Mar 2013, at 10:55, Benjamin wrote: > >> Because some one decided that methods starting with "should" are also tests > > I added that change, because I didn't see an easy and extensible way to do it differently. > > Please see https://code.google.com/p/pharo/issues/detail?id=7367 > > If you could provide me with a proper hook in Nautilus, or use the facilities in SUnit to determine whether a method is a test that would be much better and avoid Stephane's problems. > > Thanks > Stefan > > > >> >> Ben >> >> On Mar 3, 2013, at 10:38 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>> Hi ben >>> >>> I do not know if you saw this behavior but when I press the button on the class of a test methods that are not tests >>> are also executed and reported as failures. >>> For example I got >>> >>> XMLNodeTest>>should: aBlock enumerate: aCollection >>> | enumerated | >>> >>> enumerated := OrderedCollection new. >>> aBlock value: [:each | enumerated add: each]. >>> self assert: enumerated = aCollection asOrderedCollection. >>> >>> executed while it is an helper. >>> With the testrunner I get a class with 100% green tests now. >>> but not with nautilus. >>> >>> Stef >> > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > >

March 3, 2013

[Pharo-project] Fwd: [Esug-list] [ANN] Minecraft Bindings

by stephane ducasse

Fun. I wonder if this is working on mac because my son has minecraft on my mac :) Stef Begin forwarded message: > From: Bert Freudenberg <bert(a)freudenbergs.de> > Subject: [Esug-list] [ANN] Minecraft Bindings > Date: February 25, 2013 3:00:36 AM GMT+01:00 > To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org>, ESUG Mailing list <esug-list(a)lists.esug.org> > > I'm happy to announce my Smalltalk bindings for "Minecraft: Pi Edition": > > > > Find out more at > http://croquetweak.blogspot.com/2013/02/smalltalk-bindings-for-minecraft-pi… > > - Bert - > > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org

March 3, 2013

Re: [Pharo-project] about OrderedCollection new replaceFrom: 1 to: 5 with: #(6 7 8 9 10) startingAt: 1

by stephane ducasse

Hi levente Thankx for the mail. >> > That OrderedCollection still has 0 size, so there's nothing to replace there. indeed this is what I saw. > It was an accident that the code worked before. Consider using #ofSize: instead of #new: if you want the collection to have slots. Yes I fixed the test by providing a receiver with equal size so that all the elements can be swapped nicely and all the tests are green now. > Levente > > P.S.: If XMLOrderedList is a subclass of OrderedCollection, then it's just plain wrong IMHO. Creating subclasses of collections in external packages is bad practice. It is wrapping an orderedCollection :) > >> >> So I fixed the tests of the XMLOrderedList to work but I'm a bit unsatisfied. >> >> Stef >> >>> Do you have an idea how I can handle that? Because XMLObservableList and XMLOrderedList implements >>> replaceFrom: to: with: startingAt: >>> >>> because there is no self makeRoomFor: (stop - self capacity) invocation. >>> >>> >>> in 1.4>> >>> replaceFrom: start to: stop with: replacement startingAt: repStart >>> "This destructively replaces elements from start to stop in the receiver >>> starting at index, repStart, in the sequenceable collection, >>> replacementCollection. Answer the receiver. No range checks are >>> performed." >>> >>> | index repOff | >>> repOff := repStart - start. >>> index := start - 1. >>> [(index := index + 1) <= stop] >>> whileTrue: [self at: index put: (replacement at: repOff + index)] >>> >>> at: anInteger put: anObject >>> "Put anObject at element index anInteger. at:put: cannot be used to >>> append, front or back, to an ordered collection; it is used by a >>> knowledgeable client to replace an element." >>> self ensureBoundsFrom: anInteger to: anInteger. >>> ^array at: anInteger + firstIndex - 1 put: anObject >>> >>> >>> in 1.2.1 >>> >>> replaceFrom: start to: stop with: replacement startingAt: repStart >>> "An ordered collection is growable, so a call to this can make the collection grow." >>> self makeRoomFor: (stop - self capacity). >>> array >>> replaceFrom: start + firstIndex - 1 >>> to: stop + firstIndex - 1 >>> with: replacement >>> startingAt: repStart. >>> lastIndex := lastIndex max: stop + firstIndex - 1. >> >> >> >

March 3, 2013

Re: [Pharo-project] about OrderedCollection new replaceFrom: 1 to: 5 with: #(6 7 8 9 10) startingAt: 1

by Levente Uzonyi

On Sun, 3 Mar 2013, stephane ducasse wrote: >> while in 1.4 and 2.0 >> OrderedCollection new replaceFrom: 1 to: 5 with: #(6 7 8 9 10) startingAt: 1 >> raised an error > > The problem I have is in fact that > > (OrderedCollection new: 10) replaceFrom: 1 to: 5 with: #(6 7 8 9 10) startingAt: 1 > > So even if the collection has enough space only a collection with enough elements can get them replaced. That OrderedCollection still has 0 size, so there's nothing to replace there. It was an accident that the code worked before. Consider using #ofSize: instead of #new: if you want the collection to have slots. Levente P.S.: If XMLOrderedList is a subclass of OrderedCollection, then it's just plain wrong IMHO. Creating subclasses of collections in external packages is bad practice. > > So I fixed the tests of the XMLOrderedList to work but I'm a bit unsatisfied. > > Stef > >> Do you have an idea how I can handle that? Because XMLObservableList and XMLOrderedList implements >> replaceFrom: to: with: startingAt: >> >> because there is no self makeRoomFor: (stop - self capacity) invocation. >> >> >> in 1.4>> >> replaceFrom: start to: stop with: replacement startingAt: repStart >> "This destructively replaces elements from start to stop in the receiver >> starting at index, repStart, in the sequenceable collection, >> replacementCollection. Answer the receiver. No range checks are >> performed." >> >> | index repOff | >> repOff := repStart - start. >> index := start - 1. >> [(index := index + 1) <= stop] >> whileTrue: [self at: index put: (replacement at: repOff + index)] >> >> at: anInteger put: anObject >> "Put anObject at element index anInteger. at:put: cannot be used to >> append, front or back, to an ordered collection; it is used by a >> knowledgeable client to replace an element." >> self ensureBoundsFrom: anInteger to: anInteger. >> ^array at: anInteger + firstIndex - 1 put: anObject >> >> >> in 1.2.1 >> >> replaceFrom: start to: stop with: replacement startingAt: repStart >> "An ordered collection is growable, so a call to this can make the collection grow." >> self makeRoomFor: (stop - self capacity). >> array >> replaceFrom: start + firstIndex - 1 >> to: stop + firstIndex - 1 >> with: replacement >> startingAt: repStart. >> lastIndex := lastIndex max: stop + firstIndex - 1. > > >

March 3, 2013

Re: [Pharo-project] Pastell is now migrated to SmalltalkHub and has a nice CI job

by Marcus Denker

On Mar 3, 2013, at 4:59 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > Pastell is now migrated to SmalltalkHub and has a nice CI job > > https://ci.inria.fr/pharo-contribution/ > > Did I said that I love continuous integration :). > > So coooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooool > > It is one of those things where one wonders how one could ever do anything without it. Marcus

March 3, 2013