January 2020 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Mm10s] 2020-01-06

by ducasse

Hello Denis > > What is Fluid class parser? This is the name of the class definition we sketched and presented at Maribor. The idea is how to fight the combinatory explosion of parameters (tags, ephemerons, traits, slots, â¦.) For now Iâm putting in place the structure to be able to create a tree of definition nodes for a class definition Superclass < #MyObject uses: #MyTrait; slots: { #a. #b }; classVariables: { #A. #B }; tags: #(Core) ; package: #MyPackage The minimal class definition is the following one: Superclass < #MyObject package: #MyPackage or Superclass < #MyObject Like that we get closer to ruby and other language that have a compact class definition. One of the key constraints is that we do not want to break the syntax. So everything is message based and consistent with the syntax and our motto. But we will see. I prefer talking with something running. When I worked on the package I rewrote everything three times. The idea is that this class definition parser should replace the ClassDefinitionParser (which we will keep for the traditional class definition but that in a couple of years from now should vanish). S. > Is it the name of currently integrated parser? > > Ð²Ñ, 7 ÑÐ½Ð². 2020 Ð³. Ð² 19:48, ducasse <stepharo(a)netcourrier.com <mailto:stepharo@netcourrier.com>>: > Thanks Pablo > > > Last Week > - Working on concurrent programming booklet > - Enlumineur > - Better iceberg explanation with Pablo > - Fluid class parser > > This week > - Fluid class parser > - Enlumineur > - Consortium meeting > - PBE80 > - Working on concurrent programming booklet > > > > > Hello, last week was a short one but some things have been done: > > > > - [VM] Porting the GC fix to Pharo 7 / 8 VM > > - [VM] Building for the different Platforms > > - [VM] Signing for OSX > > - [VM] The versions will be available today to start testing it before > > promoting them to stable. > > - [Pharo8] Fixing Issues before the release > > - [VM Dev] Starting to work in improving tests in JIT and GC. > > > > -- > > Pablo Tesone. > > tesonep(a)gmail.com <mailto:tesonep@gmail.com> > > > > >

Jan. 7, 2020

Re: [Pharo-dev] [Mm10s] 2020-01-06

by Denis Kudriashov

Hi Stef. What is Fluid class parser? Is it the name of currently integrated parser? Ð²Ñ, 7 ÑÐ½Ð². 2020 Ð³. Ð² 19:48, ducasse <stepharo(a)netcourrier.com>: > Thanks Pablo > > > Last Week > - Working on concurrent programming booklet > - Enlumineur > - Better iceberg explanation with Pablo > - Fluid class parser > > This week > - Fluid class parser > - Enlumineur > - Consortium meeting > - PBE80 > - Working on concurrent programming booklet > > > > > Hello, last week was a short one but some things have been done: > > > > - [VM] Porting the GC fix to Pharo 7 / 8 VM > > - [VM] Building for the different Platforms > > - [VM] Signing for OSX > > - [VM] The versions will be available today to start testing it before > > promoting them to stable. > > - [Pharo8] Fixing Issues before the release > > - [VM Dev] Starting to work in improving tests in JIT and GC. > > > > -- > > Pablo Tesone. > > tesonep(a)gmail.com > > > > > >

Jan. 7, 2020

Re: [Pharo-dev] [Mm10s] 2020-01-06

by ducasse

Thanks Pablo Last Week - Working on concurrent programming booklet - Enlumineur - Better iceberg explanation with Pablo - Fluid class parser This week - Fluid class parser - Enlumineur - Consortium meeting - PBE80 - Working on concurrent programming booklet > Hello, last week was a short one but some things have been done: > > - [VM] Porting the GC fix to Pharo 7 / 8 VM > - [VM] Building for the different Platforms > - [VM] Signing for OSX > - [VM] The versions will be available today to start testing it before > promoting them to stable. > - [Pharo8] Fixing Issues before the release > - [VM Dev] Starting to work in improving tests in JIT and GC. > > -- > Pablo Tesone. > tesonep(a)gmail.com >

Jan. 7, 2020

[Mm10s] 2020-01-06

by tesonep＠gmail.com

Hello, last week was a short one but some things have been done: - [VM] Porting the GC fix to Pharo 7 / 8 VM - [VM] Building for the different Platforms - [VM] Signing for OSX - [VM] The versions will be available today to start testing it before promoting them to stable. - [Pharo8] Fixing Issues before the release - [VM Dev] Starting to work in improving tests in JIT and GC. -- Pablo Tesone. tesonep(a)gmail.com

Jan. 7, 2020

[Pharo 9.0] Build #2: 5441--typo-in-HashedCollection--comment

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

There is a new Pharo build available! The status of the build #2 was: SUCCESS. The Pull Request #5442 was integrated: "5441--typo-in-HashedCollection--comment" Pull request url: https://github.com/pharo-project/pharo/pull/5442 Issue Url: https://github.com/pharo-project/pharo/issues/5441 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 7, 2020

Re: [Pharo-dev] pharo compiler on scientific notation

by Sven Van Caekenberghe

https://github.com/pharo-project/pharo/issues/5443 > On 20 Dec 2019, at 13:37, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > The tests you refer to would basically test Float infinity = Float infinity. > > If you change > > NumberParser>>#readExponent > "read the exponent if any (stored in instVar). > Answer true if found, answer false if none. > If exponent letter is not followed by a digit, > this is not considered as an error. > Exponent are always read in base 10." > > | eneg epos | > exponent := 0. > sourceStream atEnd ifTrue: [ ^ false ]. > (self exponentLetters includes: sourceStream peek) ifFalse: [ ^ false ]. > sourceStream next. > eneg := sourceStream peekFor: $-. > epos := eneg not and: [ self allowPlusSignInExponent and: [ sourceStream peekFor: $+ ] ]. > (exponent := self nextUnsignedIntegerOrNilBase: 10) ifNil: [ > "Oops, there was no digit after the exponent letter.Ungobble the letter" > exponent := 0. > sourceStream skip: ((eneg or: [ epos ]) ifTrue: [ -2 ] ifFalse: [ -1 ]). > ^ false ]. > eneg ifTrue: [ exponent := exponent negated ]. > ^ true > > You will get Float infinity for exponents that are too large. > > The test on the exponent range was bogus anyway. > >> On 20 Dec 2019, at 10:58, Nicolas Anquetil <nicolas.anquetil(a)inria.fr> wrote: >> >> >> actually the problem arose from some old code that I tried to load and >> failed to. >> >> So I guess at some point in the past (pharo4 or prior) it was working : >> >> --- >> PPExpressParserTests>>testReal3 >> self parse: '-1.1333e3333' rule: #literal. >> self assert: (result value = -1.1333e3333). >> self assert: (PPSmalltalkParser parseExpression: '- >> 1.1333e3333') = result rbNode >> --- >> >> nicolas >> >> On Fri, 2019-12-20 at 10:21 +0100, Sven Van Caekenberghe wrote: >>> Yes, the difference is not good. >>> >>> Indeed, >>> >>> Float fmax. "1.7976931348623157e308" >>> >>> The reason >>> >>> Number readFrom: '7.5e333'. >>> >>> gives infinity is actual not because of the reading, but because of >>> >>> 75e332 asFloat. >>> >>> Which is probably correct. >>> >>> The failure of >>> >>> Number readFrom: '7.5e3333'. >>> >>> is because of NumberParser>>#readExponent >>> >>> However, the test at the end is probably wrong. >>> >>> Float emax >>> >>> is a binary number, not a decimal one, IIUC. >>> >>> Nicolas (nice) ? >>> >>>> On 19 Dec 2019, at 19:28, tbrunz <wild.ideas(a)gmail.com> wrote: >>>> >>>> I would expect that both would result in +Inf. >>>> >>>> A IEEE-754 'double' overflows around 2e308. >>>> >>>> Surely both cases should behave the same way..?? >>>> >>>> -t >>>> >>>> >>>> >>>> -- >>>> Sent from: >>>> http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >>>> >>> >>> >> -- >> Nicolas Anquetil >> RMod team -- Inria Lille >> >> >

Jan. 6, 2020

[Pharo 8.0] Build #1101: 5441--typo-in-HashedCollection--comment

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

There is a new Pharo build available! The status of the build #1101 was: FAILURE. The Pull Request #5442 was integrated: "5441--typo-in-HashedCollection--comment" Pull request url: https://github.com/pharo-project/pharo/pull/5442 Issue Url: https://github.com/pharo-project/pharo/issues/5441 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 6, 2020

Re: [Pharo-dev] BaselineOfZincHTTPComponents>>baseline:

by Sven Van Caekenberghe

> On 6 Jan 2020, at 08:16, Alistair Grant <akgrant0710(a)gmail.com> wrote: > >> What is your particular problem ? > > Pavel did some refactoring in > https://github.com/pharo-project/pharo/commit/45b7de2b6c901112be04230faba48… > that moved some methods from the FileSystem-Core package to the > Zinc-Resource-Meta-Core package, and they go missing when loading > other Zinc packages, e.g. SSO. Let's see: this should solve your immediate problem then: https://github.com/svenvc/zinc/commit/7d7f55e5654639a81e669b50f196ea4af38b8… It will fix the issue in Pharo 8. It will load uncleanly in Pharo 7, but we could do a back port to it if needed. Sven

Jan. 6, 2020

R: Pharo key features (document)

by Lorenzo

+1 Lorenzo Schiavina Da: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] Per conto di Esteban Lorenzano Inviato: domenica 5 gennaio 2020 12:04 A: Pharo Development List <pharo-dev(a)lists.pharo.org> Oggetto: Re: [Pharo-dev] Pharo key features (document) On 5 Jan 2020, at 11:59, serge.stinckwich(a)gmail.com <mailto:serge.stinckwich@gmail.com> wrote: Impressive list !!! Would be nice to have an html version at the end with high-resolution screen shots and put it on the pharo.org <http://pharo.org> website with nice transition animations like the one you found on Apple website for example. +1 Sent from my iPhone On 5 Jan 2020, at 11:02, Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com> > wrote: ï»¿ Hi, I have created a list of the key Pharo features with some images and animations that should help to explain to public what is cool on Pharo. It is based on a list formerly created for a Wikipedia article. https://github.com/pavel-krivanek/pharoMaterials/blob/master/features/Pharo… Please look at it to check if something is worth to add or change before we will try to use it somewhere for real. Cheers, -- Pavel

Jan. 6, 2020

[Pharo 8.0] Build #1100: [cleanup] better refactor for ReTestClassNotInPackageWithTestEndingNameTest

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

There is a new Pharo build available! The status of the build #1100 was: SUCCESS. The Pull Request #5423 was integrated: "[cleanup] better refactor for ReTestClassNotInPackageWithTestEndingNameTest" Pull request url: https://github.com/pharo-project/pharo/pull/5423 Issue Url: https://github.com/pharo-project/pharo/issues/RenkaruWarning Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 6, 2020