- Pharo-dev - lists.pharo.org

Re: [Pharo-project] #name

by StÃ©phane Ducasse

Do you really get that ? :) Stef On Aug 13, 2011, at 5:15 PM, Alexander LazareviÄ wrote: > 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 > <bullfrog.png>

Aug. 13, 2011

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

by Lukas Renggli

On 13 August 2011 18:43, Damien Pollet <damien.pollet(a)gmail.com> wrote: > On 13 August 2011 18:29, Lukas Renggli <renggli(a)gmail.com> wrote: >>> 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? >> >> Did you patch PetitParser? AFAIK you didn't change anything, you just >> added a class and a few extension methods. > > I modified the package == patched it == new PetitParser-DamienPollet.XXX.mcz > > Question is, how/where do I commit so you can review/accept code into > petitparser, but coral continues to load and work, and we don't get > too many surprises when you decide to accept the new functionality. Packaging separately seems to be the way to go. -- Lukas Renggli www.lukas-renggli.ch

Aug. 13, 2011

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

by Lukas Renggli

On 13 August 2011 18:41, Damien Pollet <damien.pollet(a)gmail.com> wrote: > On 13 August 2011 18:27, Lukas Renggli <renggli(a)gmail.com> wrote: >> This is kind of ambiguous of how to report such nested errors. I >> wonder if you couldn't avoid all the troubles if you just used a flat >> string, instead of a preprocessed one? > > ARGV is not a flat string, and I can't join it with spaces since I > can't reproduce how the shell split it in the first place. What about a special sentinel like Character value: 0? Lukas -- Lukas Renggli www.lukas-renggli.ch

Aug. 13, 2011

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

by Damien Pollet

On 13 August 2011 18:29, Lukas Renggli <renggli(a)gmail.com> wrote: >> 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? > > Did you patch PetitParser? AFAIK you didn't change anything, you just > added a class and a few extension methods. I modified the package == patched it == new PetitParser-DamienPollet.XXX.mcz Question is, how/where do I commit so you can review/accept code into petitparser, but coral continues to load and work, and we don't get too many surprises when you decide to accept the new functionality. -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Aug. 13, 2011

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

by Damien Pollet

On 13 August 2011 18:27, Lukas Renggli <renggli(a)gmail.com> wrote: > This is kind of ambiguous of how to report such nested errors. I > wonder if you couldn't avoid all the troubles if you just used a flat > string, instead of a preprocessed one? ARGV is not a flat string, and I can't join it with spaces since I can't reproduce how the shell split it in the first place. -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Aug. 13, 2011

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

by Lukas Renggli

> 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? Did you patch PetitParser? AFAIK you didn't change anything, you just added a class and a few extension methods. Lukas -- Lukas Renggli www.lukas-renggli.ch

Aug. 13, 2011

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

by Lukas Renggli

On 13 August 2011 17:28, Damien Pollet <damien.pollet(a)gmail.com> wrote: > 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â¦ This is kind of ambiguous of how to report such nested errors. I wonder if you couldn't avoid all the troubles if you just used a flat string, instead of a preprocessed one? Lukas -- Lukas Renggli www.lukas-renggli.ch

Aug. 13, 2011

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