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

[pharo-project/pharo-core]

by GitHub

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

Sept. 30, 2016

[pharo-project/pharo-core] f68ece: 60243

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: f68ecefb602be715d886dc5050f9309585ca06a4 https://github.com/pharo-project/pharo-core/commit/f68ecefb602be715d886dc50… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-09-30 (Fri, 30 Sep 2016) Changed paths: A Kernel.package/CompiledBlock.class/instance/accessing/hash.st A Kernel.package/CompiledBlock.class/instance/accessing/penultimateLiteral.st R Kernel.package/CompiledBlock.class/instance/additions/ast.st R Kernel.package/CompiledBlock.class/instance/additions/hash.st R Kernel.package/CompiledBlock.class/instance/additions/isTestMethod.st R Kernel.package/CompiledBlock.class/instance/additions/pcInOuter.st R Kernel.package/CompiledBlock.class/instance/additions/printOn_.st R Kernel.package/CompiledBlock.class/instance/additions/properties.st R Kernel.package/CompiledBlock.class/instance/additions/sameLiteralsAs_.st R Kernel.package/CompiledBlock.class/instance/additions/sourceNode.st R Kernel.package/CompiledBlock.class/instance/additions/sourceNodeForPC_.st R Kernel.package/CompiledBlock.class/instance/additions/sourceNodeInOuter.st A Kernel.package/CompiledBlock.class/instance/comparing/sameLiteralsAs_.st A Kernel.package/CompiledBlock.class/instance/compatibility/properties.st A Kernel.package/CompiledBlock.class/instance/printing/printOn_.st A Kernel.package/CompiledBlock.class/instance/scanning/hasMethodReturn.st A Kernel.package/CompiledBlock.class/instance/scanning/pcInOuter.st A Kernel.package/CompiledBlock.class/instance/testing/isTestMethod.st M Kernel.package/CompiledCode.class/instance/literals/hasLiteralSuchThat_.st M Kernel.package/CompiledCode.class/instance/literals/hasLiteralThorough_.st M Kernel.package/CompiledCode.class/instance/literals/hasLiteral_.st A Kernel.package/CompiledCode.class/instance/literals/innerCompiledBlocksAnySatisfy_.st A Kernel.package/CompiledCode.class/instance/literals/innerCompiledBlocksDo_.st M Kernel.package/CompiledCode.class/instance/scanning/hasInstVarRef.st A Kernel.package/CompiledCode.class/instance/scanning/localHasInstVarRef.st A Kernel.package/CompiledCode.class/instance/scanning/localMessages.st A Kernel.package/CompiledCode.class/instance/scanning/localReadsRef_.st A Kernel.package/CompiledCode.class/instance/scanning/localSendsToSuper.st A Kernel.package/CompiledCode.class/instance/scanning/localWritesRef_.st M Kernel.package/CompiledCode.class/instance/scanning/messages.st M Kernel.package/CompiledCode.class/instance/scanning/readsField_.st M Kernel.package/CompiledCode.class/instance/scanning/readsRef_.st M Kernel.package/CompiledCode.class/instance/scanning/sendsToSuper.st M Kernel.package/CompiledCode.class/instance/scanning/writesField_.st M Kernel.package/CompiledCode.class/instance/scanning/writesRef_.st A Kernel.package/CompiledMethod.class/instance/scanning/readsField_.st A Kernel.package/CompiledMethod.class/instance/scanning/writesField_.st A Kernel.package/FullBlockClosure.class/instance/scanning/abstractBytecodeMessagesDo_.st A Kernel.package/FullBlockClosure.class/instance/scanning/hasMethodReturn.st R Kernel.package/FullBlockClosure.class/instance/testing/hasMethodReturn.st R Kernel.package/LargeInteger.class/instance/mathematical functions/mightBeASquare.st A Kernel.package/LargeInteger.class/instance/testing/mightBeASquare.st A Kernel.package/LargeNegativeInteger.class/instance/testing/mightBeASquare.st A Kernel.package/LargePositiveInteger.class/instance/testing/mightBeASquare.st A OpalCompiler-Core.package/extension/CompiledBlock/instance/ast.st A OpalCompiler-Core.package/extension/CompiledBlock/instance/sourceNode.st A OpalCompiler-Core.package/extension/CompiledBlock/instance/sourceNodeForPC_.st A OpalCompiler-Core.package/extension/CompiledBlock/instance/sourceNodeInOuter.st A RPackage-Core.package/RPackage.class/instance/class tags/actualClassTags.st A RPackage-Tests.package/RPackageTest.class/instance/tests/testActualClassTags.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60242.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60243.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60242.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60243.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60243 18032 mightBeASquare should be implemented in LargePositiveInteger https://pharo.fogbugz.com/f/cases/18032 19154 Move to RPackage logic to retrieve actual class tags https://pharo.fogbugz.com/f/cases/19154 19100 Senders of with Full closures https://pharo.fogbugz.com/f/cases/19100 http://files.pharo.org/image/60/60243.zip

Sept. 30, 2016

Re: [Pharo-dev] Slides online: "Perfection & Feedback Loops" talk from esug

by Marcus Denker

Hi, - I merged the annotations with the main slides set using annotation sides (thanks to Oscar for that idea!) - The Video is online on youtube, too. http://www.slideshare.net/MarcusDenker/perfection- feedback-loops-or-why-worse-is-better-65540840 Marcus On Fri, Sep 2, 2016 at 8:38 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > 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-worse-is-better-65540840 > > 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 -- -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

Sept. 30, 2016

CfP: OOPS @ SAC 2017, deadline extended to October 7th, 2016

by Nick Papoylias

========================================================= ***** SUBMISSION DEADLINE EXTENDED: October 7, 2016 ***** ========================================================= ************************************************** OOPS 2017 Call for Papers Object-Oriented Programming Languages and Systems http://oops.disi.unige.it/OOPS17 ************************************************** Technical Track at the 32nd ACM Symposium on Applied Computing, SAC 2017 http://www.acm.org/conferences/sac/sac2017 April 3 - 7, 2017 Marrakesh, Morocco - Important Dates Submission of regular papers and SRC abstracts October 7, 2016 (final extended deadline) Paper and SRC notifications November 18, 2016 Paper and SRC camera-ready copies December 2, 2016 Author registration December 10, 2016 SAC 2017 April 3 - 7, 2017 - Track Chair Davide Ancona (davide.ancona(a)unige.it) DIBRIS, University of Genova, Italy - SAC 2017 For the past thirty one years, the ACM Symposium on Applied Computing (SAC) has been a primary gathering forum for applied computer scientists, computer engineers, software engineers, and application developers from around the world. SAC 2017 is sponsored by the ACM Special Interest Group on Applied Computing (SIGAPP) and is hosted by the University of Quebec at Montreal, Canada; University Cadi Ayyad (UCA) of Marrakech, Morocco; National School of Engineering in Rabat (EMI), Rabat, Morocco; and National School of Applied Sciences (ENSA) of Kenitra, Morocco. - Call For Student Research Abstracts Graduate students seeking feedback from the scientific community on their research ideas are invited to submit original abstracts of their research work in areas of experimental computing and application development related to SAC 2017 Tracks. The Student Research Competition (SRC) Program is designed to provide graduate students the opportunity to meet and exchange ideas with researchers and practitioners in their areas of interest. - OOPS Track: Aims and Topics Object-oriented programming (OOP) has become the mainstream programming paradigm for developing complex software systems in most application domains. However, existing OO languages and platforms need to evolve to meet the continuous demand for new abstractions, features, and tools able to reduce the time, effort, and cost of creating object-oriented software systems, and improving their performance, quality and usability. To this aim, OOPS is seeking for research advances bringing benefits in all those typical aspects of software development, such as modeling, prototyping, design, implementation, concurrency and distribution, code generation, analysis, verification, testing, debugging, evaluation, deployment, maintenance, reuse, and software evolution and adaptation. The specific topics of interest for the OOPS track include, but are not limited to, the following: * Aspects and components * Code generation, and optimization, just-in-time compilation * Context-oriented programming * Databases and persistence * Distribution and concurrency * Dynamic and scripting languages * Evaluation * Feature Oriented Software Development and Programming * Formal verification * Internet of Things technology and programming * Integration with other paradigms * Interoperability, versioning and software evolution and adaptation * Language design and implementation * Modular and generic programming * Reflection, meta-programming * Runtime verification * Secure and dependable software * Static analysis * Testing and debugging * Type systems and type inference * Virtual machines OOPS offers a great opportunity to the OOP community to gain visibility, and to exploit the inter-disciplinary nature of SAC. - Submission Instructions Prospective papers should be submitted to the track in pdf format using the START submission system for regular and SRC papers available through the SAC 2017 home page. Submission of the same paper to multiple tracks is not allowed; all papers should represent original and previously unpublished works that are currently not under review in any conference or journal. Both basic and applied research papers are welcome. SAC 2017 will use double-blind reviewing; to facilitate this, author name(s) and institution(s) must be omitted, and references to authors' own related work should be in the third person. The format of the paper must adhere to the sig-alternate style. Full papers are limited to 6 pages with the option for up to 2 additional pages (max of 8 pages) at extra charge (80 USD per page). Posters are limited to 3 pages with the option for up to 1 additional page (max of 4 pages) at extra charge (80 USD). The length of the SRC abstracts is 2 pages with no additional pages at extra charge. Papers that fall short the above requirements are subjected to rejection. All papers must be submitted by October 7, 2016. For more information please visit the SAC 2017 home page. - Proceedings Accepted papers will be published by ACM in the annual conference proceedings. Accepted posters will be published as extended abstracts in the same proceedings. Paper registration is required, allowing the inclusion of the paper/poster in the conference proceedings. An author or a proxy attending SAC MUST present the paper. This is a requirement for the paper/poster to be included in the ACM/IEEE digital library. No-show of scheduled papers and posters will result in excluding them from the ACM/IEEE digital library. Student registration is only intended to encourage student attendance and does not cover inclusion of papers/posters in the conference proceedings. Finally, following the tradition of the past OOPS editions, depending on the quality and the overall number of accepted papers, authors of selected papers will be invited to submit an extended version for a journal special issue, after the conference.

Sept. 30, 2016

Re: [Pharo-dev] Getting Pharo to Mars?

by philippe.back＠highoctane.be

I am already working in an ESA oroject. Le 30 sept. 2016 00:05, "Richard Sargent" < richard.sargent(a)gemtalksystems.com> a Ã©crit : > ClÃ©ment Bera-4 wrote > > The first thing is to get naturalised as a US citizen. > > I think you would be much further ahead to find someone who works for the > ESA. > (Or maybe approach the ESA itself directly!) > > > > > It seems that the space market has been opened to private companies in > the > > US, but they're still quite skeptical about sharing knowledge with non > > american citizens. If you want to work with Space X, you have either to > be > > an american citizen or have something they really really really want to > > convince them to work with you (and even so, it's likely your native > > country matters). > > > > Quoting their website: > > > > *To conform to U.S. Government space technology export regulations, > > applicant must be a U.S. citizen, lawful permanent resident of the U.S., > > protected individual as defined by 8 U.S.C. 1324b(a)(3), or eligible to > > obtain the required authorizations from the U.S. Department of State. > > Learn > > more about ITAR here.* > > > > > > > > On Thu, Sep 29, 2016 at 6:27 AM, > > > phil@ > > > < > > > phil@ > > > > > > wrote: > > > >> Given > >> > >> http://waitbutwhy.com/2016/09/spacexs-big-fking-rocket-the- > full-story.html > >> > >> we should find some way to get Pharo into it somehow. > >> > >> Anyone having ideas on how to do that? > >> > >> Phil > >> > > > > > > -- > View this message in context: http://forum.world.st/Getting-Pharo-to-Mars- > tp4917390p4917478.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

Sept. 29, 2016

Re: [Pharo-dev] Getting Pharo to Mars?

by Richard Sargent

ClÃ©ment Bera-4 wrote > The first thing is to get naturalised as a US citizen. I think you would be much further ahead to find someone who works for the ESA. (Or maybe approach the ESA itself directly!) > It seems that the space market has been opened to private companies in the > US, but they're still quite skeptical about sharing knowledge with non > american citizens. If you want to work with Space X, you have either to be > an american citizen or have something they really really really want to > convince them to work with you (and even so, it's likely your native > country matters). > > Quoting their website: > > *To conform to U.S. Government space technology export regulations, > applicant must be a U.S. citizen, lawful permanent resident of the U.S., > protected individual as defined by 8 U.S.C. 1324b(a)(3), or eligible to > obtain the required authorizations from the U.S. Department of State. > Learn > more about ITAR here.* > > > > On Thu, Sep 29, 2016 at 6:27 AM, > phil@ > < > phil@ > > > wrote: > >> Given >> >> http://waitbutwhy.com/2016/09/spacexs-big-fking-rocket-the-full-story.html >> >> we should find some way to get Pharo into it somehow. >> >> Anyone having ideas on how to do that? >> >> Phil >> -- View this message in context: http://forum.world.st/Getting-Pharo-to-Mars-tp4917390p4917478.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 29, 2016

Re: [Pharo-dev] Getting Pharo to Mars?

by phil＠highoctane.be

I do not want to go to Mars, just wanting to get Pharo in the vehicle somehow. On Thu, Sep 29, 2016 at 7:16 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > The first thing is to get naturalised as a US citizen. > > It seems that the space market has been opened to private companies in the > US, but they're still quite skeptical about sharing knowledge with non > american citizens. If you want to work with Space X, you have either to be > an american citizen or have something they really really really want to > convince them to work with you (and even so, it's likely your native > country matters). > > Quoting their website: > > *To conform to U.S. Government space technology export regulations, > applicant must be a U.S. citizen, lawful permanent resident of the U.S., > protected individual as defined by 8 U.S.C. 1324b(a)(3), or eligible to > obtain the required authorizations from the U.S. Department of State. Learn > more about ITAR here.* > > > > On Thu, Sep 29, 2016 at 6:27 AM, phil(a)highoctane.be <phil(a)highoctane.be> > wrote: > >> Given >> >> http://waitbutwhy.com/2016/09/spacexs-big-fking-rocket-the-f >> ull-story.html >> >> we should find some way to get Pharo into it somehow. >> >> Anyone having ideas on how to do that? >> >> Phil >> > >

Sept. 29, 2016

Re: [Pharo-dev] Getting Pharo to Mars?

by Dimitris Chloupis

Its highly unlikely that SpaceX will be the only one to go to Mars , as its curently planned is it will take 7+ years best case scenario to send first humans to Mars. Thats plenty of time for other USA and non USA companies to join in. Plus there is no prediction where technology will be in a decade. Include to this that US is 1/4th of the global economy this story has just started to unveil. Include also the fact that our ever growing population is unstoppable, this alone is a huge motivating factor because the alternative is a humanitarian , ecological and economy crisis human race has ever experienced. Pharo will get to Mars since laptops will get to Mars eventually :) There is no need to find a way to get it there we already have the technology in place, its just a matter of improving it. On Thu, Sep 29, 2016 at 8:17 AM ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > The first thing is to get naturalised as a US citizen. > > It seems that the space market has been opened to private companies in the > US, but they're still quite skeptical about sharing knowledge with non > american citizens. If you want to work with Space X, you have either to be > an american citizen or have something they really really really want to > convince them to work with you (and even so, it's likely your native > country matters). > > Quoting their website: > > *To conform to U.S. Government space technology export regulations, > applicant must be a U.S. citizen, lawful permanent resident of the U.S., > protected individual as defined by 8 U.S.C. 1324b(a)(3), or eligible to > obtain the required authorizations from the U.S. Department of State. Learn > more about ITAR here.* > > > > On Thu, Sep 29, 2016 at 6:27 AM, phil(a)highoctane.be <phil(a)highoctane.be> > wrote: > >> Given >> >> http://waitbutwhy.com/2016/09/spacexs-big-fking-rocket-the-full-story.html >> >> we should find some way to get Pharo into it somehow. >> >> Anyone having ideas on how to do that? >> >> Phil >> > >

Sept. 29, 2016

Re: [Pharo-dev] Getting Pharo to Mars?

by ClÃ©ment Bera

The first thing is to get naturalised as a US citizen. It seems that the space market has been opened to private companies in the US, but they're still quite skeptical about sharing knowledge with non american citizens. If you want to work with Space X, you have either to be an american citizen or have something they really really really want to convince them to work with you (and even so, it's likely your native country matters). Quoting their website: *To conform to U.S. Government space technology export regulations, applicant must be a U.S. citizen, lawful permanent resident of the U.S., protected individual as defined by 8 U.S.C. 1324b(a)(3), or eligible to obtain the required authorizations from the U.S. Department of State. Learn more about ITAR here.* On Thu, Sep 29, 2016 at 6:27 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > Given > > http://waitbutwhy.com/2016/09/spacexs-big-fking-rocket-the-full-story.html > > we should find some way to get Pharo into it somehow. > > Anyone having ideas on how to do that? > > Phil >

Sept. 29, 2016

Re: [Pharo-dev] stdev

by stepharo

Do not worry this is so complex to define that I will define my own in my own class for myself. Like that I will be able to use the names I want for my projects. You see in Rectangle we have a protocol named fmp and I was sad to see it. I would have preferred wtf Stef Le 29/9/16 Ã 02:52, Ben Coman a Ã©crit : > On Thu, Sep 29, 2016 at 1:50 AM, stepharo <stepharo(a)free.fr> wrote: >> Hi guys >> >> >> is stdev a typical name for standardDeviation? >> >> Because I found it sad to have mean and stdev instead of mean and >> standardDeviation. > stdev() or std() seems fairly typical. Doesn't mean we can't be > different. One thing though is that the typical function is what > newcomers would search on, which makes me consider it could be useful > in Spotter to have a mapping from functions in other languages to > Pharo methods. So a user would type stdev and the top hit would be > standardDeviation. > > MathCAD: stdev() > http://www.phys.uconn.edu/~Eyler/phys258/P/stats.pdf > > Excel: stdev() > http://www.wikihow.com/Calculate-Standard-Deviation-in-Excel > > Python 3.4: stdev() > http://stackoverflow.com/questions/15389768/standard-deviation-of-a-list > > NumPy: std() > http://stackoverflow.com/questions/15389768/standard-deviation-of-a-list > > Mathworks: std() > https://au.mathworks.com/help/matlab/ref/std.html?s_tid=gn_loc_drop > > SAS: std() > http://blogs.sas.com/content/iml/2012/03/05/functions-to-know-the-mean-var-… > > cheers -ben > >

Sept. 29, 2016