- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo 6] failing tests down to 6

by Ben Coman

Cool to hear this progress. cheers -ben On Wed, Sep 14, 2016 at 1:51 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> With these, we are down to 9 failing tests on the CI: >> > We are down to 6! These: > > > SmalllintManifestCheckerTest.testCriticsOf > SmalllintManifestCheckerTest.testToDoOf > - tests need to be updated, will be fixed with next QA update > > ReleaseTest.testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits > - fixed upstream > > SystemAnnouncerLiveTest.testNoDeadSubscriptions > Announcements.Tests.Core.Tests.WeakAnnouncerTest.testNoDeadWeakSubscriptions > > ClassDescriptionTest.testClassDescriptionRespectsPolymorphismWithTraitDescription > #iconNamed: in ClassDescription. > > > >

Sept. 13, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

by Nicolai Hess

2016-09-13 21:00 GMT+02:00 stepharo <stepharo(a)free.fr>: > Hi nicolai > > Why we should not accept > > foo > <func: (3+4) res:0> > ^ self > > and be forced to put around '' > > foo > < func: '(3+4)' res: 0 > > ^ self > > I understand that we store literal but why you do not like it :). > First of all, the old compiler did not accept this. And I am a bit sensitive about changes, we allow a different syntax just because RB happens to allow this (and maybe no one knows why or it just does not happens on purpose). And another reason, even without my fix, if we don't put quotes around that expression, the reformatting the source will convert this to: foo <func: #(3 #+ 4) res: 0> ^ self And, even if (3+4) looks like an expression, it is just a list of literals something like this: foo <func: ([[[}}}) res:0> ^ self would be allowed too. But of course this is only my own opinion :) We can change it back and maybe add support for the reformatter to not convert it to the literal array #(3 #+ 4) . nicolai > Stef > > > 60220 >> 19086 do not allow expressions as pragma arguments >> https://pharo.fogbugz.com/f/cases/19086 >> > > >

Sept. 13, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

by stepharo

Hi nicolai Why we should not accept foo <func: (3+4) res:0> ^ self and be forced to put around '' foo < func: '(3+4)' res: 0 > ^ self I understand that we store literal but why you do not like it :). Stef > 60220 > 19086 do not allow expressions as pragma arguments > https://pharo.fogbugz.com/f/cases/19086

Sept. 13, 2016

[Pharo 6] failing tests down to 6

by Marcus Denker

> > With these, we are down to 9 failing tests on the CI: > We are down to 6! These: SmalllintManifestCheckerTest.testCriticsOf SmalllintManifestCheckerTest.testToDoOf - tests need to be updated, will be fixed with next QA update ReleaseTest.testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits - fixed upstream SystemAnnouncerLiveTest.testNoDeadSubscriptions Announcements.Tests.Core.Tests.WeakAnnouncerTest.testNoDeadWeakSubscriptions ClassDescriptionTest.testClassDescriptionRespectsPolymorphismWithTraitDescription #iconNamed: in ClassDescription.

Sept. 13, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60220 Home: https://github.com/pharo-project/pharo-core

Sept. 13, 2016

[pharo-project/pharo-core] edd9f3: 60220

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: edd9f3770d89ef3c48592411b97507dcb453bcef https://github.com/pharo-project/pharo-core/commit/edd9f3770d89ef3c48592411… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-09-13 (Tue, 13 Sep 2016) Changed paths: M AST-Core.package/RBParser.class/instance/private-parsing/parsePragmaLiteral.st A AST-Tests-Core.package/RBParserTest.class/instance/tests parsing/testInvalidPragmaPosition.st R AST-Tests-Core.package/RBParserTest.class/instance/tests parsing/testInvalidPragmas.st A AST-Tests-Core.package/RBParserTest.class/instance/tests parsing/testPragmaImplicitLiteralArrayIsInvalid.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60219.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60220.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60219.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60220.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60220 19086 do not allow expressions as pragma arguments https://pharo.fogbugz.com/f/cases/19086 http://files.pharo.org/image/60/60220.zip

Sept. 13, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] d6bfc8: 60219

by Marcus Denker

Hi, This update should fix the âload updatesâ menu. Thanks to Norbert who helped tracking that down. Marcus > On 13 Sep 2016, at 18:55, GitHub <noreply(a)github.com> wrote: > > Branch: refs/heads/6.0 > Home: https://github.com/pharo-project/pharo-core > Commit: d6bfc88a219ec6f709fa6d481aa7c83c27089dbc > https://github.com/pharo-project/pharo-core/commit/d6bfc88a219ec6f709fa6d48… > Author: Jenkins Build Server <board(a)pharo-project.org> > Date: 2016-09-13 (Tue, 13 Sep 2016) > > Changed paths: > M Kernel-Tests.package/MetaclassTest.class/instance/tests/testMetaclassAndTraitClassRespectsPolymorphismRules.st > A Kernel.package/Metaclass.class/instance/instance creation/newAnonymousSubclass.st > R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60218.st > A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60219.st > R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60218.st > A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60219.st > M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st > M System-Support.package/SystemVersion.class/instance/printing/shortVersionString.st > > Log Message: > ----------- > 60219 > 17857 newAnonymousSubclass should works for Metaclass > https://pharo.fogbugz.com/f/cases/17857 > > 19082 The tool to do updates is broken due to space in SystemVersion > https://pharo.fogbugz.com/f/cases/19082 > > http://files.pharo.org/image/60/60219.zip > >

Sept. 13, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60219 Home: https://github.com/pharo-project/pharo-core

Sept. 13, 2016

[pharo-project/pharo-core] d6bfc8: 60219

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: d6bfc88a219ec6f709fa6d481aa7c83c27089dbc https://github.com/pharo-project/pharo-core/commit/d6bfc88a219ec6f709fa6d48… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-09-13 (Tue, 13 Sep 2016) Changed paths: M Kernel-Tests.package/MetaclassTest.class/instance/tests/testMetaclassAndTraitClassRespectsPolymorphismRules.st A Kernel.package/Metaclass.class/instance/instance creation/newAnonymousSubclass.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60218.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60219.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60218.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60219.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Support.package/SystemVersion.class/instance/printing/shortVersionString.st Log Message: ----------- 60219 17857 newAnonymousSubclass should works for Metaclass https://pharo.fogbugz.com/f/cases/17857 19082 The tool to do updates is broken due to space in SystemVersion https://pharo.fogbugz.com/f/cases/19082 http://files.pharo.org/image/60/60219.zip

Sept. 13, 2016

Re: [Pharo-dev] [ANN] RProjectConnector V2.1

by Blondeau Vincent

> -----Message d'origine----- > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de > Serge Stinckwich > EnvoyÃ© : vendredi 2 septembre 2016 16:44 > Ã : Pharo Development List > Cc : scismalltalk(a)googlegroups.com; Any question about pharo is welcome > Objet : Re: [Pharo-dev] [ANN] RProjectConnector V2.1 > > Great job Vincent ! > It will be great when it will work on OS X ;) > There is some problems on Mac OS X: > - when I try to load in a fresh Pharo 5.0 image, I got a DNU on: > RObjectArray class>>initElementType: > I was able to load the package after a while by loading directly the package > with the Monticello Browser Strange, I deleted these methods... Please ensure you are using a Pharo 6.0 image (it should work under Pharo 5.0 too) and that version 14 of ConfigurationOfRProjectConnector and version 71 of the RConnector packages are loaded. > - Apparently there is still some methods using NB like: RSession > class>>checkSession or RSession class>>initEmbeddedR: Should not, it is modified ... > > I try to move the R dll close to my Pharo VM and also inside the Plugins > directory but without success ... It should be at the same location that libcairo.2.dylib > Is there a way to say where are the R dll instead of copying them ? > Didn't think so .. Maybe the VM developers knows ? Thanks! Vincent > Thank you. > > > > > On Thu, Sep 1, 2016 at 5:42 PM, Blondeau Vincent > <vincent.blondeau(a)worldline.com> wrote: > > Hello everyone, > > > > > > > > I am glad to announce the release of version 2.1 of the RProjectConnector. > > > > The binding between Pharo and R (https://www.r-project.org/) is now > > translated to UFFI and so to Pharo 6.0. > > > > > > > > You can call directly your R methods from Pharo. For example, with the > > famous iris clustering example: > > > > > > > > iris := 'eval' asREval: {RObject findVar: 'iris'}. > > > > 'plot' > > > > asREval: > > > > {(iris at: 'Petal.Length'). > > > > (iris at: 'Petal.Width'). > > > > (#pch -> 21). > > > > (#xlab -> 'length'). > > > > (#ylab -> 'Width'). > > > > (#bg ->((iris at: 'Species') collect: > > [ :value | {'red'. 'green3'. 'blue'} at: value ])). > > > > (#main -> 'Edgar Anderson''s Iris Data')}. > > > > iris inspect. > > > > > > > > To use it, you should install R and copy the R libraries near the > > Pharo VM (see the documentation on SmalltalkHub > > (http://smalltalkhub.com/#!/~VincentBlondeau/RProjectConnector) for > > how to proceed). > > > > > > > > Donât forget to relaunch Pharo after the installation to be able to > > use the connector. > > > > > > > > Only basic features are implemented yet, but you can participate to > > its extension! > > > > > > > > Cheers, > > > > Vincent Blondeau > > > > > > > !!!************************************************************ > ******* > > ****************** "Ce message et les piÃ¨ces jointes sont > > confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il > > peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous > > recevez ce message par erreur, merci d'en avertir immÃ©diatement > > l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre > > assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre > > recherchÃ©e quant au contenu de ce message. Bien que les meilleurs > > efforts soient faits pour maintenir cette transmission exempte de tout > > virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa > > responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant > > d'un virus transmis. > > > > This e-mail and the documents attached are confidential and intended > > solely for the addressee; it may also be privileged. If you receive > > this e-mail in error, please notify the sender immediately and destroy > > it. As its integrity cannot be secured on the Internet, the Worldline > > liability cannot be triggered for the message content. Although the > > sender endeavours to maintain a computer virus-free network, the > > sender does not warrant that this transmission is virus-free and will > > not be liable for any damages resulting from any virus transmitted.!!!" > > > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ !!!************************************************************************************* "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

Sept. 13, 2016