- Pharo-users - lists.pharo.org

Re: [Pharo-users] Moose: Problem in Petit Parser

by Damien Cassou

On Sat, Feb 22, 2014 at 6:00 PM, PBK Research <peter(a)pbkresearch.co.uk> wrote: > The documentation is rather sparse did you read the dedicated book chapter of Deep into Pharo? http://deepintopharo.com/ -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Feb. 24, 2014

Re: [Pharo-users] The new versionner is cool

by HernÃ¡n Morales Durand

2014-02-21 8:25 GMT-03:00 Usman Bhatti <usman.bhatti(a)gmail.com>: > Hello, > > I found Versionner very productive tool. I was able to create a new > configuration "from scratch" within a few minutes with the packages that I > wanted to put into it. Though, I couldn't commit my new config through its > interface because Komitter kept asking for a issue number but I didn't have > it. > > You want to commit a new configuration through Kommiter?

Feb. 22, 2014

Re: [Pharo-users] Moose: Problem in Petit Parser

by PBK Research

Doru Many thanks. I knew it must be something simple. I was nearly there, because I had tried 'negated' as an alternative to 'not'. You may regret the invitation in your last line. The documentation is rather sparse, so there may well be more questions. I shall always try to solve it myself first, of course. Thanks also for the speedy answer - on a Saturday afternoon too! Peter _____ From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Tudor Girba Sent: 22 February 2014 16:38 To: Any question about pharo is welcome Subject: Re: [Pharo-users] Moose: Problem in Petit Parser Hi, For Moose related questions, there exists a dedicated mailing list: http://www.moosetechnology.org/about/contact Related to your problem, "not" does consume the input. You want to use "negate", which is implemented as: PPParser>>negate "Answer a new parser consumes any input token but the receiver." ^ self not , #any asParser ==> #second Keep the questions flowing :) Cheers, Doru On Sat, Feb 22, 2014 at 5:25 PM, PBK Research <peter(a)pbkresearch.co.uk> wrote: Hello All Not sure whether this is the right forum for this question - please excuse and point me in the right direction if I'm wrong. I have been playing with Moose 4.8, downloaded last October, mainly because I am interested in PetitParser. I have been constructing fairly trivial parsers to get to understand the system. I took as an example a typical HTML tag, i.e. any text enclosed in angle brackets <>. My first attempt was: ($< asParser, $> asParser not star, $> asParser). This seemed to send the parser into a loop, except in the case where there was no text between the brackets. Floundering around, I tried: ($< asParser, (PPPredicateObjectParser anyExceptAnyOf: '>') star, $> asParser). This worked as expected, but I was not happy with the apparent clumsiness of the middle term. So I tried: ($< asParser, (PPPredicateObjectParser char: $>) not star, $> asParser). This again sent the parser into a loop. It looks as though I have some fundamental misunderstanding of the function of 'not' in a parser, or else it is not working as specified. Could someone kindly explain to an inquisitive idiot what is going wrong? Many thanks in advance Peter Kenny -- www.tudorgirba.com "Every thing has its own flow"

Feb. 22, 2014

Re: [Pharo-users] Moose: Problem in Petit Parser

by Tudor Girba

Hi, For Moose related questions, there exists a dedicated mailing list: http://www.moosetechnology.org/about/contact Related to your problem, "not" does consume the input. You want to use "negate", which is implemented as: PPParser>>negate "Answer a new parser consumes any input token but the receiver." ^ self not , #any asParser ==> #second Keep the questions flowing :) Cheers, Doru On Sat, Feb 22, 2014 at 5:25 PM, PBK Research <peter(a)pbkresearch.co.uk>wrote: > Hello All > > Not sure whether this is the right forum for this question - please excuse > and point me in the right direction if I'm wrong. > > I have been playing with Moose 4.8, downloaded last October, mainly > because I am interested in PetitParser. I have been constructing fairly > trivial parsers to get to understand the system. I took as an example a > typical HTML tag, i.e. any text enclosed in angle brackets <>. My first > attempt was: > > ($< asParser, $> asParser not star, $> asParser). > > This seemed to send the parser into a loop, except in the case where there > was no text between the brackets. Floundering around, I tried: > > ($< asParser, (PPPredicateObjectParser anyExceptAnyOf: '>') star, $> > asParser). > > This worked as expected, but I was not happy with the apparent clumsiness > of the middle term. So I tried: > > ($< asParser, (PPPredicateObjectParser char: $>) not star, $> asParser). > > This again sent the parser into a loop. > > It looks as though I have some fundamental misunderstanding of the > function of 'not' in a parser, or else it is not working as specified. > Could someone kindly explain to an inquisitive idiot what is going wrong? > > Many thanks in advance > > Peter Kenny > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 22, 2014

Moose: Problem in Petit Parser

by PBK Research

Hello All Not sure whether this is the right forum for this question - please excuse and point me in the right direction if I'm wrong. I have been playing with Moose 4.8, downloaded last October, mainly because I am interested in PetitParser. I have been constructing fairly trivial parsers to get to understand the system. I took as an example a typical HTML tag, i.e. any text enclosed in angle brackets <>. My first attempt was: ($< asParser, $> asParser not star, $> asParser). This seemed to send the parser into a loop, except in the case where there was no text between the brackets. Floundering around, I tried: ($< asParser, (PPPredicateObjectParser anyExceptAnyOf: '>') star, $> asParser). This worked as expected, but I was not happy with the apparent clumsiness of the middle term. So I tried: ($< asParser, (PPPredicateObjectParser char: $>) not star, $> asParser). This again sent the parser into a loop. It looks as though I have some fundamental misunderstanding of the function of 'not' in a parser, or else it is not working as specified. Could someone kindly explain to an inquisitive idiot what is going wrong? Many thanks in advance Peter Kenny

Feb. 22, 2014

Re: [Pharo-users] Dowser edges

by rosariosm

Ok Hernan, that helps! I will check later. Regards, Rosario -- View this message in context: http://forum.world.st/Dowser-edges-tp4744705p4745492.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 21, 2014

Re: [Pharo-users] neo json and valueSchema for integer attributes ...

by Sven Van Caekenberghe

Hi Marten, There is indeed something currently not completely implemented: #valueSchema: and #nextAs: were added afterwards for reading (for example a collection of Points), the use of this concept for writing is simply not there. (compare NeoJSONPropertyMapping>>#readObject:from: to NeoJSONPropertyMapping>>#writeObject:on:) I will think about this a bit first. On the other hand, I am not so sure your solution is good, because you cannot write a generic #AsString for reading (going from String to ?). So I would suggest one of the other solutions mentioned in this thread. Thanks for the feedback. Sven On 21 Feb 2014, at 13:56, itlists(a)schrievkrom.de wrote: > Hmm, I think that something is definitly missing here. > > The same code but instead of using #AsString I use DateAndTime and it > works as expected - and that's what I would expect: use for that > property mapping a valueSchema named "AsString". > > It seems to work for all classes, when there is no predefined encoding > available in the running system:Integer has a mathod, DateAndTime not. > > Is there any reason why is works that way ? > > Marten > > > > > > Am 21.02.2014 12:07, schrieb Sven Van Caekenberghe: >> >> On 21 Feb 2014, at 09:18, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> Am 21.02.2014 um 07:50 schrieb itlists(a)schrievkrom.de: >>> >>>> I have a class with an instance attribute "x" and this one contains an >>>> integer value. >>>> >>>> No when exporting this to json I want to write a string instead of this >>>> number to the json string ... >>>> >>>> neoJsonMapping: mapper >>>> mapper for: self do: [ :mapping | >>>> (mapping mapInstVar: #x to: 'x') valueSchema: #AsString. >>>> ]. >>>> >>>> mapper for: #AsString customDo: [ :mapping | >>>> mapping encoder: [ :anInteger | x asString ]. >>>> mapping decoder: [ :aString | ... ] ]. >>>> >>>> But whatever I do ... only numbers are written out ... and yes of course >>>> I could add additional accessors doing the conversion. >>> > > > -- > Marten Feldtmann

Feb. 21, 2014

Re: [Pharo-users] Contact for pharo association?

by Esteban Lorenzano

ah, yesâ¦ forget to answer. but you can talk to me or Luc :) anywayâ¦ I need to improve that info in the association page. Esteban On 20 Feb 2014, at 20:12, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > Hi all, > > whom do I need to mail for questions regarding the pharo association and billing? The association web site has no contact information (or at least I cannot find it). > > Also, I think it would be good to add contact information to the association web site. (Or make it more prominent.) > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD lab - Computer Science Department (DCC) - University of Chile > >

Feb. 21, 2014

Re: [Pharo-users] neo json and valueSchema for integer attributes ...

by itlists＠schrievkrom.de

Hmm, I think that something is definitly missing here. The same code but instead of using #AsString I use DateAndTime and it works as expected - and that's what I would expect: use for that property mapping a valueSchema named "AsString". It seems to work for all classes, when there is no predefined encoding available in the running system:Integer has a mathod, DateAndTime not. Is there any reason why is works that way ? Marten Am 21.02.2014 12:07, schrieb Sven Van Caekenberghe: > > On 21 Feb 2014, at 09:18, Norbert Hartl <norbert(a)hartl.name> wrote: > >> Am 21.02.2014 um 07:50 schrieb itlists(a)schrievkrom.de: >> >>> I have a class with an instance attribute "x" and this one contains an >>> integer value. >>> >>> No when exporting this to json I want to write a string instead of this >>> number to the json string ... >>> >>> neoJsonMapping: mapper >>> mapper for: self do: [ :mapping | >>> (mapping mapInstVar: #x to: 'x') valueSchema: #AsString. >>> ]. >>> >>> mapper for: #AsString customDo: [ :mapping | >>> mapping encoder: [ :anInteger | x asString ]. >>> mapping decoder: [ :aString | ... ] ]. >>> >>> But whatever I do ... only numbers are written out ... and yes of course >>> I could add additional accessors doing the conversion. >> -- Marten Feldtmann

Feb. 21, 2014

The new versionner is cool

by Usman Bhatti

Hello, I found Versionner very productive tool. I was able to create a new configuration "from scratch" within a few minutes with the packages that I wanted to put into it. Though, I couldn't commit my new config through its interface because Komitter kept asking for a issue number but I didn't have it. So, it is excellent to have such a tool in Pharo. Great work guys. regards, Usman

Feb. 21, 2014