- Pharo-users - lists.pharo.org

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

by Bernardo Ezequiel Contreras

did you try with negate? comment ^ ($" asParser , $" asParser negate star , $" asParser) flatten On Sat, Aug 5, 2017 at 5:26 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > 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.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > -- Bernardo E.C. Sent from a cheap desktop computer in South America.

Aug. 5, 2017

Lazy-initialization patterns

by Esteban A. Maringolo

Hi there, I have a question about lazy initialization accessor methods that always keep me thinking in terms of performance and style. For years I did something like: MyClass>>#property property isNil ifTrue: [ self initializeProperty ]. "It could be ifNil: as well" ^property MyClass>>#initializeProperty "Returns the receiver, not the property." property := self foo collect: [:e | ... ]. But this made me think that maybe I'm performing extra operations, so I started doing something like: MyClass>>#property ^property ifNil: [ self initializeProperty ] MyClass>>#initializeProperty ^property := self foo collect: [:e | ... ] The initialize method is often created by an "Extract Method" refactoring I do in the accesor, where I do the initial implementation. The messages makes me think that the second implementation is "faster", but an initializationMethod returning the value instead of the receiver is a code smell to me. I early initialize everything I know will be be used right away, but for cases it doesn't make sense. What do you think/prefer? Why? Maybe we could use the reified variables (slots) to implement the lazy initialization themselves :) Best regards! Esteban A. Maringolo

Aug. 5, 2017

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

by Esteban A. Maringolo

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 2017-08-05 15:52 GMT-03:00 Herby VojÄÃk <herby(a)mailbox.sk>: > Alistair Grant wrote: > >> Hi Herby, >> >> On 5 August 2017 at 18:09, Herby VojÄÃk<herby(a)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 >> > > 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 > >

Aug. 5, 2017

PetitParser: Parse X as long as it's not Y

by Sean P. DeNigris

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.h… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 5, 2017

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

by Herby VojÄÃk

Alistair Grant wrote: > Hi Herby, > > On 5 August 2017 at 18:09, Herby VojÄÃk<herby(a)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 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

Aug. 5, 2017

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

by Alistair Grant

Hi Herby, On 5 August 2017 at 18:09, Herby VojÄÃk <herby(a)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 Cheers, Alistair

Aug. 5, 2017

Re: [Pharo-users] problem with FLMaterializer

by Johannes Brauer

In the EnterprisePharo Book there is a chapter "Fuel Format Migration". There the format migration form Fuel version 1.7 to 1.9 is shown. I ask me if there is a similar possibility for the migration between Fuel in Pharo 4 and 6. Johannes Am 05.08.2017 um 15:08 schrieb Cyril Ferlicot <cyril.ferlicot(a)gmail.com<mailto:cyril.ferlicot@gmail.com>>: On sam. 5 aoÃ»t 2017 at 13:10, Johannes Brauer <brauer(a)nordakademie.de<mailto:brauer@nordakademie.de>> wrote: Peter Your suggestion is correct. I correct the expression to (FLMaterializer materializeFromFileNamed: aFileRefence fullName) Now I get another exception. KeyNotFound: key #'ositive8SmallIntegerClusterJ 4Ã 1â Ã°+ â( %? "< 9 Âª 6P M Â¾0 d *ÃD ''x ! Å 8' not found in SystemDictionary I think this is a compatibility problem between different Fuel versions. Hi, If you use Fuel to serialize objects with Pharo 4, then you can only materialize them with a Fuel from Pharo 4. Other versions of Fuel will not be able to read them. Johannes -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Aug. 5, 2017

Re: [Pharo-users] about a pillar based output format for Epicea

by Stephane Ducasse

This is question of time and energy. I should restart to work and make it smaller and nicer. I want ecstatic too. On Wed, Aug 2, 2017 at 10:21 PM, Tim Mackinnon <tim(a)testit.works> wrote: > Out of curiosity (as Pillar - well actually Ecstatic, was on my next hitlist > to research), but is it so different from something like JavaScripts > Metalsmith.io ? I found metalsmithâs publishing pipeline and plugin system > quite intuitive and easy to use but I just didnât like nodejs so much (and > the crappy webpack/brunch auto reloading systems). > > It struck me that what they were doing was quite trivial in Smalltalk and I > assumed Pillar (and Ecstatic) were similar in concept. However when I had a > peak it did look quite complicated and made me think that porting Metalsmith > might be easier and in interesting personal project. > > Anyway, might be worth a look if you want architectural inspiration. > > Tim > > Sent from my iPhone > > > On 2 Aug 2017, at 18:19, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > I'm because Pillar is central to all my writings around Pharo (books, > slides,...). > We also want to use it for a lecture on open-source development. > > Pillar got too complex and we should simplify its architecture. > > I'm working on a new version of Cocoon but this tedious and I got > stuck in managing > initialisation of fields (from text to objects). now I will continue > to work but task switching is killing me. > Guillermo is helping me from time to time and damien helps me with the > makefile/latex. > > I will first finish all the slides for my lectures at Prague first. > > Now we made > - sure that we can run archetype without being forced to passed by the > command-line. > - and many changes and cleanup. > Now we should work on > > - Make sure that we identify for real bugs showing up in the three > different archetypes (slides, books...). > - Avoid to convert to JSON files to apply mustache. > > - Rethink the architecture. > - Like removing the dependency on magritte from the core. > - Avoid a lot of strange behavior related to metadata handling. > > Stef > > > On Wed, Aug 2, 2017 at 6:15 PM, Alexandre Bergel > <alexandre.bergel(a)me.com> wrote: > > Pillar is becoming central in the way I produce documents. > Is there anyone working on improving Pillar? > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Aug 2, 2017, at 11:55 AM, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > > Hi martin > > I would like to wlak over epicea objects and save the changed methods > to be able to write booklets faster. > What advices can you give me? > Create a special visitor? > > Stef > > > >

Aug. 5, 2017

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

by Stephane Ducasse

Hi Evan Depending on the size of the documentation. - if you have a kind of tutorial I would go (and I can help) for a pillar booklet or a chapter. - else class comments are simply cool with examples stef On Sat, Aug 5, 2017 at 2:19 AM, Evan Donahue <emdonahu(a)gmail.com> wrote: > Hello, > > I'm working on cleaning up a couple of projects for release, and I was > wondering what the best practices were for including appropriate > documentation with projects. Should I just drop a text blob in a prominent > class comment? Is there a tool for structuring documentation? Is > documentation typically kept separate from the code? Seems natural to > include it so you never have to leave the image, but I'm not sure what most > people do. > > Thanks, > Evan

Aug. 5, 2017

Glorp: `session login` fails for Garage SQLite

by Herby VojÄÃk

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

Aug. 5, 2017