March 2019 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Fail on condense when image name is drgeo.image

by Alistair Grant

Hi Hilaire, On Mon, 4 Mar 2019 at 22:18, Hilaire <hilaire(a)drgeo.eu> wrote: > > Hi, > > When I use the stable P7, drgeo build fails. > > There is an obscure error in File>>nextVersion, with negative index > which are not catch, although it looks like it should be. > > This same build was working on alpha P7 of June. > > The stack of the debugger is attached as well the PharoDebug.log. > > Does it sound familiar to any of you? There were some changes made to FileReference>>nextVersion late last year (it was broken with only .1 and .1.1 version numbers being created). It looks like drgeo.changes.new has uncovered another issue as #nextVersion returns drgeo.1.new, when it should probably return drgeo.changes.1.new. But I can't reproduce the problem you're seeing. Can you create a small script that reproduces the issue? Cheers, Alistair

March 5, 2019

Fail on condense when image name is drgeo.image

by Hilaire

Hi, When I use the stable P7, drgeo build fails. There is an obscure error in File>>nextVersion, with negative index which are not catch, although it looks like it should be. This same build was working on alpha P7 of June. The stack of the debugger is attached as well the PharoDebug.log. Does it sound familiar to any of you? Hilaire -- Dr. Geo http://drgeo.eu

March 4, 2019

Re: [Pharo-users] Google Protobuf and usage of Slots

by Marcus Denker

Hello! Nice, I will have a look. I am interested to see how class layouts / slots can be used here. (but it might take some days to find timeâ¦) Marcus > On 26 Feb 2019, at 07:54, Holger Freyther <holger(a)freyther.de> wrote: > > Hi, > > from my point of view the pillars of future services are Google protobuf[1] and gRPC. Protobuf can be used for configuration files[2], tracing/logging[3] and storage[4]. gRPC is built on top-of HTTP2 and is using the protobuf IDL and marshaling. Many projects (etcd, envoy, Google Cloud, ...) provide a gRPC based API (and some automatically map this from REST to gRPC) already and I would like to build clients and servers in Pharo. > > > My plan of action is to start with a protobuf compiler/model and then look into binding the gRPC C implementation to Pharo. > > > I have started with gokr's Protobuf code on Smalltalkhub and defined base types and a Slot and could use some help to structure this more nicely. > > The code is at: https://github.com/zecke/pharo-protobuf and I could use some comments/review of how to use Slots in a significant way (add "type" validation on write, constraint checks, builder pattern?). > > Given a definition like: > > syntax = "proto2"; > package foo; > enum Color { > RED = 0; > GREEN = 1; > BLUE = 2; > } > message MyMessage { > optional Color color = 1; > } > > And an encoded binary message of #[8 2] the following can: > > PBTestMessage materializeFrom: #[8 2] readStream > > > decode and set the color field. Proper handling of mandatory and repeated fields are missing and decoding the other values, nested messages... :) > > > > Looking forward to have some eyes on the code. > > holger > > > > > > [1] A simple IDL to define structs/enums with marshaller/materializer for a binary protocol, JSON (and yaml). > > [2] Without having to write a XML/JSON schema and getting validation from the IDL. > > [3] Many of us log structured to text, then have something like logstash to re-parse, regexp it and dump it into ElasticSearch. With protobuf we can have plain objects end to end for logging. > > [4] We have FUEL so this is less interesting for us than others but quite interesting if you are mixing Pharo with other implementation languages.

March 4, 2019

Changes between two different classes

by Ben Coman

Say I duplicate Class A as Class B then modify some methods in Class B. Is there some way to use the DIff or Changes tools to compare Class A and Class B ? cheers -ben

March 4, 2019

Exercism / Ring

by Ben Coman

For Pharo track on https://exercism.io it may be useful for mentors to be able to review submitted solutions without disturbing their live image, and I wonder if Ring could be useful? Looking at Slide 30 here... https://www.slideshare.net/esug/metamodeling-of-custom-pharo-images it seems that maybe Calypso can open up on a Ring model? cheers -ben

March 4, 2019

Re: [Pharo-users] A "with" construct like Pascal - easy to do, but is it terrible?

by Herby VojÄÃk

On 4. 3. 2019 14:15, Esteban Maringolo wrote: > Well... you have the cascading that provides you that. > > book1 > title:'C Programming'; > author: 'Nuha Ali '; > subject: 'C Programming Tutorial'; > book_id: 6495407. > > What I would like, sometimes, is the option to nest cascades, very > much like the WITH DO construct of Pascal, Basic and others. Shameless plug: https://blog.herby.sk/post/customizing-cascade. Some year(s) ago I did a poll in twitter in ppl would like this in Amber. It was 5 for, 5 against. Herby > > But also I take this as a hint of some refactoring needed in my objects. > > Regards, > > Esteban A. Maringolo

March 4, 2019

Re: [Pharo-users] A "with" construct like Pascal - easy to do, but is it terrible?

by Tim Mackinnon

> On 4 Mar 2019, at 13:59, Christian Haider <christian.haider(a)smalltalked-visuals.com> wrote: > > Or #ifNotNil: When you are in the right mindset - lots of things come out of the wood work...

March 4, 2019

Re: [Pharo-users] A "with" construct like Pascal - easy to do, but is it terrible?

by Tim Mackinnon

> On 4 Mar 2019, at 13:34, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > There is #in: that does exactly that: Classic - it was there - you just needed to get the name right. thanks.

March 4, 2019

Re: [Pharo-users] A "with" construct like Pascal - easy to do, but is it terrible?

by Christian Haider

Or #ifNotNil: class metaclass ifNotNil: [ :metaclass | metaclass xxx. metaclass yyy ]. With the added benefit to not do anything with nil. Christian > -----UrsprÃ¼ngliche Nachricht----- > Von: Pharo-users <pharo-users-bounces(a)lists.pharo.org> Im Auftrag von > Sven Van Caekenberghe > Gesendet: Montag, 4. MÃ¤rz 2019 14:35 > An: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Betreff: Re: [Pharo-users] A "with" construct like Pascal - easy to do, but is it > terrible? > > There is #in: that does exactly that: > > class metaclass in: [ :metaclass | > metaclass xxx. > metaclass yyy ]. > > This is quite similar to lisp's let. > > You can do almost anything with blocks/closures. > > Although not relevant in most cases, there is a small performance price to > pay - but again this is only relevant inside performance critical loops. > > > On 4 Mar 2019, at 14:06, Tim Mackinnon <tim(a)testit.works> wrote: > > > > Iâve noticed that as weâve progressed there has been a move to more > concise and fluid code - e.g. I quite like the new String streaming stuff > > > > e.g. > > > > ^ String > > streamContents: [ :stream | > > stream nextPut: â¦. ] > > > > > > So I was wondering why we donât have a construct like Pascals with to > avoid Book1.title, Book1.author etc. > > > > (* book 1 specification *) > > With Book1 do > > begin > > > > title > > := 'C Programming'; > > > > author > > := 'Nuha Ali '; > > > > subject > > := 'C Programming Tutorial'; > > > > book_id > > := 6495407; > > end; > > > > I often find it a bit tedious with code like the following which then needs an > instvar... > > > > self classes do: [ :class | > > | metaclass | > > metaclass := class metaclass. > > metaclass xxxx. > > mataclass yyyy. > > ] > > > > > > Iâm wondering why we donât have #with:do: > > > > class with: class metaclass do: [:metaclass | > > metaclass xxx. > > ] > > > > > > But when such things arenât there - there is usually a good reason and Iâm > curious â¦ this said, there are all kinds of other such tricks (which I rarely use > that I keep coming across). > > > > Tim > > >

March 4, 2019

Re: [Pharo-users] A "with" construct like Pascal - easy to do, but is it terrible?

by Sven Van Caekenberghe

There is #in: that does exactly that: class metaclass in: [ :metaclass | metaclass xxx. metaclass yyy ]. This is quite similar to lisp's let. You can do almost anything with blocks/closures. Although not relevant in most cases, there is a small performance price to pay - but again this is only relevant inside performance critical loops. > On 4 Mar 2019, at 14:06, Tim Mackinnon <tim(a)testit.works> wrote: > > Iâve noticed that as weâve progressed there has been a move to more concise and fluid code - e.g. I quite like the new String streaming stuff > > e.g. > > ^ String > streamContents: [ :stream | > stream nextPut: â¦. ] > > > So I was wondering why we donât have a construct like Pascals with to avoid Book1.title, Book1.author etc. > > (* book 1 specification *) > With Book1 do > begin > > title > := 'C Programming'; > > author > := 'Nuha Ali '; > > subject > := 'C Programming Tutorial'; > > book_id > := 6495407; > end; > > I often find it a bit tedious with code like the following which then needs an instvar... > > self classes do: [ :class | > | metaclass | > metaclass := class metaclass. > metaclass xxxx. > mataclass yyyy. > ] > > > Iâm wondering why we donât have #with:do: > > class with: class metaclass do: [:metaclass | > metaclass xxx. > ] > > > But when such things arenât there - there is usually a good reason and Iâm curious â¦ this said, there are all kinds of other such tricks (which I rarely use that I keep coming across). > > Tim >

March 4, 2019