September 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] About Git support for windows

by Esteban Lorenzano

> On 9 Sep 2017, at 12:28, Henrik Nergaard <draagren(a)outlook.com> wrote: > > >> but this is still WIP: for example timestamp needs to go to avoid conflicts. > why/how would this cause conflicts versus other changes? two people modifying same method could have a marge without conflict, but if both modify same line (like the timestamp line), then for sure it will be a conflict :) Esteban > > > Fra: Pharo-dev <pharo-dev-bounces(a)lists.pharo.org> pÃ¥ vegne av Esteban Lorenzano <estebanlm(a)gmail.com> > Sendt: 9. september 2017 11:39:12 > Til: Pharo Development List > Emne: Re: [Pharo-dev] About Git support for windows > > > > On 8 Sep 2017, at 22:02, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > Hi All, > > > >> On Sep 8, 2017, at 9:44 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > >> > >> Hi all > >> > >> At ESUG we discussed with Esteban, martin mcClure, Dale and (many many > >> others :), esteban designed a nice class file format. So that we will > >> not have 2Gb of space on harddisc, problems with long method names and > >> sluggish commits. > > > > Wow, that's great news! It'll make it much easier to import from Pharo hit repositories. Thank you, Esteban! > > > > Can someone post the grammar or a description of the syntax asap? > > I will commit it with a spec next week. > and I made the parser by hand and simple enough (e.g. I didnât use RBParser) so it can be ported easily to other dialects. > > Esteban > > > > >> > >> He is waiting at Wien and is probably checking everything right now. > >> > >> It is a nice format because we will be able to use it to communicate > >> by emails using it. So readable, compact and I like it :) > > > > Lovely! Details please :-) > > > >> > >> Stef > >> > >

Sept. 9, 2017

Re: [Pharo-dev] STON: SortedCollection Bug?

by Sven Van Caekenberghe

> On 9 Sep 2017, at 15:45, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Sven Van Caekenberghe-2 wrote >> STON cannot serialise block closures. > > Oops, sorry. I see that now: > https://github.com/svenvc/ston/blob/master/ston-paper.md#limitations > > I wonder, in this case, there are no references in the block to any objects > except its own arguments. Would it be possible to support that limited case? > (I don't need it for myself, just pondering out loud) Yeah, I was thinking along the same lines, especially clean block might be doable. I'll mark this as todo and think about it a bit.

Sept. 9, 2017

Re: [Pharo-dev] STON: SortedCollection Bug?

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > STON cannot serialise block closures. Oops, sorry. I see that now: https://github.com/svenvc/ston/blob/master/ston-paper.md#limitations I wonder, in this case, there are no references in the block to any objects except its own arguments. Would it be possible to support that limited case? (I don't need it for myself, just pondering out loud) ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Sept. 9, 2017

Re: [Pharo-dev] About Git support for windows

by Henrik Nergaard

>> but this is still WIP: for example timestamp needs to go to avoid conflicts. why/how would this cause conflicts versus other changes? ________________________________ Fra: Pharo-dev <pharo-dev-bounces(a)lists.pharo.org> pÃ¥ vegne av Esteban Lorenzano <estebanlm(a)gmail.com> Sendt: 9. september 2017 11:39:12 Til: Pharo Development List Emne: Re: [Pharo-dev] About Git support for windows > On 8 Sep 2017, at 22:02, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi All, > >> On Sep 8, 2017, at 9:44 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> >> Hi all >> >> At ESUG we discussed with Esteban, martin mcClure, Dale and (many many >> others :), esteban designed a nice class file format. So that we will >> not have 2Gb of space on harddisc, problems with long method names and >> sluggish commits. > > Wow, that's great news! It'll make it much easier to import from Pharo hit repositories. Thank you, Esteban! > > Can someone post the grammar or a description of the syntax asap? I will commit it with a spec next week. and I made the parser by hand and simple enough (e.g. I didnât use RBParser) so it can be ported easily to other dialects. Esteban > >> >> He is waiting at Wien and is probably checking everything right now. >> >> It is a nice format because we will be able to use it to communicate >> by emails using it. So readable, compact and I like it :) > > Lovely! Details please :-) > >> >> Stef >> >

Sept. 9, 2017

Re: [Pharo-dev] About Git support for windows

by Esteban Lorenzano

> On 8 Sep 2017, at 22:02, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi All, > >> On Sep 8, 2017, at 9:44 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> >> Hi all >> >> At ESUG we discussed with Esteban, martin mcClure, Dale and (many many >> others :), esteban designed a nice class file format. So that we will >> not have 2Gb of space on harddisc, problems with long method names and >> sluggish commits. > > Wow, that's great news! It'll make it much easier to import from Pharo hit repositories. Thank you, Esteban! > > Can someone post the grammar or a description of the syntax asap? I will commit it with a spec next week. and I made the parser by hand and simple enough (e.g. I didnât use RBParser) so it can be ported easily to other dialects. Esteban > >> >> He is waiting at Wien and is probably checking everything right now. >> >> It is a nice format because we will be able to use it to communicate >> by emails using it. So readable, compact and I like it :) > > Lovely! Details please :-) > >> >> Stef >> >

Sept. 9, 2017

Re: [Pharo-dev] Changing pharo default branch to development

by Stephane Ducasse

Thanks you guys! I will remove a lot of mistakes :) I think that when we can simplify without losing anything, it is a clear sign that we should do it. Stef On Sat, Sep 9, 2017 at 10:53 AM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > As we discussed in ESUG, and since this is a cheap change to do in the > airport, we are making the development branch in pharo the default branch. > > This will help avoiding accidental pull requests targeting master instead > of development. > > For those who may ask, we will not remove the master branch yet. This is > because we are in the airport doing this and we would like to give it a > better thought :). > > Guille, Esteban and Pablo > > -- > > > > 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 <+33%206%2052%2070%2066%2013> >

Sept. 9, 2017

Changing pharo default branch to development

by Guillermo Polito

As we discussed in ESUG, and since this is a cheap change to do in the airport, we are making the development branch in pharo the default branch. This will help avoiding accidental pull requests targeting master instead of development. For those who may ask, we will not remove the master branch yet. This is because we are in the airport doing this and we would like to give it a better thought :). Guille, Esteban and Pablo -- 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

Sept. 9, 2017

Re: [Pharo-dev] STON: SortedCollection Bug?

by Sven Van Caekenberghe

STON cannot serialise block closures. You would have to get creative to make this work. For SortedCollection, it would only work without a sort block. STON fromString: (STON toString: #(1 2 3) asSortedCollection). > On 9 Sep 2017, at 04:58, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > I serialized aSortedCollection with a sort block comparing via a #startTime > message on the domain objects. When I attempted to materialize it, I got an > error that my domain objects don't understand #<=. It seems that the > elements are being loaded before the sort block. > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Sept. 9, 2017

STON: SortedCollection Bug?

by Sean P. DeNigris

I serialized aSortedCollection with a sort block comparing via a #startTime message on the domain objects. When I attempted to materialize it, I got an error that my domain objects don't understand #<=. It seems that the elements are being loaded before the sort block. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Sept. 9, 2017

Fuel Materialization Error

by Sean P. DeNigris

I'm trying to serialize in Pharo 4.0 and materialize in Pharo 6.1. Although both images claim Fuel 194, when materializing I'm getting: "KeyNotFound: key #FLMethodContextCluster not found in SystemDictionary". Anyone know what the problem is? Thanks! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Sept. 9, 2017