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

Re: [Pharo-project] PPElementParser & a small PetitTests contribution

by Lukas Renggli

Ahh, I didn't understand that you try parse nested structures :-) I discussed with Doru at some point about that and I believe he intended to implement some support for it, but I don't know the current state. Maybe you want to check with him? Lukas On 13 August 2011 15:17, Damien Pollet <damien.pollet(a)gmail.com> wrote: > On 13 August 2011 15:06, Lukas Renggli <renggli(a)gmail.com> wrote: >> Can you give a real-world example that shows what you want to do? Do >> you just want to customize the error message if elementParser fails? > > I want to parse arrays of strings, while also parsing each element > depending on where the array parse goes, e.g: > > #('command' '--option' '123') > > With a parser defined roughly like: > (PPElementParser on: (#word asParser plus token end)) , > Â Â (PPElementParser on: ('--' asParser , #word asParser plus token > end ==> [:nodes | Option named: nodes second]) , > Â Â (PPElementParser on: (#digit asParser plus token end ==> [:token | > token value asNumber]) > > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet > > -- Lukas Renggli www.lukas-renggli.ch

Aug. 13, 2011

Re: [Pharo-project] #name

by Max Leske

I have. For example: Implement #name in a couple of classes that form a hierarchy. Since #name is implemented in Object, you might not implement #name in an abstract superclass to send "self subclassResponsibility". Now, if you forget to implement #name in one of the classes in your hierarchy, you don't get a DNU but some cryptic exception since the value you expect from #name is not the one you get. I know, this isn't really that tragic but I've had it happen to me twice I think and both times I spent a couple of minutes tracking down the problem. Think of the time that is lost if only a couple of us encounter this problem once or twice. Max On 12.08.2011, at 19:18, Pat Maddox wrote: > I use #name all over the place and have never had problems. > > > > On Aug 12, 2011, at 9:35 AM, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > >> How is #name used by the system? I often want to use it in my classes, but I >> don't want to mess with whatever Object is doing with it. There are +++ >> senders. >> >> On the flip side, should the system use a different, more specific, >> intention-revealing selector to avoid this confusion? >> >> Thanks. >> Sean >> >> -- >> View this message in context: http://forum.world.st/name-tp3739677p3739677.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >

Aug. 13, 2011

Re: [Pharo-project] Why is #stepTime in the 'testing' protocol?

by StÃ©phane Ducasse

yes Sean what would be cool is that if you could come up with a list protocol typical method selector Then I would like to use this list and see how to can automatically recategorize a lot of methods in the system Stef On Aug 13, 2011, at 12:36 AM, Sean P. DeNigris wrote: > It should be in 'stepping and presenter' with the other step methods, no? > > S > > -- > View this message in context: http://forum.world.st/Why-is-stepTime-in-the-testing-protocol-tp3740584p374… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Aug. 13, 2011

Re: [Pharo-project] uMorphic

by StÃ©phane Ducasse

Pavel (i'm painting half of my house so just scanning at mails) but what we want to do is to have Morphic Core Morphic Morphs borderedMorph, ellispe Morphic Widgets List.... So any step in that direction is welcomed. On Aug 12, 2011, at 10:35 PM, Pavel Krivanek wrote: > Hi, > > this code (see the attachment) can help in Morphic refactoring and > repackaging a lot. It contains basic Morphic classes and methods > (about 530) that represent the core of Morphic functionality. > It is code that can be loaded into PharoKernel-Gofer image, it > initializes Morphic and the only thing it can do is to open basic > morph, grab and move it with mouse. It doesn't have Fonts support, > SystemWindows etc. > It was generated mostly automatically and it doesn't modify any code > so the resultant image is very unclean and it crashes easily. > > -- Pavel > <uMorphic.cs.zip>

Aug. 13, 2011

Re: [Pharo-project] #name

by StÃ©phane Ducasse

On Aug 12, 2011, at 5:35 PM, Sean P. DeNigris wrote: > How is #name used by the system? I often want to use it in my classes, but I > don't want to mess with whatever Object is doing with it. There are +++ > senders. Yes name is object is quite a bad smell to me. This is on my radar to nule setname: and friends. Since this is only used to give name to part in etoyish morphic If I remember also pay attention for class methods too. > On the flip side, should the system use a different, more specific, > intention-revealing selector to avoid this confusion? > > Thanks. > Sean > > -- > View this message in context: http://forum.world.st/name-tp3739677p3739677.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Aug. 13, 2011

Re: [Pharo-project] Ring question

by StÃ©phane Ducasse

But it would be good to have a class method too. Can you add one? Stef On Aug 12, 2011, at 5:51 PM, Veronica Isabel Uquillas Gomez wrote: > > On 12 Aug 2011, at 17:12, StÃ©phane Ducasse wrote: > >> Hi veronica >> >> How do I create a RGMethodDefinition for a SmalltalkClass >> >> I used class:selector: but this is wrong because for example for a class >> >> RGMethodDefinition >> class: Point class >> selector: #new >> >> but then I get error when querying className that 'Point class' is not in the SystemDictionary or something like that. > > indeed that only works for ring classes.. > > The other option is using the factory > > RGFactory current createMethodNamed: aSymbol realParent: aClass > > >> >> I suggest to add a creation method for realClass: selector: >> >> what do you think? >> > it will be handy for tools ( so far i did not need it) > > gonna add it > >> Stef >

Aug. 13, 2011

Re: [Pharo-project] formatting style

by StÃ©phane Ducasse

On Aug 12, 2011, at 3:58 PM, Lukas Renggli wrote: > On 12 August 2011 15:42, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> I mean that I prefer >> >>>> Smalltalk tools >>>> register: ;lkl;k;lk;l >>>> in: lkl;k;lkl;kl; >> >> over >> >>>> Smalltalk tools register: ;lkl;k;lk;l >>>> in: lkl;k;lkl;kl; >> >> >> because I do not see fast that the message is register: in: > > Hmm, I still don't understand your example because the $; has semantic > meaning and because the example doesn't even compile :-) >>>> Smalltalk tools >>>> register: 'string' >>>> in: 'hkjjkhkhjh' :) > >> and I guess that you are formatting the way I like but the rb formatter may be wrong because > > You can configure after how how many keyword parts (that is probably > too low right now) it should print on one line. Also you can tell it > how many characters per line you maximally want (used to be 80, I > think i changed the default to 100; but probably should be inifite). > I will play with it. I'm really thinking that having a systematic formatting of code within the core would be good. > Lukas > >> >> On Aug 12, 2011, at 1:49 PM, Lukas Renggli wrote: >> >>> Hmm, I don't get your example. >>> >>> What I changed is that the formatter does not enforce the useless >>> parenthesis around the receiver of a cascade. Can be disabled though. >>> >>> Also note that there are settings to automatically format code on >>> display and/or accept. I use the "on display" mode often to read ugly >>> code :-) >>> >>> Lukas >>> >>> On 12 August 2011 13:29, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>> Yes >>>> >>>> Smalltalk tools >>>> register: ;lkl;k;lk;l >>>> in: lkl;k;lkl;kl; >>>> >>>> >>>> stef >>>> On Aug 12, 2011, at 1:20 PM, Lukas Renggli wrote: >>>> >>>>>> I always think of this a the Seaside style, but I am not sure if that is a correct attribution. >>>>> >>>>> Haha, thank you. >>>>> >>>>> Actually the refactoring browser formatter with the default settings >>>>> is quite close to the Seaside style, I just recently submitted some >>>>> fixes for cascades. The only thing that I don't like about the >>>>> automatic formatter is how the brackets in multiline blocks are >>>>> aligned. Anyway, the formatter would style #inject:into: as you >>>>> suggest. >>>>> >>>>> Lukas >>>>> >>>>> -- >>>>> Lukas Renggli >>>>> www.lukas-renggli.ch >>>>> >>>> >>>> >>>> >>> >>> >>> >>> -- >>> Lukas Renggli >>> www.lukas-renggli.ch >>> >> >> >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch >

Aug. 13, 2011

Re: [Pharo-project] PPElementParser & a small PetitTests contribution

by Damien Pollet

On 13 August 2011 15:06, Lukas Renggli <renggli(a)gmail.com> wrote: > Can you give a real-world example that shows what you want to do? Do > you just want to customize the error message if elementParser fails? I want to parse arrays of strings, while also parsing each element depending on where the array parse goes, e.g: #('command' '--option' '123') With a parser defined roughly like: (PPElementParser on: (#word asParser plus token end)) , (PPElementParser on: ('--' asParser , #word asParser plus token end ==> [:nodes | Option named: nodes second]) , (PPElementParser on: (#digit asParser plus token end ==> [:token | token value asNumber]) -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Aug. 13, 2011

Re: [Pharo-project] [Vm-dev] building Cog on 64 bits debian

by laurent laffont

On Sat, Aug 13, 2011 at 11:57 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > Nicolas Passerini commited a '-m32' flag to the CogUnixConfiguration in > order to be able to compile it on a 64bits machine. > Can you check it is still there? maybe it only was added to the VM and not > to plugins. > Seems to be here: CogUnixConfig>>commonCompilerFlags ... ^ ' -DLSB_FIRST=1 -DUSE_GLOBAL_STRUCT=0 -DCOGMTVM=0 -m32' and build# cat vm-display-null/CMakeLists.txt |grep m32 add_definitions( -DLSB_FIRST=1 -DUSE_GLOBAL_STRUCT=0 -DCOGMTVM=0 -m32 -g0 -O2 -msse2 -D_GNU_SOURCE -DNDEBUG -DITIMER_HEARTBEAT=1 Laurent. > > On Sat, Aug 13, 2011 at 11:13 AM, laurent laffont < > laurent.laffont(a)gmail.com> wrote: > >> >> Hi >> >> I try to build a 32bits Cog on Debian 64 bits. I do: >> >> apt-get install libsm-dev libasound2-dev libgl1-mesa-dev cmake g++ >> libc6-dev-i386 >> >> git clone --depth 1 git:// >> gitorious.org/~laurentlaffont/cogvm/smallharbour.git<http://gitorious.org/%7Elaurentlaffont/cogvm/smallharbour.git>shvm >> cd shvm/codegen-scripts/ >> export SQUEAKVM=/usr/local/bin/coglinux/squeak >> sh ./buildImage.sh -headless >> sh ./generate.sh -headless CogUnixConfig >> cd ../build/ >> sh ../codegen-scripts/extract-commit-info.sh >> cmake . >> make >> >> >> I have the error: >> >> [ 94%] Built target CogVM >> Linking C shared library /root/securedvm/results/vm-display-null >> /usr/bin/ld: i386 architecture of input file >> `CMakeFiles/vm-display-null.dir/root/securedvm/platforms/unix/vm-display-null/sqUnixDisplayNull.c.o' >> is incompatible with i386:x86-64 output >> >> Any idea ? >> >> >> >> Laurent Laffont - @lolgzs <http://twitter.com/#%21/lolgzs> >> >> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ >> Blog: http://magaloma.blogspot.com/ >> Developer group: http://cara74.seasidehosting.st >> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > >

Aug. 13, 2011

Re: [Pharo-project] PPElementParser & a small PetitTests contribution

by Lukas Renggli

On 13 August 2011 14:56, Damien Pollet <damien.pollet(a)gmail.com> wrote: > On 13 August 2011 09:05, Lukas Renggli <renggli(a)gmail.com> wrote: >> I don't really see the point of PPElementParser? Why don't you just use >> >> Â Â aParser answer: anObject > > something like this ? > this temp feels strangeâ¦ > > PPPredicateObjectParser class >> > matching: elementParser message: aString > Â Â Â Â | result | > Â Â Â Â ^ (self > Â Â Â Â Â Â Â Â Â Â Â Â on: [ :each | > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â result := elementParser parse: each. > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â result isPetitFailure not ] > Â Â Â Â Â Â Â Â Â Â Â Â message: aString) > Â Â Â Â Â Â Â Â answer: result No. Wrapping a parser into a PPPredicateObjectParser really doesn't make sense. Can you give a real-world example that shows what you want to do? Do you just want to customize the error message if elementParser fails? Lukas -- Lukas Renggli www.lukas-renggli.ch

Aug. 13, 2011