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

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

by phil＠highoctane.be

Now, the getting started links look like gone or not working nicely on github's Wiki It is hard to find http://amber-lang.net/documentation.html#Tutorials from there. Phil 2013/3/3 Manfred KrÃ¶hnert <mkroehnert42(a)googlemail.com>: > Hi Phil, > > On Sun, Mar 3, 2013 at 8:21 PM, phil(a)highoctane.be <phil(a)highoctane.be> > wrote: >> >> 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 > > > This error has already been fixed in the master branch. > After a new version is released it will also be fixed on the main website. > > Best, > Manfred

March 4, 2013

Re: [Pharo-project] ubuntu and debian support

by phil＠highoctane.be

Hello, I got the VM running fine on Debian 6 amd64 version and posted the steps. http://www.mail-archive.com/pharo-project@lists.gforge.inria.fr/msg73627.ht… Mostly symlinking issues. I guess you can the VM to work on Ubuntu 10 without hassles doing more or less the same thing. Is your Ubuntu a 32-bit install or a 64-bit one? Phil 2013/3/4 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > Moose 4.7 was just released on top of Pharo 1.4, and now we are moving to Pharo 2.0. > > In the process of upgrading, we need to get the continuous integration server build on Pharo 2.0. However, the current server is a Ubuntu 10, and it seems that the latest Pharo VM does not run on this machine (as discussed before, I get /lib32/libc.so.6: version `GLIBC_2.15' not found). > > I understand the need to break loose from old operating systems, and Ubuntu 10 is rather old, but I am limited by the OSs offered by my virtual host provider. The other option would be to use Debian version 6. > > However, before switching to either another operating system or another provider, I could use some answers to the following questions: > - Is the problem with Ubuntu 10 systematic, or can it be solved somehow (perhaps I can install something on my OS to get it to work)? > - If it cannot be solved, does the Pharo VM work on Debian 6? > - Otherwise, does anyone know a provider that supports the latest Ubuntu (version 12 at this moment) > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "In a world where everything is moving ever faster, > one might have better chances to win by moving slower." > > > >

March 4, 2013

[Pharo-project] ubuntu and debian support

by Tudor Girba

Hi, Moose 4.7 was just released on top of Pharo 1.4, and now we are moving to Pharo 2.0. In the process of upgrading, we need to get the continuous integration server build on Pharo 2.0. However, the current server is a Ubuntu 10, and it seems that the latest Pharo VM does not run on this machine (as discussed before, I get /lib32/libc.so.6: version `GLIBC_2.15' not found). I understand the need to break loose from old operating systems, and Ubuntu 10 is rather old, but I am limited by the OSs offered by my virtual host provider. The other option would be to use Debian version 6. However, before switching to either another operating system or another provider, I could use some answers to the following questions: - Is the problem with Ubuntu 10 systematic, or can it be solved somehow (perhaps I can install something on my OS to get it to work)? - If it cannot be solved, does the Pharo VM work on Debian 6? - Otherwise, does anyone know a provider that supports the latest Ubuntu (version 12 at this moment) Cheers, Doru -- www.tudorgirba.com "In a world where everything is moving ever faster, one might have better chances to win by moving slower."

March 4, 2013

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

by Igor Stasenko

On 3 March 2013 17:52, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > Fun. > > I wonder if this is working on mac because my son has minecraft on my mac > :) > > by looking at example, it looks like it use socket to connect with MC. If it so, then i don't see why it should not work (as long as you using MC version which supports this API). > 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 > > > -- Best regards, Igor Stasenko.

March 4, 2013

Re: [Pharo-project] about method lookup

by Igor Stasenko

On 3 March 2013 18:33, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > 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 yes. On DNU, an original message is replaced with #doesNotUnderstand: as selector and Message instance, which contains original message (the receiver is unchanged). Next, VM again does a lookup for #doesNotUnderstand: and here is caveat: if object does not understands #doesNotUnderstand: there is no way how you can proceed, so execution should fail with some error. > > Stef -- Best regards, Igor Stasenko.

March 4, 2013

[Pharo-project] Android VM builds restored

by Dmitry Golubovsky

Hi, The unbundled Android VM builds on new Jenkins have been restored. No changes in the source codes on my part, and I tried to preserve the building environment. The new download page is at: https://ci.inria.fr/pharo-contribution/job/CogDroid/ Feel free to download and try it with your images. Bundled builds haven't been restored yet, but I am planning to work on it in the future. Thanks. -- Dmitry Golubovsky Anywhere on the Web

March 3, 2013

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

by phil＠highoctane.be

Okay :-) Was just busy playing around and noticed that in my console. Phil 2013/3/3 Manfred KrÃ¶hnert <mkroehnert42(a)googlemail.com>: > Hi Phil, > > On Sun, Mar 3, 2013 at 8:21 PM, phil(a)highoctane.be <phil(a)highoctane.be> > wrote: >> >> 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 > > > This error has already been fixed in the master branch. > After a new version is released it will also be fixed on the main website. > > Best, > Manfred

March 3, 2013

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

by Manfred KrÃ¶hnert

Hi Phil, On Sun, Mar 3, 2013 at 8:21 PM, phil(a)highoctane.be <phil(a)highoctane.be>wrote: > Because of the move? > > In Javascript console on http://amber-lang.net/ : > > GET > https://assets.github.com/img/bec6c51521dcc8148146135149fe06a9cc737577?repo > â¦3.amazonaws.com > %2Fgithub%2Fribbons%2Fforkme_left_darkblue_121621.png&path= > 404 (Not Found) amber-lang.net:29 This error has already been fixed in the master branch. After a new version is released it will also be fixed on the main website. Best, Manfred

March 3, 2013

Re: [Pharo-project] Test Resources

by Jan Vrany

On 02/03/13 09:03, stephane ducasse wrote: > sounds really interesting. I want this features since long time. > So where can I find the latest maintained version of SUnit? The current version for St/X maintained by me could be found at https://swing.fit.cvut.cz/hg/stx.goodies.sunit/ (branch default) or at http://www.exept.de/cgi-bin/viewvc.cgi/stx/goodies/sunit/ For VW, it suppose it lives in Cincom's public repository. Jan

March 3, 2013

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

by stephane ducasse

On Mar 3, 2013, at 9:52 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Stef, > > this is not a problem of SqS. I copied the two new versions > manually today back from MetacelloRepository to the SqS/Pastell > repo since it looks like they were missing there. strange because I just queried from the pastell ss repo and my script is always the same I always use this one and when there is no config I look around. | go | go := Gofer new. go squeaksource: 'DrGeo'. (go allResolved select: [ :each | 'DrGeo*' match: each packageName]) do: [ :pack | pack packageName crLog. go package: pack packageName; fetch] > This is historic and from the time when usually sqS/MetacelloRepository > was used for all configurations. I do not think so. Because I do not look at MetacelloRepository to migrate packages. I pushed there after I'm done. > It's not a real problem that the numbers have changed - I dont think many > people reference Pastell. I already updated my other configs. I will follow the semantics versioning now (not now). At least I can understand 1.2.0 now. Probably that we should reify these boring strings but for that we need tools. but I will copy and paste the semantics else nobody will ever understand it. This is why we need tools to build configurations. > If you have a script it should take care in the future if a newer > ConfigurationOfXXX is either > - in sqS/MetacelloRepository > - or the projects own directory > > Regarding version numbers: I would vote for two digits - Major and minor version. for me I do not care. I just want something that I can understand. and 1.0.2 for going from something that does not work to something that does is not sometihng I can remember. > So usually you start with 0.1, then 0.2, 0.3, ... > > When you make a patch to an old (problematic) version then you branch > with a patch number. So for instance 0.2.1 means it is the first patch > for Version 0.2. > > > Bye Bye ;) > T. > > > >

March 3, 2013