- Pharo-users - lists.pharo.org

Re: [Pharo-users] PetitParser: Parse X as long as it's not Y

by PBKResearch

Sean This seems to be what the PPAndParser is designed for. I tried the following: identifier := #letter asParser plus flatten. exclusion := ('Bar' asParser / 'Baz' asParser) negate. restricted := identifier and, exclusion. restricted matches: 'abc'. "--> true" restricted matches: 'Baz'. "--> false" (Note the comma after 'and' is necessary - this wasted me a few minutes in trying.) Hope this helps Peter Kenny -----Original Message----- From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Sean P. DeNigris Sent: 05 August 2017 21:26 To: pharo-users(a)lists.pharo.org Subject: [Pharo-users] PetitParser: Parse X as long as it's not Y How do I tell Petit Parser to parse a string of certain allowable characters as long as the final result isn't a particular string? E.g. consume an identifier as long as it's not 'Baz' or 'Bar' Thanks ----- Cheers, Sean -- View this message in context: http://forum.world.st/PetitParser-Parse-X-as-long-as-it-s-not-Y-tp4958895.ht ml Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 6, 2017

Re: [Pharo-users] Glorp: `session login` fails for Garage SQLite

by Herby VojÄÃk

Guillermo Polito wrote: > How did you install garage and glorp? Catalog, configurations? Can you > paste here the installation instructions you followed? Just adding GarageGlorp as dependency: baseline: spec <baseline> spec for: #common do: [ spec package: 'Towergame' with: [ spec requires: #('GarageGlorp' 'NeoJSON') ]; package: 'Towergame-Tests' with: [ spec requires: #('Towergame' 'Mocketry') ]; configuration: 'GarageGlorp' with: [ spec version: #stable; repository: 'http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo60/main' ]; configuration: 'NeoJSON' with: [ spec version: #stable; repository: 'http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo60/main' ]; baseline: 'Mocketry' with: [ spec repository: 'github://dionisiydk/Mocketry:v4.0.x' ]; group: 'default' with: #('Core'); group: 'development' with: #('Core' 'Tests'); group: 'Core' with: #('Towergame'); group: 'Tests' with: #('Towergame-Tests') ] and loading it in script via Metacello new baseline: 'Towergame'; repository: 'gitlocal:///', (hereRef / 'src') fullName; load: 'development'. I presume this is how it should be done? --- But, does that affect the presence of queryEncoding? It's the mythincal creature, I have browsed repos out there, history of development of Glorp and found it nowhere. Did it actually exist? :-) In fact, from what I saw, it seems Glorp accumulated its share of technical debt, drivers came and went, platforms, too, dialects on which it runs, too. It seems to me it needs serious detanglement. Get rid of ifs, structure clenly, change ifs comparing to hardcoded symbols with double dispatch, etc. :-( Herby P.S.: And most of all, add one smoke test to test it with each login type that actually uses `session login`, not database accessor's one (not seen, but it was mention in this thread or the one linked below no test actually sends `session login`). > > On Sun, Aug 6, 2017 at 1:37 AM, Herby VojÄÃk <herby(a)mailbox.sk > <mailto:herby@mailbox.sk>> wrote: > > Herby VojÄÃk wrote: > > Guillermo Polito wrote: > > AFAIR, PharoDatabaseAccessor was meant to work with > SqueakDBX/DBXTalk > driver. No other driver should use it. At the time Garage > did not even > exist. > > So I'd say that you should not use PharoDatabaseAccessor > with another > driver than the one it was originally mean to? I do not know > exactly > your setup, I was not following this thread. > > Really I cannot tell much more. This was really long time ago. > > > Great to know! > > I am not using it consciously, though. System somehow selects it and > uses it in the background (I just do MyDescriptorSystem > sessionForLogin: > myLoginObject; and before that I set GarageGlorpDrive to be the > default). > > This seems to be the actual fix (make Glorp with Garage not use > PharoDatabaseAccessor). > > > Actually, probably not. It is more in, it should be fixed to work > with Garage. It has lots of functionality there... :-( > > > > Herby > > > On Sun, Aug 6, 2017 at 12:20 AM, Herby VojÄÃk > <herby(a)mailbox.sk <mailto:herby@mailbox.sk> > <mailto:herby@mailbox.sk <mailto:herby@mailbox.sk>>> wrote: > > Esteban A. Maringolo wrote: > > Herby, > > I regularly use `session login`, but I don't use SQLite in > Pharo, but I > do in VisualWorks and it works just fine. > Maybe if there is a bug we should fix it. Even with a no-op > method. > > Regards! > > Esteban A. Maringolo > > > It's hard. The problem is > > PharoDatabaseAccessor >> encoding > ^self connection queryEncoding > > which overrides parent, which is atm: > > encoding > "The connection is specific to the dialect; some dialects > will need > to override this method." > > ^connection encoding > > The former was added at GuillermoPolito.73 back in 2011 (and the > latter was the same back then). It probably fixed something, > but I > don't see any implementors of queryEncoding atm (definitely > not in > Garage). From the diff it is clear lots of databases and drivers > have gone. Now, why was it change for Pharo (and does it > need to be > changed in 2017)? > > Ccing Guillermo Polito. > > Herby > > P.S.: I wonder how it is that no one actually had problem > with this? > This predictably fails on `session login` on pharo, unless > queryEncoding is somehow magically present without seeing it in > source code for other platforms? > > > 2017-08-05 15:52 GMT-03:00 Herby VojÄÃk <herby(a)mailbox.sk > <mailto:herby@mailbox.sk> > <mailto:herby@mailbox.sk <mailto:herby@mailbox.sk>> > <mailto:herby@mailbox.sk <mailto:herby@mailbox.sk> > <mailto:herby@mailbox.sk <mailto:herby@mailbox.sk>>>>: > > Alistair Grant wrote: > > Hi Herby, > > On 5 August 2017 at 18:09, Herby > VojÄÃk<herby(a)mailbox.sk <mailto:herby@mailbox.sk> > <mailto:herby@mailbox.sk <mailto:herby@mailbox.sk>> > <mailto:herby@mailbox.sk <mailto:herby@mailbox.sk> > <mailto:herby@mailbox.sk <mailto:herby@mailbox.sk>>>> wrote: > > Hello! > > First of all, what is preferred way to (first time) > login > into database? I > had the impression that `aDatabaseAccessor login` > is sorta > low-level, and > one should do `session login` (after all, it is > session you > get to work > with, not an accessor). > > But with Garage SQLite, `session login`, when > accessor is > not logged, always > fails with "MessageNotUnderstood: > GASqlite3Driver>>queryEncoding". > > Should one not use `session login` at all, then (when > accessor is logged, it > just does nothing, if it isn't, it connects the > accessor, > but tries to do > some additional work which always fails)? > > Herby > > > From memory this is caused by differences between > VisualWorks > and Pharo. > > Anyway, it is discussed and resolved in: > > http://forum.world.st/Glorp-SQLite3-issue-td4899792.html > <http://forum.world.st/Glorp-SQLite3-issue-td4899792.html> > <http://forum.world.st/Glorp-SQLite3-issue-td4899792.html > <http://forum.world.st/Glorp-SQLite3-issue-td4899792.html>> > <http://forum.world.st/Glorp-SQLite3-issue-td4899792.html > <http://forum.world.st/Glorp-SQLite3-issue-td4899792.html> > <http://forum.world.st/Glorp-SQLite3-issue-td4899792.html > <http://forum.world.st/Glorp-SQLite3-issue-td4899792.html>>> > > > Doesn't look like solved to me. Anyway, at least I know it > is known > for year and no-one seemed to see it as a bug. > > I think it is one (you cannot just send queryEncoding where > no class > implements it and be fine, imo). > > So what is the state of `session login`? Is it meant to be > used, or > everyone just took a step down to low-level and uses `accessor > login` instead? :-( > > > Cheers, > Alistair > > > Thanks, Herby > > > > > > > -- > > > > Guille Polito > > > Research Engineer > > French National Center for Scientific Research - > _http://www.cnrs.fr_ > > > > *Web:* _http://guillep.github.io_ > > *Phone: *+33 06 52 70 66 13 <tel:%2B33%2006%2052%2070%2066%2013> > > > > > > > > -- > > > > Guille Polito > > > Research Engineer > > French National Center for Scientific Research - _http://www.cnrs.fr_ > > > > *Web:* _http://guillep.github.io_ > > *Phone: *+33 06 52 70 66 13 >

Aug. 6, 2017

Re: [Pharo-users] Glorp: `session login` fails for Garage SQLite

by Herby VojÄÃk

Pierce Ng wrote: > On Sun, Aug 06, 2017 at 12:54:41AM +0200, Herby VojÄÃk wrote: >> Pharo is 6.1, Glorp, Garage etc. are #stable loaded from Pharo60 >> catalog (see attachment). > > You may want to try GlorpSQLite. Load from Catalog Browser into a fresh 60510 > image. All 889 tests should pass, as has been the case since Pharo 5. In > GlorpSQLite, #encoding is implemented by UDBCDatabaseDriver. But, Pierce, who cares about #encoding? It's #queryEncoding, sent from PharoDatabaseAccessor each time `session login` actually tries to do logging in (the bug was probably masked by the fact it just early returns nil if `accessor isLogged`), and missing everywhere. Besides, as I understand, Garage is the way to go, so I want to use that (it works, except for bugs, which are in PharoDatabaseAccessor, not in Garage). > Pierce Herby

Aug. 6, 2017

Re: [Pharo-users] PetitParser: Parse X as long as it's not Y

by Jan KurÅ¡

Hi, not sure if I understand your requirement, but you can try: Y not, chars star Is this what you need? Cheers Jan On Sun, Aug 6, 2017, 04:47 Sean P. DeNigris <sean(a)clipperadams.com> wrote: > vonbecmann wrote > > did you try with negate? > > That is the standard trick with PP, but the problem here is that I'm trying > to say, not just "anything which is not Y", but "any string of these > characters as long is it doesn't also match Y" > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/PetitParser-Parse-X-as-long-as-it-s-not-Y-tp4958895p4… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Aug. 6, 2017

Re: [Pharo-users] Best Practices for Bundling Documentation

by Stephane Ducasse

or MyStuff MyStuff/Tutorial On Sun, Aug 6, 2017 at 11:00 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hello evan > > Cool I want to read them! > If you have your code in github you can include pillar files there and > with travis build the pdf as I did for the booklets. > I prefer to separate tutorials from code. > > I would go for > MyStuff > MyStuffTutorial > or > > > This way readers can get the pdf > https://github.com/SquareBracketAssociates/Booklet-BuildingMemoryGameWithBl… > or > https://github.com/SquareBracketAssociates/Booklet-Mocking > > I can help you to set it up. > After you booklet can be published on the Pharo books page too. > > stef > > > On Sun, Aug 6, 2017 at 1:34 AM, Evan Donahue <emdonahu(a)gmail.com> wrote: >> Hello, >> >> The projects are a logic programming and machine learning system >> respectively, so they probably warrant more involved tutorial-style >> documentation. I will take a look at the Pillar docs, but just to think >> ahead a bit, assuming I write up some docs in Pillar, what would be the best >> way to distribute those? Can they be packaged with the code or would the >> docs be outside the image? If outside, where do people tend to host them? >> >> Thanks, >> Evan >> >> >> >> -- >> View this message in context: http://forum.world.st/Best-Practices-for-Bundling-Documentation-tp4958788p4… >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >>

Aug. 6, 2017

Re: [Pharo-users] Best Practices for Bundling Documentation

by Stephane Ducasse

Hello evan Cool I want to read them! If you have your code in github you can include pillar files there and with travis build the pdf as I did for the booklets. I prefer to separate tutorials from code. I would go for MyStuff MyStuffTutorial or This way readers can get the pdf https://github.com/SquareBracketAssociates/Booklet-BuildingMemoryGameWithBl… or https://github.com/SquareBracketAssociates/Booklet-Mocking I can help you to set it up. After you booklet can be published on the Pharo books page too. stef On Sun, Aug 6, 2017 at 1:34 AM, Evan Donahue <emdonahu(a)gmail.com> wrote: > Hello, > > The projects are a logic programming and machine learning system > respectively, so they probably warrant more involved tutorial-style > documentation. I will take a look at the Pillar docs, but just to think > ahead a bit, assuming I write up some docs in Pillar, what would be the best > way to distribute those? Can they be packaged with the code or would the > docs be outside the image? If outside, where do people tend to host them? > > Thanks, > Evan > > > > -- > View this message in context: http://forum.world.st/Best-Practices-for-Bundling-Documentation-tp4958788p4… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Aug. 6, 2017

Re: [Pharo-users] Glorp: `session login` fails for Garage SQLite

by Pierce Ng

On Sun, Aug 06, 2017 at 12:54:41AM +0200, Herby VojÄÃk wrote: > Pharo is 6.1, Glorp, Garage etc. are #stable loaded from Pharo60 > catalog (see attachment). You may want to try GlorpSQLite. Load from Catalog Browser into a fresh 60510 image. All 889 tests should pass, as has been the case since Pharo 5. In GlorpSQLite, #encoding is implemented by UDBCDatabaseDriver. Pierce

Aug. 6, 2017

Re: [Pharo-users] Glorp: `session login` fails for Garage SQLite

by Guillermo Polito

How did you install garage and glorp? Catalog, configurations? Can you paste here the installation instructions you followed? On Sun, Aug 6, 2017 at 1:37 AM, Herby VojÄÃk <herby(a)mailbox.sk> wrote: > Herby VojÄÃk wrote: > >> Guillermo Polito wrote: >> >>> AFAIR, PharoDatabaseAccessor was meant to work with SqueakDBX/DBXTalk >>> driver. No other driver should use it. At the time Garage did not even >>> exist. >>> >>> So I'd say that you should not use PharoDatabaseAccessor with another >>> driver than the one it was originally mean to? I do not know exactly >>> your setup, I was not following this thread. >>> >>> Really I cannot tell much more. This was really long time ago. >>> >> >> Great to know! >> >> I am not using it consciously, though. System somehow selects it and >> uses it in the background (I just do MyDescriptorSystem sessionForLogin: >> myLoginObject; and before that I set GarageGlorpDrive to be the default). >> >> This seems to be the actual fix (make Glorp with Garage not use >> PharoDatabaseAccessor). >> > > Actually, probably not. It is more in, it should be fixed to work with > Garage. It has lots of functionality there... :-( > > > >> Herby >> >> >>> On Sun, Aug 6, 2017 at 12:20 AM, Herby VojÄÃk <herby(a)mailbox.sk >>> <mailto:herby@mailbox.sk>> wrote: >>> >>> Esteban A. Maringolo wrote: >>> >>> Herby, >>> >>> I regularly use `session login`, but I don't use SQLite in >>> Pharo, but I >>> do in VisualWorks and it works just fine. >>> Maybe if there is a bug we should fix it. Even with a no-op method. >>> >>> Regards! >>> >>> Esteban A. Maringolo >>> >>> >>> It's hard. The problem is >>> >>> PharoDatabaseAccessor >> encoding >>> ^self connection queryEncoding >>> >>> which overrides parent, which is atm: >>> >>> encoding >>> "The connection is specific to the dialect; some dialects will need >>> to override this method." >>> >>> ^connection encoding >>> >>> The former was added at GuillermoPolito.73 back in 2011 (and the >>> latter was the same back then). It probably fixed something, but I >>> don't see any implementors of queryEncoding atm (definitely not in >>> Garage). From the diff it is clear lots of databases and drivers >>> have gone. Now, why was it change for Pharo (and does it need to be >>> changed in 2017)? >>> >>> Ccing Guillermo Polito. >>> >>> Herby >>> >>> P.S.: I wonder how it is that no one actually had problem with this? >>> This predictably fails on `session login` on pharo, unless >>> queryEncoding is somehow magically present without seeing it in >>> source code for other platforms? >>> >>> >>> 2017-08-05 15:52 GMT-03:00 Herby VojÄÃk <herby(a)mailbox.sk >>> <mailto:herby@mailbox.sk> >>> <mailto:herby@mailbox.sk <mailto:herby@mailbox.sk>>>: >>> >>> Alistair Grant wrote: >>> >>> Hi Herby, >>> >>> On 5 August 2017 at 18:09, Herby >>> VojÄÃk<herby(a)mailbox.sk <mailto:herby@mailbox.sk> >>> <mailto:herby@mailbox.sk <mailto:herby@mailbox.sk>>> wrote: >>> >>> Hello! >>> >>> First of all, what is preferred way to (first time) >>> login >>> into database? I >>> had the impression that `aDatabaseAccessor login` >>> is sorta >>> low-level, and >>> one should do `session login` (after all, it is >>> session you >>> get to work >>> with, not an accessor). >>> >>> But with Garage SQLite, `session login`, when >>> accessor is >>> not logged, always >>> fails with "MessageNotUnderstood: >>> GASqlite3Driver>>queryEncoding". >>> >>> Should one not use `session login` at all, then (when >>> accessor is logged, it >>> just does nothing, if it isn't, it connects the >>> accessor, >>> but tries to do >>> some additional work which always fails)? >>> >>> Herby >>> >>> >>> From memory this is caused by differences between >>> VisualWorks >>> and Pharo. >>> >>> Anyway, it is discussed and resolved in: >>> >>> http://forum.world.st/Glorp-SQLite3-issue-td4899792.html >>> <http://forum.world.st/Glorp-SQLite3-issue-td4899792.html> >>> <http://forum.world.st/Glorp-SQLite3-issue-td4899792.html >>> <http://forum.world.st/Glorp-SQLite3-issue-td4899792.html>> >>> >>> >>> Doesn't look like solved to me. Anyway, at least I know it >>> is known >>> for year and no-one seemed to see it as a bug. >>> >>> I think it is one (you cannot just send queryEncoding where >>> no class >>> implements it and be fine, imo). >>> >>> So what is the state of `session login`? Is it meant to be >>> used, or >>> everyone just took a step down to low-level and uses `accessor >>> login` instead? :-( >>> >>> >>> Cheers, >>> Alistair >>> >>> >>> Thanks, Herby >>> >>> >>> >>> >>> >>> >>> -- >>> >>> >>> >>> Guille Polito >>> >>> >>> Research Engineer >>> >>> French National Center for Scientific Research - _http://www.cnrs.fr_ >>> >>> >>> >>> *Web:* _http://guillep.github.io_ >>> >>> *Phone: *+33 06 52 70 66 13 >>> >>> >> >> > -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Aug. 6, 2017

Re: [Pharo-users] PetitParser: Parse X as long as it's not Y

by Sean P. DeNigris

vonbecmann wrote > did you try with negate? That is the standard trick with PP, but the problem here is that I'm trying to say, not just "anything which is not Y", but "any string of these characters as long is it doesn't also match Y" ----- Cheers, Sean -- View this message in context: http://forum.world.st/PetitParser-Parse-X-as-long-as-it-s-not-Y-tp4958895p4… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 6, 2017

Re: [Pharo-users] Glorp: `session login` fails for Garage SQLite

by Herby VojÄÃk

Herby VojÄÃk wrote: > Guillermo Polito wrote: >> AFAIR, PharoDatabaseAccessor was meant to work with SqueakDBX/DBXTalk >> driver. No other driver should use it. At the time Garage did not even >> exist. >> >> So I'd say that you should not use PharoDatabaseAccessor with another >> driver than the one it was originally mean to? I do not know exactly >> your setup, I was not following this thread. >> >> Really I cannot tell much more. This was really long time ago. > > Great to know! > > I am not using it consciously, though. System somehow selects it and > uses it in the background (I just do MyDescriptorSystem sessionForLogin: > myLoginObject; and before that I set GarageGlorpDrive to be the default). > > This seems to be the actual fix (make Glorp with Garage not use > PharoDatabaseAccessor). Actually, probably not. It is more in, it should be fixed to work with Garage. It has lots of functionality there... :-( > > Herby > >> >> On Sun, Aug 6, 2017 at 12:20 AM, Herby VojÄÃk <herby(a)mailbox.sk >> <mailto:herby@mailbox.sk>> wrote: >> >> Esteban A. Maringolo wrote: >> >> Herby, >> >> I regularly use `session login`, but I don't use SQLite in >> Pharo, but I >> do in VisualWorks and it works just fine. >> Maybe if there is a bug we should fix it. Even with a no-op method. >> >> Regards! >> >> Esteban A. Maringolo >> >> >> It's hard. The problem is >> >> PharoDatabaseAccessor >> encoding >> ^self connection queryEncoding >> >> which overrides parent, which is atm: >> >> encoding >> "The connection is specific to the dialect; some dialects will need >> to override this method." >> >> ^connection encoding >> >> The former was added at GuillermoPolito.73 back in 2011 (and the >> latter was the same back then). It probably fixed something, but I >> don't see any implementors of queryEncoding atm (definitely not in >> Garage). From the diff it is clear lots of databases and drivers >> have gone. Now, why was it change for Pharo (and does it need to be >> changed in 2017)? >> >> Ccing Guillermo Polito. >> >> Herby >> >> P.S.: I wonder how it is that no one actually had problem with this? >> This predictably fails on `session login` on pharo, unless >> queryEncoding is somehow magically present without seeing it in >> source code for other platforms? >> >> >> 2017-08-05 15:52 GMT-03:00 Herby VojÄÃk <herby(a)mailbox.sk >> <mailto:herby@mailbox.sk> >> <mailto:herby@mailbox.sk <mailto:herby@mailbox.sk>>>: >> >> Alistair Grant wrote: >> >> Hi Herby, >> >> On 5 August 2017 at 18:09, Herby >> VojÄÃk<herby(a)mailbox.sk <mailto:herby@mailbox.sk> >> <mailto:herby@mailbox.sk <mailto:herby@mailbox.sk>>> wrote: >> >> Hello! >> >> First of all, what is preferred way to (first time) >> login >> into database? I >> had the impression that `aDatabaseAccessor login` >> is sorta >> low-level, and >> one should do `session login` (after all, it is >> session you >> get to work >> with, not an accessor). >> >> But with Garage SQLite, `session login`, when >> accessor is >> not logged, always >> fails with "MessageNotUnderstood: >> GASqlite3Driver>>queryEncoding". >> >> Should one not use `session login` at all, then (when >> accessor is logged, it >> just does nothing, if it isn't, it connects the >> accessor, >> but tries to do >> some additional work which always fails)? >> >> Herby >> >> >> From memory this is caused by differences between >> VisualWorks >> and Pharo. >> >> Anyway, it is discussed and resolved in: >> >> http://forum.world.st/Glorp-SQLite3-issue-td4899792.html >> <http://forum.world.st/Glorp-SQLite3-issue-td4899792.html> >> <http://forum.world.st/Glorp-SQLite3-issue-td4899792.html >> <http://forum.world.st/Glorp-SQLite3-issue-td4899792.html>> >> >> >> Doesn't look like solved to me. Anyway, at least I know it >> is known >> for year and no-one seemed to see it as a bug. >> >> I think it is one (you cannot just send queryEncoding where >> no class >> implements it and be fine, imo). >> >> So what is the state of `session login`? Is it meant to be >> used, or >> everyone just took a step down to low-level and uses `accessor >> login` instead? :-( >> >> >> Cheers, >> Alistair >> >> >> Thanks, Herby >> >> >> >> >> >> >> -- >> >> >> >> Guille Polito >> >> >> Research Engineer >> >> French National Center for Scientific Research - _http://www.cnrs.fr_ >> >> >> >> *Web:* _http://guillep.github.io_ >> >> *Phone: *+33 06 52 70 66 13 >> > >

Aug. 5, 2017