February 2019 - Pharo-users

Iliad on Pharo 7.0

by Siemen Baader

Hi, is anyone planning to port Iliad to Pharo 7.0? The Grease package seams to have been removed from 7.0 so Iliad does not work out of the box. cheers, Siemen

Feb. 5, 2019

Re: [Pharo-users] Non-greedy RegEx?

by Pierce Ng

On Wed, Feb 06, 2019 at 12:26:00AM +1300, Richard O'Keefe wrote: > Please DON'T move to PCRE. > "Outside world standards"? There are so many. > There are two important things to know about > PCRE: (1) it is a popular open source regexp > library for Perl-style regexps, (2) because of > that, it is prone to truly horrendous performance > problems. There are alternatives, such as re2, > https://github.com/google/re2 , > which are not subject to PCRE's intrinsic > performance pathologies. As it happens, re2 > supports *? +? and ??. Can you share some examples of PCRE's bad performance? Pierce

Feb. 5, 2019

Re: [Pharo-users] Github pharo-* organizations

by Pierce Ng

On Tue, Feb 05, 2019 at 12:52:37AM -0300, HernÃ¡n Morales Durand wrote: > I am currently writing a command-line tool which queries pharo repositories > using the GitHub API, and based on the repository tag. Maybe not exactly > what you asked for but it's a start. You can find the tool at: > https://github.com/hernanmd/pi Looks interesting. Thanks. Pierce

Feb. 5, 2019

Re: [Pharo-users] SQLite3 [UDBC2] - "Could not coerce arguments" error for UTF8 chars

by Pierce Ng

On Tue, Feb 05, 2019 at 02:51:42PM +0000, Petr Fischer via Pharo-users wrote: > When I executing this insert SQL command: > insert into "TABLE" (..., "VARCHAR_FIELD") values (..., 'ÄÅ¡ÄÅÅ¾Ã½Ã¡ÃÃ©ÃºÅ¯ÄÅ ÄÅÅ½ÃÃÃÃÃÅ®'); > this UDBC error occurs (what's wrong?): > Error: "Could not coerce arguments" Please show complete code. Below code completes without error. | db | db := UDBCSQLite3Connection openOn: '/tmp/u.db'. [ db basicExecute: 'create table x (xv varchar)'. db execute: 'insert into x values (?)' with: (Array with: 'ÄÅ¡ÄÅÅ¾Ã½Ã¡ÃÃ©ÃºÅ¯ÄÅ ÄÅÅ½ÃÃÃÃÃÅ®'). ] ensure: [ db close ] Below checks the database outside Pharo. % sqlite3 /tmp/u.db SQLite version 3.26.0 2018-12-01 12:34:55 Enter ".help" for usage hints. sqlite> .tables x sqlite> .schema x CREATE TABLE x (xv varchar); sqlite> .header on sqlite> select xv from x; xv ÄÅ¡ÄÅÅ¾Ã½Ã¡ÃÃ©ÃºÅ¯ÄÅ ÄÅÅ½ÃÃÃÃÃÅ® sqlite>

Feb. 5, 2019

Re: [Pharo-users] Non-greedy RegEx?

by Sven Van Caekenberghe

Still, there are advantages to an in-image solution, can't says this enough, these external lib dependencies pose their own problems ... > On 5 Feb 2019, at 08:33, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > Yes, Pharo regex implementation is very naive. > We will be moving to a PCRE binding to match outside world standards but we have not had the time to work on it :( > > Esteban > >> On 5 Feb 2019, at 00:27, Manuel Leuenberger <leuenberger(a)inf.unibe.ch> wrote: >> >> Hi, >> >> I just noticed that the Pharo regexes do not understand non-greedy matches. A regex engine to be PCRE is kind of essential, not having '.*?' to be a parseable and working regex is a bummer. Are there any more powerful regex engines around for Pharo? I could not find any. >> >> Cheers, >> Manuel >> >> > >

Feb. 5, 2019

Re: [Pharo-users] Non-greedy RegEx?

by Denis Kudriashov

We can also update pharo version from original VW repositoriy if the current license is appropriate. I think it covers missing parts. 5 ÑÐµÐ²Ñ. 2019 Ð³. 7:34 Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°ÑÐµÐ»Ñ "Esteban Lorenzano" <estebanlm(a)gmail.com> Ð½Ð°Ð¿Ð¸ÑÐ°Ð»: Hi, Yes, Pharo regex implementation is very naive. We will be moving to a PCRE binding to match outside world standards but we have not had the time to work on it :( Esteban > On 5 Feb 2019, at 00:27, Manuel Leuenberger <leuenberger(a)inf.unibe.ch> wrote: > > Hi, > > I just noticed that the Pharo regexes do not understand non-greedy matches. A regex engine to be PCRE is kind of essential, not having '.*?' to be a parseable and working regex is a bummer. Are there any more powerful regex engines around for Pharo? I could not find any. > > Cheers, > Manuel > >

Feb. 5, 2019

SQLite3 [UDBC2] - "Could not coerce arguments" error for UTF8 chars

by Petr Fischer

Hello, there is a little mess in SQLite 3 drivers for Pharo, so I am using Pharo 7 and newest UDBC2 sqlite driver from here: http://smalltalkhub.com/#!/~TorstenBergmann/UDBC2 When I executing this insert SQL command: insert into "TABLE" (..., "VARCHAR_FIELD") values (..., 'ÄÅ¡ÄÅÅ¾Ã½Ã¡ÃÃ©ÃºÅ¯ÄÅ ÄÅÅ½ÃÃÃÃÃÅ®'); this UDBC error occurs (what's wrong?): Error: "Could not coerce arguments" Stack: ExternalLibraryFunction(Object)>>error: ExternalLibraryFunction(Object)>>externalCallFailed ExternalLibraryFunction(ExternalFunction)>>invokeWithArguments: UDBCSQLite3Library>>apiPrepare:withSQLText:with:with:with: UDBCSQLite3Library>>prepare:on:with: UDBCSQLite3Connection(UDBCSQLite3BaseConnection)>>prepare: UDBCSQLite3ResultSet>>prepareStatement: UDBCSQLite3ResultSet>>execute:withCollection: UDBCSQLite3ResultSet>>execute:with:on: UDBCSQLite3Connection>>execute:with: UDBCSQLite3Connection>>execute: ... Thanks, pf

Feb. 5, 2019

Re: [Pharo-users] Non-greedy RegEx?

by Manuel Leuenberger

I am not advocating for PCRE in particular, I just need a regex engine that is just as powerful. I guess re2 serves that purpose, although I haven't used it myself (knowingly). Looking at https://github.com/google/re2/wiki/WhyRE2 <https://github.com/google/re2/wiki/WhyRE2>, re2 actually seems to be a good target. "match time is linear in the length of the input string", sounds like a really nice property. > On 5 Feb 2019, at 12:26, Richard O'Keefe <raoknz(a)gmail.com> wrote: > > Please DON'T move to PCRE. > "Outside world standards"? There are so many. > There are two important things to know about > PCRE: (1) it is a popular open source regexp > library for Perl-style regexps, (2) because of > that, it is prone to truly horrendous performance > problems. There are alternatives, such as re2, > https://github.com/google/re2 <https://github.com/google/re2> , > which are not subject to PCRE's intrinsic > performance pathologies. As it happens, re2 > supports *? +? and ??. > > On Tue, 5 Feb 2019 at 20:34, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > Hi, > > Yes, Pharo regex implementation is very naive. > We will be moving to a PCRE binding to match outside world standards but we have not had the time to work on it :( > > Esteban > > > On 5 Feb 2019, at 00:27, Manuel Leuenberger <leuenberger(a)inf.unibe.ch <mailto:leuenberger@inf.unibe.ch>> wrote: > > > > Hi, > > > > I just noticed that the Pharo regexes do not understand non-greedy matches. A regex engine to be PCRE is kind of essential, not having '.*?' to be a parseable and working regex is a bummer. Are there any more powerful regex engines around for Pharo? I could not find any. > > > > Cheers, > > Manuel > > > > > >

Feb. 5, 2019

Pharo Launcher and Command Line

by sergio ruiz

Hey, all. I REALLY dig the pharo launcher! this is a great addition. One quick question. How do i go about running a method from the command line? Specifically, I usually run something like: ./pharo Pharo.image ../scripts/setup-client-application.st To set up a new image with the current project. I am not sure which executable to run with this that will execute the same executable as pharo launcher. Thanks! ---- peace, sergio photographer, journalist, visionary Public Key: http://bit.ly/29z9fG0 #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.codeandmusic.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Feb. 5, 2019

Re: [Pharo-users] Github pharo-* organizations

by Esteban Lorenzano

> On 5 Feb 2019, at 13:55, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > >> On 5 Feb 2019, at 13:49, Ben Coman <btc(a)openinworld.com> wrote: >> >>> On 5 Feb 2019, at 02:42, Pierce Ng <pierce(a)samadhiweb.com> wrote: >>> >>> Hi all, >>> >>> Is there a definitive list of all the pharo-* organizations on GH? Like >>> pharo-rdbms, pharo-nosql, pharo-vcs, ... Or, a way to query GH to find out? >>> >>> Pierce >> >> On Tue, 5 Feb 2019 at 15:52, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> Hi, >> >> Naming the teams âpharo-somethingâ was kind of my idea to improve visibility of pharo. This has been followed by others which means we do not know all organisations nor all pharo contributions are made under a pharo-something team (in fact the less of them). >> >> We have in our TODO a new version of the catalog that will be âGitHub basedâ to group all projects. >> >> That would be very cool. Could that be something like a STON file people can text edit directly on github? >> Then for simple testing, could have a CI job that tests the new entries by diffing against the previous commit, >> to confirm that the specified version exists in the specified ConfigurationOf or BaselineOf. >> >> cheers -ben > > Let's not make it (too) complex, please. Everything has to be maintained (that is why 99% of all wikis are a mess). The idea is to make it even easier than now (but so far nothing is defined). Something like (but this is JUST A DRAFT IN MY MIND): { #project : âMyCoolProjectâ, #description : âBlablablaâ, #tags: [ âaâ, âbâ, âcâ ], #versions : [ #current : â1.2.3â, #pharo7: â1.2.0â, etc. ], url: âgithub://estebanlm/MyCoolProject' } So you edit the versions to add new ones available (or user can ask for a branch like âmaster" directly, if they want). â¦ and of course, something similar for projects who still live at sthub or others. The only problem with this approach is that you need to fork the catalog to add your version, something Iâm still not convinced is the best solution (but no other way if using github). Finally, the tool in image would be the same. Esteban > > Even the old scheme (just copy the ConfigurationOf in the right repository) was not that easy to use (it required manual action to maintain). > > And can we please solve the problem that BaselineOf cannot be used as Catalog entries (or so I understood it). > >

Feb. 5, 2019