- Pharo-users - lists.pharo.org

About asSymbol message , some questions in my mind
by lb Feb. 11, 2017

Feb. 11, 2017

Hi, I know Symbol is subclass of String. Any string object can become symbol object by sending 'asSymbol' message.. I think symbol must has its meaning in comon use, so the symbol should be composed of alphabet or number âwithout spaceâ. BUT There are not compliant below 1. ' ' asSymbol >>>> no meaning 2. '$%%&' asSymbol >>>> no meaning 3. 'sign' asSymbol = 'sign ' asSymbol >>> false because of space. 3. ' one two three ' asSymbol >>> I think It should become three symbols = #one, #two, #three Maybe my understanding is wrong. Bing Liang

2 1

Final rush for submitting GSOC proposal - Need your help
by Serge Stinckwich Feb. 10, 2017

Feb. 10, 2017

Hi all, we are currently working with Alexandre to submit the gsoc proposal to Google. I was a little bit busy with my lectures and I didn't check the current proposals available here: http://gsoc.pharo.org/ but all the projects are coming from RMOD team, but having all the projects proposal coming from the same place might be perceived negatively from Google. Can we add more projects from previous gsoc form other people also ? We have only one hour to polish the list. Thank you for your help. -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

6 11

[Teapot and Voyage] sending over the voyageId
by sergio ruiz Feb. 10, 2017

Feb. 10, 2017

I am working on the U of the CRUD part of my Teapot/Voyage REST interface, and found that I cannot get the voyageId to be delivered as part of the REST response.. in order to do RUD, I will need that in the feed. the problem is that NeoJSON uses the instance variables to JSON encode the object. to circumvent this, i made an instance variable called âidâ.. and made an accessor like so: id ^ self voyageId value so i can do something like station id -> â23434234234243423432â but when i inspect the object, or send it back from voyage, id is nil.. rather than mirror voyageâs _id, i would like access to it in JSON encoding, but i can see that might be a problem.. any ideas? thanks! ---- peace, sergio photographer, journalist, visionary Public Key:Â http://bit.ly/29z9fG0 #BitMessageÂ BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.Village-Buzz.com http://www.ThoseOptimizeGuys.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

2 2

Pharo Object Model
by Oleksandr Zaytsev Feb. 10, 2017

Feb. 10, 2017

Hello, I'm trying to understand the logic behind The Pharo Object Model. Rule 3 states that every class in Pharo has a subclass. I was expecting some cool loop, like in the case of Metaclass, which is an instance and also a class of Metaclass class. But ProtoObject, which is the root of an inheritance hierarchy does not seem to have a superclass (ProtoObject superclass answers nil, which is not a class). Does this mean that Pharo Object Model is inconsistent? Is ProtoObject an exception of the third rule? If you think about it, an inheritance hierarchy can't have a loop, because otherwise, when looking for a nonexistent method in superclasses, Pharo would be stuck in that loop. So why is there even a loop in instance hierarchy (Metaclass class)? Does it have a purpose, or is it there only to satisfy the second rule of the Object Model? Because if the consistency of third rule can not be satisfied, wouldn't it be better to add two exceptions to the model? Please correct me if my understanding or reasoning is wrong. Thanks!

2 1

GSOC Pharo application done
by Serge Stinckwich Feb. 10, 2017

Feb. 10, 2017

Dear all, thanks to the efforts of Jigyasa Grover, Yuriy Tymchuk and Alexandre Bergel, , we were able to have a GSOC 2017 application for the Pharo Consortium. This is only the first phase. If we are selected by Google, they will give some slots for students. We have a list of projects for GSOC here : http://gsoc.pharo.org/ If you have more ideas, please send them to me or send a PR on : https://github.com/pharo-project/pharo-project-proposals/blob/master/Topics… Try to describe your project idea with 10-15 lines maximum. The ideas is not too much projects proposals but to find important projects for the Pharo community (i.e that will have some impact for the community) with the support of the appropriate mentors. I would like to have maximum 2-3 projects for each mentors. Thank you. Cheers, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

1 0

Re: [Pharo-users] Problem in installing Pharo â Solved thanks to you
by Ben Coman Feb. 10, 2017

Feb. 10, 2017

Thanks for the followup. Great to hear its working. Just a minor one thing. Can you see if your email client has a "Text Only" send feature that can apply to the mail list? Your font ends up too large & bold here (its nice to have all the mails a standard size), and some of the list archiving software interacts badly with formatted text. Hope you have fun with Pharo and we see you back on the list with more questions soon. cheers -ben On Fri, Feb 10, 2017 at 6:59 AM, Mark Neagu <mark(a)mneagu.fr> wrote: > Hi! > > Several nice persons mailed me to help: Sven, Dimitris, Ben, Nicole. > > Now everything works fine and I'm studying the tutorial. > > You people are really helpful and there is no doubt the PHARO language is > promised to a briliant future thanks to its qualities and to your dedication > at making it work. > > Best regards, > > Mark

1 0

Problem in installing Pharo â Solved thanks to you
by Mark Neagu Feb. 9, 2017

Feb. 9, 2017

1 0

Problem in installing Pharo
by Mark Neagu Feb. 9, 2017

Feb. 9, 2017

5 5

[Pharo-user] Does SSDP package supposed to work on Pharo 6?
by Denis Kudriashov Feb. 9, 2017

Feb. 9, 2017

Hi. Question probably to Henrik. I try SSDP <http://smalltalkhub.com/#!/~henriksp/SSDP> on latest Pharo 6 and code for server and client signal primitive error on #primGetAddressInfoHost:service:flags:family:type:protocol:. Do you know about such problems? Does it VM or code needs to be adapted for Pharo6?

2 2

1st CfP: SLE 2017 (10th ACM SIGPLAN International Conference on Software Language Engineering)
by Andrei Chis Feb. 9, 2017

Feb. 9, 2017

======================================================================== **Call for Papers** 10th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2017) 23-24 October 2017, Vancouver, Canada (Co-located with SPLASH 2017) General chair: Benoit Combemale, University of Rennes 1, France Program co-chairs: Marjan Mernik, University of Maribor, Slovenia Bernhard Rumpe, RWTH Aachen University, Germany Artifact evaluation chairs Tanja Mayerhofer, TU Wien, Austria Laurence Tratt, King's College London, UK http://conf.researchr.org/track/sle-2017/sle-2017-papers http://www.sleconf.org/2017 Follow us on twitter: https://twitter.com/sleconf ======================================================================== Software Language Engineering (SLE) is the application of systematic, disciplined, and measurable approaches to the development, use, deployment, and maintenance of software languages. The term "software language" is used broadly, and includes: general-purpose programming languages; domain-specific languages (e.g. BPMN, Simulink, Modelica); modeling and metamodeling languages (e.g. SysML and UML); data models and ontologies (e.g. XML-based and OWL-based languages and vocabularies). ### Important Dates Fri 2 Jun 2017 - Abstract Submission Fri 9 Jun 2017 - Paper Submission Fri 4 Aug 2017 - Author Notification Thu 10 Aug 2017 - Artifact Submission Fri 1 Sep 2017 - Artifact Notification Fri 8 Sep 2017 - Camera Ready Deadline Sun 22 Oct - SLE workshops Mon 23 Oct - Tue 24 Oct 2017 - SLE Conference ### Topics of Interest SLE aims to be broad-minded and inclusive about relevance and scope. We solicit high-quality contributions in areas ranging from theoretical and conceptual contributions to tools, techniques, and frameworks in the domain of language engineering. Topics relevant to SLE cover generic aspects of software languages development rather than aspects of engineering a specific language. In particular, SLE is interested in principled engineering approaches and techniques in the following areas: * Language Design and Implementation * Approaches and methodologies for language design * Static semantics (e.g., design rules, well-formedness constraints) * Techniques for behavioral / executable semantics * Generative approaches (incl. code synthesis, compilation) * Meta-languages, meta-tools, language workbenches * Language Validation * Verification and formal methods for languages * Testing techniques for languages * Simulation techniques for languages * Language Integration and Composition * Coordination of heterogeneous languages and tools * Mappings between languages (incl. transformation languages) * Traceability between languages * Deployment of languages to different platforms * Language Maintenance * Software language reuse * Language evolution * Language families and variability * Domain-specific approaches for any aspects of SLE (design, implementation, validation, maintenance) * Empirical evaluation and experience reports of language engineering tools * User studies evaluating usability * Performance benchmarks * Industrial applications ### Types of Submissions * **Research papers**: These should report a substantial research contribution to SLE or successful application of SLE techniques or both. Full paper submissions must not exceed 12 pages including bibliography in ACM SIGPLAN conference style (http://www.sigplan.org/Resources/Author/) * **Tool papers**: Because of SLE's interest in tools, we seek papers that present software tools related to the field of SLE. Selection criteria include originality of the tool, its innovative aspects, and relevance to SLE. Any of the SLE topics of interest are appropriate areas for tool demonstrations. Submissions must provide a tool description of 4 pages including bibliography in ACM SIGPLAN conference style ( http://www.sigplan.org/Resources/Author/) and a demonstration outline including screenshots of up to 6 pages. Tool demonstrations must have the keywords âTool Demoâ or âTool Demonstrationâ in the title. The 4-page tool description will, if the demonstration is accepted, be published in the proceedings. The 6-page demonstration outline will be used by the program committee only for evaluating the submission. * **Industrial papers**: These should describe real-world application scenarios of SLE in industry, explained in their context with an analysis of the challenges that were overcome and the lessons which the audience can learn from this experience. Industry paper submissions must not exceed 6 pages including bibliography in ACM SIGPLAN conference style ( http://www.sigplan.org/Resources/Author/) * **New ideas / vision papers**: New ideas papers should describe new, non-conventional SLE research approaches that depart from standard practice. They are intended to describe well-defined research ideas that are at an early stage of investigation. Vision papers are intended to present new unifying theories about existing SLE research that can lead to the development of new technologies or approaches. New ideas / vision papers must not exceed 4 pages including bibliography in ACM SIGPLAN conference style (http://www.sigplan.org/Resources/Author/) ### Artifact evaluation Authors of accepted papers at SLE 2017 are encouraged to submit their experiment results used for underpinning research statements to an artifact evaluation process. This submission is voluntary and will not influence the final decision regarding the papers. Papers that go through the Artifact Evaluation process successfully receive a seal of approval printed on the first page of the paper in the proceedings. Authors of papers with accepted artifacts are encouraged to make these materials publicly available upon publication of the proceedings, by including them as "source materials" in the ACM Digital Library. ### Publications All submitted papers will be reviewed by at least three members of the program committee. All accepted papers, including tool papers, industrial papers and new ideas / vision papers will be published in ACM Digital Library. Selected accepted papers will be invited to a special issue of the Computer Languages, Systems and Structures (COMLAN) journal. ### Awards * **Distinguished paper**: Award for most notable paper, as determined by the PC chairs based on the recommendations of the program committee. * **Distinguished reviewer**: Award for distinguished reviewer, as determined by the PC chairs using feedback from the authors. * **Distinguished artifact**: Award for the artifact most significantly exceeding expectations, as determined by the AEC chairs based on the recommendations of the artifact evaluation committee. ### Program Committee Marjan Mernik (co-chair), University of Maribor, Slovenia Bernhard Rumpe (co-chair), RWTH Aachen University, Germany Mark van den Brand, TU Eindhoven, The Netherlands Ruth Breu, University of Innsbruck, Austria Jordi Cabot, ICREA, Spain Walter Cazzola, University of Milan, Italy Marsha Chechik, University of Toronto, Canada Tony Clark, Middlesex University, UK Tom Dinkelaker, Ericsson, Germany Bernd Fischer, Stellenbosch University, South Africa Sebastian Gerard, CEA, France Jeff Gray, University of Alabama, USA Esther Guerra, Autonomous University of Madrid, Spain Michael Homer, Victoria University of Wellington, New Zealand Ralf LÃ¤mmel, University of Koblenz-Landau, Germany Tihamer Levendovszky, Microsoft, USA Gunter Mussbacher, McGill University, Canada Terence Parr, University of San Francisco, USA Jaroslav PorubÃ¤n, University of KoÅ¡ice, Slovakia Jan Ringert, Tel Aviv University, Israel Julia Rubin, University of British Columbia, Canada Tony Sloane, Macquarie University, Australia Eugene Syriani, University of Montreal, Canada Emma SÃ¶derberg, Google, Denmark Eric Van Wyk, University of Minnesota, USA Jurgen Vinju, CWI, Netherlands Eric Walkingshaw, Oregon State University, USA Andreas Wortmann, RWTH Aachen University, Germany Tian Zhang, Nanjing University, China ### Contact For any question, please contact the organizers via email: sle2017(a)inria.fr

1 0