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

Re: [Pharo-project] Pharo/Seaside Experience Report

by Francois Stephany

Thanks Torsten :) Someone shared the post on reddit. People are intrigued by Smalltalk but it seems that it is hard to do the first step, the GUI seems to be too alien for many programmers... http://www.reddit.com/r/programming/comments/jfza8/pharo_smalltalk_experien… On 12/08/11 12:08, Torsten Bergmann wrote: > Nice post on using Pharo/Seaside: > > http://articles.tulipemoutarde.be/pharo-smalltalk-experience-report-part-i

Aug. 13, 2011

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

by Damien Pollet

On 13 August 2011 09:05, Lukas Renggli <renggli(a)gmail.com> wrote: > Ohh ohhh, that was a bit too fast: So what's the procedure in this situation ? Should I commit my patched PetitParser package to Coral's repo until it gets accepted? How will metacello deal with that? I have to update my config in the meantime? Should I package PPElementParser in one of Coral's packages and let you copy it later? But this is a recipe for getting load conflicts, isn't it? -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Aug. 13, 2011

Re: [Pharo-project] is there a way I can see the PharoDebug of a hudson job?

by Bernardo Ezequiel Contreras

or you can configure the job to archive those files as another artifact (for instance, "log-files.zip") and then download it from hudson. (without accessing the hudson server). On Sat, Aug 13, 2011 at 9:49 AM, Lukas Renggli <renggli(a)gmail.com> wrote: > builder.sh writes "PharoDebug.log" and since recently also "crash.dmp" > to the error console, so that Jenkins displays them in the build log. > Also you can find all build-artifacts (such as PharoDebug.log and > crash.dmp) in the workspace. > > Lukas > > On 13 August 2011 14:30, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > because a test is red and I don't have enough information with the small > > stack show in Hudson. > > > > THanks > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > > > > > > -- > Lukas Renggli > www.lukas-renggli.ch > >

Aug. 13, 2011

Re: [Pharo-project] is there a way I can see the PharoDebug of a hudson job?

by Mariano Martinez Peck

Thanks Lukas. I cannot see this in the Jenkis server of Pharo. I guess we are using an "old" builder.sh or whatever scsript ?? On Sat, Aug 13, 2011 at 2:49 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > builder.sh writes "PharoDebug.log" and since recently also "crash.dmp" > to the error console, so that Jenkins displays them in the build log. > Also you can find all build-artifacts (such as PharoDebug.log and > crash.dmp) in the workspace. > > Lukas > > On 13 August 2011 14:30, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > because a test is red and I don't have enough information with the small > > stack show in Hudson. > > > > THanks > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > > > > > > -- > Lukas Renggli > www.lukas-renggli.ch > > -- Mariano http://marianopeck.wordpress.com

Aug. 13, 2011

Re: [Pharo-project] formatting style

by Nicolas Cellier

2011/8/13 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > 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. > The thing that upsets me most is auto-formatting of literals. 1) the formatter SHALL try to preserve the indenting of array literals A 256 elements table organised in a 16x16 fashion can be legible. A rough 256 element suit is not. 2) the formatter SHALL preserve the base used to specify a number literal If i write 2r1011 it's clearly not my intention to read 11. It's the same for number composing a literal array/byte array In other words, the literals shall better be left unchanged. The second thing that is annoying is that it can become hard to compare code and track evolutions. But this one is just a question of having the right tool to perform the comparison... I always thought that MC, change list and friends should propose an option that simply compares scanned tokens and optionnally ignore comments. Nicolas > >> 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 16:23, Lukas Renggli <renggli(a)gmail.com> wrote: > 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? I now realize that this should more or less work: #any asParser ==> [:node | elementParser parse: node] But in case of error it would return the inner petitfailure rather than a proper one about the position in the outer streamâ¦ -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Aug. 13, 2011

Re: [Pharo-project] #name

by Alexander LazareviÄ

2011/8/13 Lukas Renggli <renggli(a)gmail.com> > Just for fun, try implementing #name on the class-side. Your image is > pretty much hosed :-) > I guess that depends on what that name method does return, no? If it's a String or Symbol it looks funny, but the image doesn't seem to be hosed. :) Alex

Aug. 13, 2011

Re: [Pharo-project] #name

by StÃ©phane Ducasse

On Aug 13, 2011, at 4:39 PM, Lukas Renggli wrote: > Just for fun, try implementing #name on the class-side. Your image is > pretty much hosed :-) Yes this was what I was thinking. Stef

Aug. 13, 2011

Re: [Pharo-project] #name

by Lukas Renggli

Just for fun, try implementing #name on the class-side. Your image is pretty much hosed :-) Lukas On 13 August 2011 15:43, Max Leske <maxleske(a)gmail.com> wrote: > 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. >>> >> > > > -- Lukas Renggli www.lukas-renggli.ch

Aug. 13, 2011

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

by Levente Uzonyi

On Sat, 13 Aug 2011, laurent laffont wrote: (no quotes thx to gmail...) This issue was discussed several times. The simplest solution is to define CC as "gcc -m32" (and optionally CXX as "g++ -m32" if you need g++). Another solution is to check how cmake supports cross compilation. IIRC autotools has some flags for this. Levente

Aug. 13, 2011