- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] 72ccbe: 60198

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 72ccbe586c93ea0c303250aee0f068247f69e9a7 https://github.com/pharo-project/pharo-core/commit/72ccbe586c93ea0c303250ae… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-09-02 (Fri, 02 Sep 2016) Changed paths: A Kernel.package/PackageManifest.class/class/unloading/postUnloadAction.st A Kernel.package/PackageManifest.class/class/unloading/preUnload.st M Monticello.package/MCWorkingCopy.class/instance/operations/unload.st M Morphic-Core.package/MouseEvent.class/instance/converting/asMouseMove.st M Morphic-Core.package/MouseEvent.class/instance/converting/asMouseOver.st A RPackage-Core.package/RPackage.class/instance/accessing/packageManifestOrNil.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/README.md A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/definition.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-class relationship/testChangingClassOfObject.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-class relationship/testGettingClassOfObject.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testChangingFixedFieldOfArray.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testChangingFixedFieldOfFixedObject.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testChangingFixedFieldOfWeakMessageSend.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testChangingGeneralFieldOfArray.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testChangingGeneralFieldOfFixedObject.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testChangingGeneralFieldOfWeakMessageSend.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testChangingIndexableFieldOfArray.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testChangingIndexableFieldOfFixedObject.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testChangingIndexableFieldOfWeakMessageSend.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testGettingFixedFieldOfArray.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testGettingFixedFieldOfFixedObject.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testGettingFixedFieldOfWeakMessageSend.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testGettingFixedSizeOfArray.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testGettingFixedSizeOfFixedObject.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testGettingFixedSizeOfWeakMessageSend.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testGettingFullSizeOfArray.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testGettingFullSizeOfFixedObject.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testGettingFullSizeOfWeakMessageSend.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testGettingGeneralFieldOfArray.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testGettingGeneralFieldOfFixedObject.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testGettingGeneralFieldOfWeakMessageSend.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testGettingIndexableFieldOfArray.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testGettingIndexableFieldOfFixedObject.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testGettingIndexableFieldOfWeakMessageSend.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testGettingIndexibleSizeOfArray.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testGettingIndexibleSizeOfFixedObject.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-fields accessing/testGettingIndexibleSizeOfWeakMessageSend.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-hashes/testGettingIdentityHashOfObject.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-message performing/testExecutingMethod.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-message performing/testExecutingPrimitive.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-message performing/testPerformingMessage.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-message performing/testPerformingMessageInSuperclass.st A ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-printing/testPrintingObject.st A ReflectionMirrors-Primitives.package/MirrorPrimitives.class/README.md A ReflectionMirrors-Primitives.package/MirrorPrimitives.class/class/class relationship/classOf_.st A ReflectionMirrors-Primitives.package/MirrorPrimitives.class/class/class relationship/setClass_to_.st A ReflectionMirrors-Primitives.package/MirrorPrimitives.class/class/errors/errorNotIndexableFor_.st A ReflectionMirrors-Primitives.package/MirrorPrimitives.class/class/fields accessing/fieldOf_at_.st A ReflectionMirrors-Primitives.package/MirrorPrimitives.class/class/fields accessing/fieldOf_at_put_.st A ReflectionMirrors-Primitives.package/MirrorPrimitives.class/class/fields accessing/fixedFieldOf_at_.st A ReflectionMirrors-Primitives.package/MirrorPrimitives.class/class/fields accessing/fixedFieldOf_at_put_.st A ReflectionMirrors-Primitives.package/MirrorPrimitives.class/class/fields accessing/fixedSizeOf_.st A ReflectionMirrors-Primitives.package/MirrorPrimitives.class/class/fields accessing/indexableFieldOf_at_.st A ReflectionMirrors-Primitives.package/MirrorPrimitives.class/class/fields accessing/indexableFieldOf_at_put_.st A ReflectionMirrors-Primitives.package/MirrorPrimitives.class/class/fields accessing/indexableSizeOf_.st A ReflectionMirrors-Primitives.package/MirrorPrimitives.class/class/fields accessing/sizeOf_.st A ReflectionMirrors-Primitives.package/MirrorPrimitives.class/class/hashes/identityHashOf_.st A ReflectionMirrors-Primitives.package/MirrorPrimitives.class/class/message performing/withReceiver_andArguments_execute_.st A ReflectionMirrors-Primitives.package/MirrorPrimitives.class/class/message performing/withReceiver_perform_withArguments_.st A ReflectionMirrors-Primitives.package/MirrorPrimitives.class/class/message performing/withReceiver_perform_withArguments_inSuperclass_.st A ReflectionMirrors-Primitives.package/MirrorPrimitives.class/class/message performing/withReceiver_tryPrimitive_withArguments_.st A ReflectionMirrors-Primitives.package/MirrorPrimitives.class/class/printing/print_.st A ReflectionMirrors-Primitives.package/MirrorPrimitives.class/class/printing/print_on_.st A ReflectionMirrors-Primitives.package/MirrorPrimitives.class/definition.st A ReflectionMirrors-Primitives.package/MirrorPrimitives.class/instance/help/seeClassSide.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60197.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60198.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60197.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60198.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Shout.package/SHRBTextStyler.class/instance/visiting/visitLiteralArrayNode_.st A System-Support-Rules.package/AsClassRule.class/README.md A System-Support-Rules.package/AsClassRule.class/definition.st A System-Support-Rules.package/AsClassRule.class/instance/accessing/group.st A System-Support-Rules.package/AsClassRule.class/instance/accessing/name.st A System-Support-Rules.package/AsClassRule.class/instance/accessing/severity.st A System-Support-Rules.package/AsClassRule.class/instance/initialization/initialize.st Log Message: ----------- 60198 18859 Loading a package break word selection on Windows https://pharo.fogbugz.com/f/cases/18859 18930 Regression: Time to show big methods is too high https://pharo.fogbugz.com/f/cases/18930 19020 add preUnload message to Manifest https://pharo.fogbugz.com/f/cases/19020 19022 asClass rules https://pharo.fogbugz.com/f/cases/19022 18827 Mirror primitives should be easy to use https://pharo.fogbugz.com/f/cases/18827 http://files.pharo.org/image/60/60198.zip

Sept. 2, 2016

[pharo-project/pharo-core]

by GitHub

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

Sept. 2, 2016

Re: [Pharo-dev] about clas deprecation

by Nicolas Passerini

Sounds good! On Fri, Sep 2, 2016 at 8:11 AM, stepharo <stepharo(a)free.fr> wrote: > Hi > > Using the idea we got with Peter Uhnak, we know implemented using > transformation library of gustavo two new transformation: > > - deprecate class > > just compile a new method raising a warning: > > + a class method deprecated returning true (this could then > improve to rename the method new if it already exist). > > - rename and deprecate: > > the idea here is that we want to make sure that we can rename a > class and that external users get a chance to load and execute their code. > For that if we have a class A we rename it into ANewName and create an > empty subclass A that we deprecate. > > Let us know what you think. > > Stef and Gustavo > > >

Sept. 2, 2016

Slides online: "Perfection & Feedback Loops" talk from esug

by Marcus Denker

Hi, At ESUG last Friday I gave a talk "Perfection & Feedback Loops or: why worse is betterâ, I was asked for the slides. They are now online: http://www.slideshare.net/MarcusDenker/perfection-feedback-loops-or-why-wor… As the slides do not contain much (just headlines), I created a special âAnnotatedâ version with links and some comments so one can follow better: http://marcusdenker.de/talks/16ESUG/FeedbackLoopsAnnotated.pdf PDF and .key file are there, too: http://marcusdenker.de/talks/16ESUG/ (the .key file contains the embedded videos shown). A video of the presentation should be available soon. Marcus

Sept. 2, 2016

Re: [Pharo-dev] About the non-use of Announcer in Bloc

by stepharo

this is really cool :) Le 1/9/16 Ã 10:21, Thierry Goubier a Ã©crit : > Hi Stef, > > here is the script I use: > > | c1 c2 c3 n1 n2 n3 l1 l2 l3 | > c1 := c2 := c3 := 0. > n1 := (Announcer>>#announce:) ast. > n2 := #(subscribe:do: subscribe:send:to: basicSubscribe:) collect: [ > :e | (Announcer>>e) ast ]. > n3 := #(unsubscribe: removeSubscription:) collect: [ :e | > (Announcer>>e) ast ]. > l1 := MetaLink new metaObject: [ c1 := c1 + 1 ]; selector: #value. > l2 := MetaLink new metaObject: [ c2 := c2 + 1 ]; selector: #value. > l3 := MetaLink new metaObject: [ c3 := c3 + 1 ]; selector: #value. > [ n1 link: l1. n2 do: [ :e | e link: l2 ]. n3 do: [ :e | e link: l3 ]. > (Duration minutes: 1) wait. > n1 removeLink: l1. n2 do: [ :e | e removeLink: l2 ]. n3 do: [ :e | e > removeLink: l3 ]. > { 'announce' -> c1. 'subscribe' -> c2. 'unsubscribe' -> c3 } inspect > ] forkAt: Processor userBackgroundPriority > > Images intÃ©grÃ©es 1 > > 2016-09-01 9:28 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com > <mailto:thierry.goubier@gmail.com>>: > > Hi Stef, > > > 2016-09-01 8:13 GMT+02:00 stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > > Hi thierry > > I think that if we would have a tool to show us the activity > I'm quite sure that we would find bugs > > or mistaken behavior. > > > Yes. I did some checks on Morphic and AltBrowser after getting the > numbers, to see if I wasn't > doing something wrong with my code. > > could you send the scripts you did? > > > Later today. I don't have access now to the laptop where I did it. > > Thierry > > > Stef > > > Le 30/8/16 Ã 22:36, Thierry Goubier a Ã©crit : > > Numbers for the discussion: > > No activity, empty desktop: > announcements 608/minute > subscribe add/remove 9/minute > > Activity, AltBrowser: > announcements 1109/minute > subscribe add/remove 207/minute > > Activity, Nautilus: > announcements 2488/minute > subscribe add/remove 716/minute > > Empirically the same processus in both environments: open > two system browser, in one, find the Announcer class, > browse through a few of the methods, select > basicSubscribe: and ask for senders. > > Tracing done with Metalinks during one minute. > > Not exactly what I would have expected, especially the > ratio subscribe add/remove and announcements. > > Thierry > > Le 30/08/2016 Ã 17:36, Henrik Johansen a Ã©crit : > > > On 30 Aug 2016, at 5:16 , Thierry Goubier > <thierry.goubier(a)gmail.com > <mailto:thierry.goubier@gmail.com>> wrote: > > > I have the same concern with an Announcer > optimized for certain use > cases, in the fact that the announcer creator is > the one choosing > the 'kind of' optimisation it would target, hoping > that the > listeners will conform to that use case... > > > > There simply is no silver bullet that will give unbeatable > performance in all scenarios; and focusing on > improving one facet of > the default implementation will inevitably lead to > either - the loss > of some important property (general thread-safety if > removing the > mutex protection, ability to unsubscribe in handler if > removing the > copy operation and extending the delivery mutex > protection, etc.) - > greatly degenerated performance for another facet > (like #remove for > OC's). > > That said, the current implementation is very geared > towards decent, > balanced subscribe/unsubscribe performance, at the > expense of > delivery speed. I've said it before, and still think, > that offering > at least one other implementation emphasizing delivery > speed over > subscription/unsubscription performance, in the same > way the original > implementation did (and/or changing the default > Announcer to switch > between the two dynamically based on heuristics) > *would* be a > valuable addition to the general library. > > Cheers, Henry > > > > > > > >

Sept. 2, 2016

about clas deprecation

by stepharo

Hi Using the idea we got with Peter Uhnak, we know implemented using transformation library of gustavo two new transformation: - deprecate class just compile a new method raising a warning: + a class method deprecated returning true (this could then improve to rename the method new if it already exist). - rename and deprecate: the idea here is that we want to make sure that we can rename a class and that external users get a chance to load and execute their code. For that if we have a class A we rename it into ANewName and create an empty subclass A that we deprecate. Let us know what you think. Stef and Gustavo

Sept. 2, 2016

Re: [Pharo-dev] [Moose-dev] [ann] pillar support in gtinspector

by Sean P. DeNigris

stepharo wrote > It does. We want a real editor in Pharo. +10 :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/ann-pillar-support-in-gtinspector-tp4913115p4913691.h… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 2, 2016

Re: [Pharo-dev] Binary selector and special characters

by Richard Sargent

Nicolai Hess-3-2 wrote > 2016-08-31 17:31 GMT+02:00 John Brant < > brant@ > >: > >> On 08/31/2016 08:46 AM, Nicolai Hess wrote: >> >> Anyone knows why RefactoringBrowsers smalltalk scanner (RBScanner) >>> explicit allowes >>> "#($Â± $Â· $Ã $Ã·)" to be binary selector characters ? >>> >> >> I do -- I added them about 20 years ago :)... >> >> Is there any smalltalk dialect that uses these characters ? >>> >> >> VW allows them. When possible, we made the scanner/parser be a superset >> of >> the VW & VA syntax. >> >> >> John Brant >> >> > Thank you John, for the info. > Hm, now, what to do, fix our (pharo) parser to allowe these characters as > binary selectors or change the scanner to not > generate binary selector tokens for them... I would argue that when Zerox PARC created Smalltalk ASCII was all they had to choose from. 40 years later, we have Unicode and we have people from around the world using Smalltalk. Most of them are not native English speakers. Having a Smalltalk implementation that supports Unicode selectors, unary, binary, or keyword, would be a good and welcome things. -- View this message in context: http://forum.world.st/Binary-selector-and-special-characters-tp4912981p4913… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 2, 2016

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

by Alexandre Bergel

I do not see any apparent libraries on OSX. I am inspecting the content of the R application Package and it only contains images and some executables. Alexandre > On Sep 1, 2016, at 1:55 PM, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > > Sorry, I havenât a Mac. > > First, you have to install R. > Then, I think you should only have to copy the R libraries (somewhere in the disk^^) to the Pharo VM folder. > > Tell me if it works ;) > > Vincent > > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org <mailto:pharo-dev-bounces@lists.pharo.org>] De la part de Alexandre Bergel > EnvoyÃ© : jeudi 1 septembre 2016 17:49 > Ã : Any question about pharo is welcome > Cc : scismalltalk(a)googlegroups.com <mailto:scismalltalk@googlegroups.com>; Pharo Development List > Objet : Re: [Pharo-dev] [Pharo-users] [ANN] RProjectConnector V2.1 > > I wanted to try, but there is no installation instruction for OS X :-( > Can you produce some on OS X? It would be great > > Anyway, this is great Vincent! Keep pushing! > > Alexandre > > > On Sep 1, 2016, at 12:42 PM, Blondeau Vincent <vincent.blondeau(a)worldline.com <mailto:vincent.blondeau@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/ <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 <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.!!!" > > > !!!************************************************************************************* > "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. 1, 2016

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

by Blondeau Vincent

Sorry, I havenât a Mac. First, you have to install R. Then, I think you should only have to copy the R libraries (somewhere in the disk^^) to the Pharo VM folder. Tell me if it works ;) Vincent De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Alexandre Bergel EnvoyÃ© : jeudi 1 septembre 2016 17:49 Ã : Any question about pharo is welcome Cc : scismalltalk(a)googlegroups.com; Pharo Development List Objet : Re: [Pharo-dev] [Pharo-users] [ANN] RProjectConnector V2.1 I wanted to try, but there is no installation instruction for OS X :-( Can you produce some on OS X? It would be great Anyway, this is great Vincent! Keep pushing! Alexandre On Sep 1, 2016, at 12:42 PM, Blondeau Vincent <vincent.blondeau(a)worldline.com<mailto:vincent.blondeau@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.!!!" !!!************************************************************************************* "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. 1, 2016