- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Fraction and ScaledDecimal should be not be serialized as Float in STON format

by Julien

Sorry, I forgot to answer. This change is indeed really nice. Thank you for it! Cheers, Julien --- Julien Delplanque Doctorant Ã lâUniversitÃ© de Lille http://juliendelplanque.be/phd.html Equipe Rmod, Inria BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40 > Le 9 oct. 2018 Ã 21:22, Sven Van Caekenberghe <sven(a)stfx.eu> a Ã©crit : > > I decided to add it for real: > > https://github.com/svenvc/ston/commit/9c83e3cc2f00cab83e57f2e10a139d6ecef3c… > > add support for Fraction and ScaledDecimal as direct numeric literals (in STON mode, not in JSON mode) with units tests > >> On 25 Sep 2018, at 14:13, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> >> >>> On 18 Sep 2018, at 16:45, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> Of course, we could also extend the basic number parser and allow the native (stored) notation >>> >>> 1/3 >>> 3/2s2 >>> >>> Note how that last one should use the more exact #storeOn: notation, not the #printOn: >>> >>> I'll have to think about this a bit more, as I can really not choose right now. >> >> I am still not sure if we should do this or not, but here is a POC implementation of the above. >> >> It implements the following syntax extension (see the class comment of STON for the rest). >> >> number >> int >> int denominator >> int denominator scale >> int frac >> int exp >> int frac exp >> >> denominator >> / digits >> >> scale >> s digits >> >> >> STONWriter>>#writeFraction: fraction >> jsonMode >> ifTrue: [ self writeFloat: fraction asFloat ] >> ifFalse: [ >> writeStream >> print: fraction numerator; >> nextPut: $/; >> print: fraction denominator ] >> >> STONWriter>>#writeScaledDecimal: scaledDecimal >> jsonMode >> ifTrue: [ self writeFloat: scaledDecimal asFloat ] >> ifFalse: [ >> writeStream >> print: scaledDecimal numerator; >> nextPut: $/; >> print: scaledDecimal denominator; >> nextPut: $s; >> print: scaledDecimal scale ] >> >> Fraction>>#stonOn: stonWriter >> stonWriter writeFraction: self >> >> ScaledDecimal>>#stonOn: stonWriter >> stonWriter writeScaledDecimal: self >> >> STONReader>>parseNumber >> | negated number | >> negated := readStream peekFor: $-. >> number := self parseNumberInteger. >> (readStream peekFor: $/) >> ifTrue: [ >> number := Fraction numerator: number denominator: self parseNumberInteger. >> (readStream peekFor: $s) >> ifTrue: [ number := ScaledDecimal newFromNumber: number scale: self parseNumberInteger ] ] >> ifFalse: [ >> (readStream peekFor: $.) >> ifTrue: [ number := number + self parseNumberFraction ]. >> ((readStream peekFor: $e) or: [ readStream peekFor: $E ]) >> ifTrue: [ number := number * self parseNumberExponent ] ]. >> negated >> ifTrue: [ number := number negated ]. >> self consumeWhitespace. >> ^ number >> >> Sven >> > >

Oct. 10, 2018

Re: [Pharo-dev] Conversion of my Libraries/Frameworks to GitHub/Tonel/TravisCI, Part 1

by Norbert Hartl

Very cool. Thank you very much, Can you make releases for your repos? In my repos I did a release of a version saying it is the same as the last on smalltalkhub. So people can pinpoint to a specific release. I think this is a good way of doing it. Norbert > Am 05.10.2018 um 14:05 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > Hi, > > I started converting my Libraries/Frameworks to GitHub/Tonel/TravisCI. > So far I did the following: > > https://github.com/svenvc/NeoJSON > https://github.com/svenvc/NeoCSV > https://github.com/svenvc/ztimestamp > https://github.com/svenvc/P3 > https://github.com/svenvc/stamp > https://github.com/svenvc/SimpleRedisClient > https://github.com/svenvc/NeoConsole > > More will follow, in particular Zinc/Zodiac and STON, both of which are more complex. > > The TravisCI builds now run for Pharo 7 (32 & 64 bits) and Pharo 6.1. > By loading the latest Metacello and Tonel, the code is also loadable in Pharo 6 or 5. > > After a while I will switch the Catalog entries and declare these repo the main ones. > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > >

Oct. 10, 2018

Re: [Pharo-dev] GitHub Topics

by Esteban Maringolo

El mar., 9 oct. 2018 a las 18:30, Peter Uhnak (<i.uhnak(a)gmail.com>) escribiÃ³: > >> Maybe there is a minimum threshold required to enable such edits. > issue a pull request to this repo https://github.com/github/explore Done! https://github.com/github/explore/pull/409 Esteban A. Maringolo

Oct. 10, 2018

Re: [Pharo-dev] GitHub Topics

by Peter Uhnak

> So at least 'Pharo' (capitalised) should be there. all topics are forcibly lowercased > I will check because I did not see that we could tag our project. > Personally I will use Pharo because of reasons that you know. For repositories that you control you can see a "button" at the top [image: image.png] Maybe there is a minimum threshold required to enable such edits. > issue a pull request to this repo https://github.com/github/explore Peter

Oct. 9, 2018

Re: [Pharo-dev] Fraction and ScaledDecimal should be not be serialized as Float in STON format

by Stephane Ducasse

This is cool because indeed scaledDecimal are nice objects :) On Tue, Oct 9, 2018 at 9:23 PM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > I decided to add it for real: > > https://github.com/svenvc/ston/commit/9c83e3cc2f00cab83e57f2e10a139d6ecef3c… > > add support for Fraction and ScaledDecimal as direct numeric literals (in STON mode, not in JSON mode) with units tests > > > On 25 Sep 2018, at 14:13, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > > > > >> On 18 Sep 2018, at 16:45, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> > >> Of course, we could also extend the basic number parser and allow the native (stored) notation > >> > >> 1/3 > >> 3/2s2 > >> > >> Note how that last one should use the more exact #storeOn: notation, not the #printOn: > >> > >> I'll have to think about this a bit more, as I can really not choose right now. > > > > I am still not sure if we should do this or not, but here is a POC implementation of the above. > > > > It implements the following syntax extension (see the class comment of STON for the rest). > > > > number > > int > > int denominator > > int denominator scale > > int frac > > int exp > > int frac exp > > > > denominator > > / digits > > > > scale > > s digits > > > > > > STONWriter>>#writeFraction: fraction > > jsonMode > > ifTrue: [ self writeFloat: fraction asFloat ] > > ifFalse: [ > > writeStream > > print: fraction numerator; > > nextPut: $/; > > print: fraction denominator ] > > > > STONWriter>>#writeScaledDecimal: scaledDecimal > > jsonMode > > ifTrue: [ self writeFloat: scaledDecimal asFloat ] > > ifFalse: [ > > writeStream > > print: scaledDecimal numerator; > > nextPut: $/; > > print: scaledDecimal denominator; > > nextPut: $s; > > print: scaledDecimal scale ] > > > > Fraction>>#stonOn: stonWriter > > stonWriter writeFraction: self > > > > ScaledDecimal>>#stonOn: stonWriter > > stonWriter writeScaledDecimal: self > > > > STONReader>>parseNumber > > | negated number | > > negated := readStream peekFor: $-. > > number := self parseNumberInteger. > > (readStream peekFor: $/) > > ifTrue: [ > > number := Fraction numerator: number denominator: self parseNumberInteger. > > (readStream peekFor: $s) > > ifTrue: [ number := ScaledDecimal newFromNumber: number scale: self parseNumberInteger ] ] > > ifFalse: [ > > (readStream peekFor: $.) > > ifTrue: [ number := number + self parseNumberFraction ]. > > ((readStream peekFor: $e) or: [ readStream peekFor: $E ]) > > ifTrue: [ number := number * self parseNumberExponent ] ]. > > negated > > ifTrue: [ number := number negated ]. > > self consumeWhitespace. > > ^ number > > > > Sven > > > >

Oct. 9, 2018

Re: [Pharo-dev] GitHub Topics

by Esteban Maringolo

What I don't know is how to suggest edits to the Pharo topic, so we can also add a logo to it, reference to pharo.org, etc. Maybe there is a minimum threshold required to enable such edits. Esteban A. Maringolo El mar., 9 oct. 2018 a las 16:57, Stephane Ducasse (<stepharo.self(a)gmail.com>) escribiÃ³: > > Hi sven > > I will check because I did not see that we could tag our project. > Personally I will use Pharo because of reasons that you know. > > Stef > On Mon, Oct 8, 2018 at 11:32 AM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > One of the goals of moving to GitHub.com is to gain visibility. > > > > There is https://github.com/topics > > > > I think we should standardise how we tag our projects. > > > > So at least 'Pharo' (capitalised) should be there. > > > > Do we also add 'Smalltalk' by default ? > > > > Any other suggestions, ideas ? > > > > Sven > > >

Oct. 9, 2018

Re: [Pharo-dev] GitHub Topics

by Stephane Ducasse

Hi sven I will check because I did not see that we could tag our project. Personally I will use Pharo because of reasons that you know. Stef On Mon, Oct 8, 2018 at 11:32 AM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > One of the goals of moving to GitHub.com is to gain visibility. > > There is https://github.com/topics > > I think we should standardise how we tag our projects. > > So at least 'Pharo' (capitalised) should be there. > > Do we also add 'Smalltalk' by default ? > > Any other suggestions, ideas ? > > Sven >

Oct. 9, 2018

Re: [Pharo-dev] Fraction and ScaledDecimal should be not be serialized as Float in STON format

by Sven Van Caekenberghe

I decided to add it for real: https://github.com/svenvc/ston/commit/9c83e3cc2f00cab83e57f2e10a139d6ecef3c… add support for Fraction and ScaledDecimal as direct numeric literals (in STON mode, not in JSON mode) with units tests > On 25 Sep 2018, at 14:13, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > >> On 18 Sep 2018, at 16:45, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Of course, we could also extend the basic number parser and allow the native (stored) notation >> >> 1/3 >> 3/2s2 >> >> Note how that last one should use the more exact #storeOn: notation, not the #printOn: >> >> I'll have to think about this a bit more, as I can really not choose right now. > > I am still not sure if we should do this or not, but here is a POC implementation of the above. > > It implements the following syntax extension (see the class comment of STON for the rest). > > number > int > int denominator > int denominator scale > int frac > int exp > int frac exp > > denominator > / digits > > scale > s digits > > > STONWriter>>#writeFraction: fraction > jsonMode > ifTrue: [ self writeFloat: fraction asFloat ] > ifFalse: [ > writeStream > print: fraction numerator; > nextPut: $/; > print: fraction denominator ] > > STONWriter>>#writeScaledDecimal: scaledDecimal > jsonMode > ifTrue: [ self writeFloat: scaledDecimal asFloat ] > ifFalse: [ > writeStream > print: scaledDecimal numerator; > nextPut: $/; > print: scaledDecimal denominator; > nextPut: $s; > print: scaledDecimal scale ] > > Fraction>>#stonOn: stonWriter > stonWriter writeFraction: self > > ScaledDecimal>>#stonOn: stonWriter > stonWriter writeScaledDecimal: self > > STONReader>>parseNumber > | negated number | > negated := readStream peekFor: $-. > number := self parseNumberInteger. > (readStream peekFor: $/) > ifTrue: [ > number := Fraction numerator: number denominator: self parseNumberInteger. > (readStream peekFor: $s) > ifTrue: [ number := ScaledDecimal newFromNumber: number scale: self parseNumberInteger ] ] > ifFalse: [ > (readStream peekFor: $.) > ifTrue: [ number := number + self parseNumberFraction ]. > ((readStream peekFor: $e) or: [ readStream peekFor: $E ]) > ifTrue: [ number := number * self parseNumberExponent ] ]. > negated > ifTrue: [ number := number negated ]. > self consumeWhitespace. > ^ number > > Sven >

Oct. 9, 2018

[Pharo 7.0-dev] Build #1324: 22563-GTInspector-can-loop-on-WindowPresenter

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1324 was: SUCCESS. The Pull Request #1898 was integrated: "22563-GTInspector-can-loop-on-WindowPresenter" Pull request url: https://github.com/pharo-project/pharo/pull/1898 Issue Url: https://pharo.fogbugz.com/f/cases/22563 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 9, 2018

[Pharo 7.0-dev] Build #1323: 22534-split-Refactoring2-package-to-extract-Tests

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1323 was: SUCCESS. The Pull Request #1871 was integrated: "22534-split-Refactoring2-package-to-extract-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/1871 Issue Url: https://pharo.fogbugz.com/f/cases/22534 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 9, 2018