January 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Tools for easy subtext extraction from text

by Dimitris Chloupis

Dtto as above. Readability was never a question. And if it was, then you > just doubled the regex complexity, and made the code more confusing by > turning the problem upside down, due to the limited API. Complaining about the compact syntax makes as much sense as complaining > that `1+2` is too cryptic and should be written as `1 digitAdd: 2` (which > you can do btw); the point of compactness is that when you know what you > are doing you can save some time. > > Typing speed is pretty much the 1000th reason for a slow down, 1th is the ability to understand code, at least for me. Ruby is a more flexible and better designed language, but I would pick python any day over it which by the way beats even Pharo in readability because of its culture on how to write APIs. On the subject of your issue, this is no work around I offered, this is standard regex syntax. Exclusion and combination of matches. Nothing special. I am using regex to parse python code, in pharo, for me at least Pharo regex API rocks.

Jan. 21, 2017

Re: [Pharo-users] super super

by Hilaire

Worst than that :) In theory I can refactor the super code and commit, but SmalltalkHub does not let me commit even I have RW access... So I have to knock at the Philippe's or Masashi's door so they can commit it for me. It's annoying to bother busy people. Anyway enough small talk ;) Le 21/01/2017 Ã 19:17, Peter Uhnak a Ã©crit : > Out of curiosity, wouldn't it be better to temporarily duplicate the code in your class and talk with the upstream owner? (That would be my usual approach.) -- Dr. Geo http://drgeo.eu

Jan. 21, 2017

Xtreams docs (previously: Tools for easy subtext extraction from text)

by Peter Uhnak

Ah, I now see my googing issue, because apparently noone knows whether the name is Xtreams or Xstreams If I google 'Pharo Xtreams' (which is the correct name it seems) I get fuckall, but if I google 'Pharo Xstreams' I get the link as second result, just because someone misspelled the filename. -_- Is there a build for the PharoLimbo, or do I have to compile it myself? Peter On Sat, Jan 21, 2017 at 09:06:34PM +0100, phil(a)highoctane.be wrote: > There is also this > > https://github.com/SquareBracketAssociates/PharoLimbo/tree/master/Xtreams > > > > On Sat, Jan 21, 2017 at 3:08 PM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > > On Sat, Jan 21, 2017 at 02:01:59PM +0100, Denis Kudriashov wrote: > > > Hi. > > > > > > 2017-01-20 16:15 GMT+01:00 Peter Uhnak <i.uhnak(a)gmail.com>: > > > > > > > In Ruby it is dead simple: > > > > str[/\[(.*)\]/,1].hex # "=> 37" > > > > > > > > > > I always wondering when people think it is dead simple. > > > I use streams for such cases. It is logical, readable and dead simple > > > > I've never mentioned readability, because the code is throwaway. > > I guess if you are not using regexes it could look odd, but as a linux > > user it is very casual; if I had to extract the information I would just > > pipe it through sed or grep. > > > > I wouldn't use such thing in code that I want to keep, but I explicitly > > mentioned that. > > > > > > > approach without crappy syntax. And with Xtreams library it become much > > > more easy and fun > > > > Are there any docs for Xtreams? I found several repositories, but none > > explain what Xtreams even is. > > > > --- > > > > > > > >> In Ruby it is dead simple: > > >> > > > > > > and dead unreadable > > > > > > Pharo way is both dead simple and dead readable > > > > Dtto as above. Readability was never a question. And if it was, then you > > just doubled the regex complexity, and made the code more confusing by > > turning the problem upside down, due to the limited API. > > > > Complaining about the compact syntax makes as much sense as complaining > > that `1+2` is too cryptic and should be written as `1 digitAdd: 2` (which > > you can do btw); the point of compactness is that when you know what you > > are doing you can save some time. > > > > You can always write .match() instead of []; e.g. in python: > > > > int(re.split('\[(.*)\]', str)[1], 16) > > int(re.search('\[(.*)\]', str).group(1), 16) > > > > But my point was not addressing this particular problem, but the general > > problem --- I often find it much easier to preprocess data with standard > > linux tools and then feed it to Pharo then to try to do the same in Pharo > > itself. > > > > Peter > > > > > >

Jan. 21, 2017

Re: [Pharo-users] singleton trait

by stepharong

Yes I like your blog entry. But my point is orthogonal :) > On Sat, Jan 21, 2017 at 11:19:24AM +0100, stepharong wrote: >> Pay attention that Singleton should not be about access but time. >> >> If you can by adding on instance variable avoid to need a singleton >> then it means that it was not a singleton. >> >> A singleton is often: >> you **CANNOT** have two instances at the same time. >> >> Many people do not use well singleton so watch out. > > We have several variations of singletons in the Pharo codebase, some of > which do allow multiple instances, some of which don't. But they are > differentiated by names. > > https://www.peteruhnak.com/blog/2015/12/06/singleton-variations/ > > > Peter > >> >> Stef >> >> On Thu, 19 Jan 2017 11:23:21 +0100, Siemen Baader >> <siemenbaader(a)gmail.com> wrote: >> >> >Is there a trait to quickly create singletons in Pharo, along the >> >way of the Ruby Singleton mixin? >> > >> >https://ruby-doc.org/stdlib-1.9.3/libdoc/singleton/rdoc/Singleton.html >> > >> >(and ideally also observer/observable, which I am going to need next..) >> > >> >-- Siemen >> >> >> >> -- >> Using Opera's mail client: http://www.opera.com/mail/ > -- Using Opera's mail client: http://www.opera.com/mail/

Jan. 21, 2017

Re: [Pharo-users] is PetitParser eager by default?

by stepharong

tx On Sat, 21 Jan 2017 18:09:32 +0100, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > The inspector shows the PPFailure, and the Debug View presentation of > PPFailure shows you the paths the parser tried. > > star produces a PPPossessiveRepeatingParser, and selecting it shows that > it matched all three characters: they are selected in the bottom pane > which shows the input string. > > Cheers, > Doru > > >> On Jan 21, 2017, at 11:26 AM, stepharong <stepharong(a)free.fr> wrote: >> >> Hi doru >> >> where do we see it? >> >> >> Stef >> >> On Fri, 20 Jan 2017 16:57:51 +0100, Tudor Girba <tudor(a)tudorgirba.com> >> wrote: >> >> Hi, >> >> When you have questions like these, you can also use the built-in >> debugging facilities. For example, in your case, you can see that the >> #any parser consumed everything like this: >> >> <Mail Attachment.png> >> >> Cheers, >> Doru >> >> >>> On Jan 20, 2017, at 4:38 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>> >>>> Am 20.01.2017 um 15:24 schrieb Peter Uhnak <i.uhnak(a)gmail.com>: >>>> >>>> Is PetitParser eager by default? >>>> >>>> I've used PetitParser countless times so I am really baffled why this >>>> doesn't work >>>> >>>> str := 'a0b'. >>>> #any asParser star, #digit asParser, #any asParser star parse: str. >>>> >>>> -> PPFailure (input expected at: 3) >>>> >>> >>> PetitParser is not greedy per default. But back tracking only works if >>> a parser fails. Using , creates a sequence of combined parsers. If one >>> fails the whole sequence fails. As a star parser always succeeds it >>> would be huge luck if your rule would succeed. The probability that >>> the parser consumes exactly one character is not high. Maybe negating >>> the first sequence part is what you want >>> >>> Norbert >>> >>> >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "What we can governs what we wish." >> >> >> >> >> >> >> >> -- >> Using Opera's mail client: http://www.opera.com/mail/ > > -- > www.tudorgirba.com > www.feenk.com > > âThe smaller and more pervasive the hardware becomes, the more physical > the software gets." > -- Using Opera's mail client: http://www.opera.com/mail/

Jan. 21, 2017

Re: [Pharo-users] super super

by Hilaire

yes, something like factoring out in its own method a chunk of code in super super method I want to access from my subclass. Le 21/01/2017 Ã 19:32, Sebastian Heidbrink via Pharo-users a Ã©crit : > Now I am wondering what you guys are meaning by "hooks"? -- Dr. Geo http://drgeo.eu

Jan. 21, 2017

Re: [Pharo-users] Tools for easy subtext extraction from text

by stepharong

Yes I should finish to convert everything. I hope that in Pharo 70 we will be able add Xtream like library and remove the old stream but this is large task. stef On Sat, 21 Jan 2017 21:06:34 +0100, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > There is also this > > https://github.com/SquareBracketAssociates/PharoLimbo/tree/master/Xtreams > > > > On Sat, Jan 21, 2017 at 3:08 PM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: >> On Sat, Jan 21, 2017 at 02:01:59PM +0100, Denis Kudriashov wrote: >>> Hi. >>> >>> 2017-01-20 16:15 GMT+01:00 Peter Uhnak <i.uhnak(a)gmail.com>: >>> >>> > In Ruby it is dead simple: >>> > str[/\[(.*)\]/,1].hex # "=> 37" >>> > >>> >>> I always wondering when people think it is dead simple. >>> I use streams for such cases. It is logical, readable and dead simple >> >> I've never mentioned readability, because the code is throwaway. >> I guess if you are not using regexes it could look odd, but as a linux >> user it is very casual; if I had to extract the information I would >> just pipe it through sed or grep. >> >> I wouldn't use such thing in code that I want to keep, but I explicitly >> mentioned that. >> >> >>> approach without crappy syntax. And with Xtreams library it become much >>> more easy and fun >> >> Are there any docs for Xtreams? I found several repositories, but none >> explain what Xtreams even is. >> >> --- >> >>> >>>> In Ruby it is dead simple: >>>> >>> >>> and dead unreadable >>> >>> Pharo way is both dead simple and dead readable >> >> Dtto as above. Readability was never a question. And if it was, then >> you just doubled the regex complexity, and made the code more confusing >> by turning the problem upside down, due to the >>limited API. >> >> Complaining about the compact syntax makes as much sense as complaining >> that `1+2` is too cryptic and should be written as `1 digitAdd: 2` >> (which you can do btw); the point of >>compactness is that when you >> know what you are doing you can save some time. >> >> You can always write .match() instead of []; e.g. in python: >> >> int(re.split('\[(.*)\]', str)[1], 16) >> int(re.search('\[(.*)\]', str).group(1), 16) >> >> But my point was not addressing this particular problem, but the >> general problem --- I often find it much easier to preprocess data with >> standard linux tools and then feed it to Pharo then to try >>to do the >> same in Pharo itself. >> >>>> Peter >> >> > -- Using Opera's mail client: http://www.opera.com/mail/

Jan. 21, 2017

Re: [Pharo-users] Tools for easy subtext extraction from text

by phil＠highoctane.be

There is also this https://github.com/SquareBracketAssociates/PharoLimbo/tree/master/Xtreams On Sat, Jan 21, 2017 at 3:08 PM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > On Sat, Jan 21, 2017 at 02:01:59PM +0100, Denis Kudriashov wrote: > > Hi. > > > > 2017-01-20 16:15 GMT+01:00 Peter Uhnak <i.uhnak(a)gmail.com>: > > > > > In Ruby it is dead simple: > > > str[/\[(.*)\]/,1].hex # "=> 37" > > > > > > > I always wondering when people think it is dead simple. > > I use streams for such cases. It is logical, readable and dead simple > > I've never mentioned readability, because the code is throwaway. > I guess if you are not using regexes it could look odd, but as a linux > user it is very casual; if I had to extract the information I would just > pipe it through sed or grep. > > I wouldn't use such thing in code that I want to keep, but I explicitly > mentioned that. > > > > approach without crappy syntax. And with Xtreams library it become much > > more easy and fun > > Are there any docs for Xtreams? I found several repositories, but none > explain what Xtreams even is. > > --- > > > > >> In Ruby it is dead simple: > >> > > > > and dead unreadable > > > > Pharo way is both dead simple and dead readable > > Dtto as above. Readability was never a question. And if it was, then you > just doubled the regex complexity, and made the code more confusing by > turning the problem upside down, due to the limited API. > > Complaining about the compact syntax makes as much sense as complaining > that `1+2` is too cryptic and should be written as `1 digitAdd: 2` (which > you can do btw); the point of compactness is that when you know what you > are doing you can save some time. > > You can always write .match() instead of []; e.g. in python: > > int(re.split('\[(.*)\]', str)[1], 16) > int(re.search('\[(.*)\]', str).group(1), 16) > > But my point was not addressing this particular problem, but the general > problem --- I often find it much easier to preprocess data with standard > linux tools and then feed it to Pharo then to try to do the same in Pharo > itself. > > Peter > > >

Jan. 21, 2017

Re: [Pharo-users] Tools for easy subtext extraction from text

by phil＠highoctane.be

Actually the things I snatched are from there. Phil On Sat, Jan 21, 2017 at 7:19 PM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > On Sat, Jan 21, 2017 at 07:09:19PM +0100, Denis Kudriashov wrote: > > 2017-01-21 17:09 GMT+01:00 phil(a)highoctane.be <phil(a)highoctane.be>: > > > > > I collected some content about that and wanted to do something about it > > > but, yeah, it got on the backburner. > > > > > > This is currently just the extract of the package comment or something > > > like that. > > > > > > https://github.com/philippeback/xstreamsdoc > > > > > > > And look here: > > > > https://github.com/mkobetic/Xtreams > > Ah, the wiki has several pages. I just saw the welcome page and > uninformative readme. > > > https://code.google.com/archive/p/xtreams/wikis > > > Thanks! > > Peter > > >

Jan. 21, 2017

Re: [Pharo-users] super super

by Sebastian Heidbrink

Hi Hilaire, I had this once, too. No time to refactor or rethink my subclass structure. Now I am wondering what you guys are meaning by "hooks"? Something like this? A ClassExtension? SuperSuperClass - methodIWantToReach - myExtendedMethod ^self methodIWantToReach SuperClass - methodIWantToReach MyClass - methodIWantToReach ^self myExtendedMethod Thanks Sebastian Am 21.01.2017 um 09:06 schrieb Hilaire: > Yep, it is the first situation I face where I need it in 10 years of > Smalltalk/Pharo. Otherwise I will refactor super class package, may be I > should > > Le 21/01/2017 Ã¯Â¿Å 11:19, stepharong a Ã¯Â¿Åcrit : >> pay attention and to not use it. It is evil to use that in plain domain >> code.

Jan. 21, 2017