August 2017 - Pharo-dev - lists.pharo.org

[CfP Deadline Extension] Workshop on Meta-Programming Techniques and Reflection, Deadline August 20
by Stefan Marr Aug. 16, 2017

Aug. 16, 2017

Call for Papers: Metaâ17 ======================== Workshop on Meta-Programming Techniques and Reflection Co-located with SPLASH 2017 October 22, 2017, Vancouver, Canada Twitter @MetaAtSPLASH http://2017.splashcon.org/track/meta-2017 The heterogeneity of mobile computing, cloud applications, multicore architectures, and other systems leads to increasing complexity of software and requires new approaches to programming languages and software engineering tools. To manage the complexity, we require generic solutions that can be adapted to specific application domains or use cases, making metaprogramming an important topic of research once more. However, the challenges with metaprogramming are still manifold. They start with fundamental issues such as typing of reflective programs, continue with practical concerns such as performance and tooling, and reach into the empirical field to understand how metaprogramming is used and how it affects software maintainability. Thus, while industry accepted metaprogramming on a wide scale with Ruby, Scala, JavaScript and others, academia still needs to answer a wide range of questions to bring it to the same level of convenience, tooling, and programming styles to cope with the increasing complexity of software systems. This workshop aims to explore meta-level technologies that help tackling the heterogeneity, scalability and openness requirements of emerging computations platforms. ### Topics of Interest The workshop is a venue for all approaches that embrace metaprogramming: - from static to dynamic techniques - reflection, meta-level architectures, staging, open language runtimes applications to middleware, frameworks, and DSLs - optimization techniques to minimize runtime overhead - contract systems, or typing of reflective programs reflection and metaobject protocols to enable tooling - case studies and evaluation of such techniques, e.g., to build applications, language extensions, or tools - empirical evaluation of metaprogramming solutions - security in reflective systems and capability-based designs - meta-level architectures and reflective middleware for modern runtime platforms (e.g. IoT, cyber-physical systems, mobile/cloud/grid computing, etc) - surveys, conceptualization, and taxonomization of existing approaches In short, we invite contributions to the workshop on a wide range of topics related to design, implementation, and application of reflective APIs and meta-programming techniques, as well as empirical studies and typing for such systems and languages. ### Workshop Format and Submissions This workshop welcomes the presentation of new ideas and emerging problems as well as mature work as part of a mini-conference format. Furthermore, we plan interactive brainstorming and demonstration sessions between the formal presentations to enable an active exchange of ideas. Therefore, we seek the following kinds of publications: â¢ technical paper: max. 8 pages, excluding references â¢ position and work-in-progress paper: 1-4 pages, excluding references â¢ technology demos or a posters: 1-page abstract All papers are to be submitted using the SIGPLAN acmart style. Please use the provided double-column Latex or Word templates. For the submission, please use the submission system at: https://meta17.hotcrp.com/ The workshop technical papers will be published in the ACM DL, if not requested otherwise by the authors. Thus, they will be part of SPLASH workshop proceedings. Demos, posters, position and work-in-progress papers can be submitted on a second, later deadline to discuss the latest results and current work and wonât be included in the ACM DL proceedings. ### Important Dates Abstract Submission: 07 August 2017 Paper Submission: 20 August 2017 Author Notification: 06 September 2017 Position/WIP Paper Deadline: 08 September 2017 Camera Ready Deadline: 18 September 2017 Position/WIP Notification: 21 September 2017 ### Program Committee The program committee consists of the organizers and the following reviewers: Anya Helen Bagge, University of Bergen, Norway Daniele Bonetta, Oracle Labs, Austria Nicolas Cardozo, Universidad de los Andes, Colombia Sebastian Erdweg, TU Delf, The Nederlands Robert Hirschfeld, HPI, Germany Roberto Ierusalimschy, PUC-Rio, Brazil Pablo Inostroza, CWI, The Nederlands Kim Mens, Universite Catholique de Louvain, Belgium Cyrus Omar, Carnegie Mellon University, USA Guillermo Polito, CNRS, France Tiark Rompf, Purdue University, USA Tom Van Cutsem, Nokia Bell Labs, Belgium Takuo Watanabe, Tokyo Institute of Technology, Japan ### Workshop Organizers Shigeru Chiba, University of Tokyo Elisa Gonzalez Boix, Vrije Universiteit Brussel Stefan Marr, Johannes Kepler University Linz ### Contact information For further inquires, do not hesitate to contact the organizers via meta AT soft.vub.ac.be http://2017.splashcon.org/track/meta-2017 -- Stefan Marr Johannes Kepler UniversitÃ¤t Linz http://stefan-marr.de/research/

2 4

Issue 20309 - Startup should run always in a fresh process
by Guillermo Polito Aug. 16, 2017

Aug. 16, 2017

Hi all, I'm proposing a kind-of critical change that I believe is very good for the health of the system: I want that the startup of the system runs in maximum priority and becomes non-interruptable. Right now, when you save your image, the shutdown and startup are run in the same priority than the process that triggered the save (usually the ui or the command line, priority 40). This can cause lots of problems and race conditions: processes with higher priorities can interrupt the shutdown/startup and try to do something while the system is unstable. As a side effect also, when you use extensively the command line, you start stacking startup contexts from old sessions: ... session 3 ctxt 4 <- This guy makes a save and a new session starts session 3 ctxt 3 session 3 ctxt 2 session 3 ctxt 1 session 2 ctxt 4 <- This guy makes a save and a new session starts session 2 ctxt 3 session 2 ctxt 2 session 2 ctxt 1 session 1 ctxt 4 <- This guy makes a save and a new session starts session 1 ctxt 3 session 1 ctxt 2 session 1 ctxt 1 Old contexts are never collected, and the objects they referenced neither. To fix these two problems I propose to do every image save/session start in a new process in maximum priority. That way, other process should not be able to interrupt the startup process. Moreover, every session shutdown/startup should happen in a new clean process, to avoid the session stacking. For normal users, this should have no side effect at all. This change will have a good impact on people working on the debugger and the stack such as fueling-out the stack because they will have a cleaner stack. There is however a side-effect/design point to consider: startup actions should be quick to run. If a startup action requires to run a long-running action such as starting a server or managing a command line action, that should run in a separate process with lower priority (usually userPriority). In other words, the startup action should create a new process managing its action. If you want to review (and I'd be glad) Pull request: https://github.com/pharo-project/pharo/pull/198 Fogbugz issue: https://pharo.fogbugz.com/f/cases/20309 Current validation going on: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… Guille -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

6 18

[Pharo 70 ] build 38 - PR 199 FileReference-size-needs-a-comment
by Stephane Ducasse Aug. 16, 2017

Aug. 16, 2017

https://pharo.fogbugz.com/f/cases/20269/FileReference-size-needs-a-comment https://github.com/pharo-project/pharo/pull/199

1 0

[Pharo 70 ] build 37 - PR 206 File names should not be canonicalised by default
by Stephane Ducasse Aug. 16, 2017

Aug. 16, 2017

https://pharo.fogbugz.com/f/cases/20307/File-names-should-not-be-canonicali… https://github.com/pharo-project/pharo/pull/206

1 0

[Pharo 70 ] build 36 - PR 204 Improve-comment-of-SmallDictionary
by Stephane Ducasse Aug. 15, 2017

Aug. 15, 2017

https://pharo.fogbugz.com/f/cases/20091/Improve-comment-of-SmallDictionary https://github.com/pharo-project/pharo/pull/204

1 0

Trying to build Mac VM - ld: library not found for -lssl
by Todd Blanchard Aug. 15, 2017

Aug. 15, 2017

Git cloned, cd to build.macosxxx/pharo.cog.spur ./mvm -A Either 32 or 64 bit builds dies trying to build libSqueakSSL with library not found for -lssl. Homebrew doesn't seem to have an entry for libssl. Stumped. -Todd Blanchard

2 3

New line on command line
by Rajula Vineet Aug. 15, 2017

Aug. 15, 2017

Hey, I have been trying to print on the command line as a part of my handler implementation. I have been using `nextPutAll: aString;lf.` Apparently, 'lf' does not seem to work. I tried 'cr' too. I am using the latest 7.0 Pharo-vm and pharo image. I tried 'OSPlatform current lineEnding' as suggested by Clement Mastin. But, when I used the 6.0 version the 'lf' message is working fine. Please find the attached image which demonstrates the same. The left terminal is of version 7.0, right one is of 6.0. Can someone help me out with this? <http://forum.world.st/file/n4960327/Screenshot_from_2017-08-11_00-04-29.png> -- View this message in context: http://forum.world.st/New-line-on-command-line-tp4960327.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

2 5

vm crash when using rairedTo: with fractions
by Andrei Chis Aug. 15, 2017

Aug. 15, 2017

Hi, I was executing this code '(2009/2000) ** (3958333/100000)' with the Pharo6.1 distribution and the vm crashed with she stack attached below. Tried it on both mac and windows 10. Seems that #raisedTo: has a special case for fractions that ends up calling #nthRoot: like '2009 nthRoot: 100000' leading to the crash. Cheers, Andrei 0xaddeac M LargePositiveInteger(Integer)>quo: 0x314093e8: a(n) LargePositiveInteger 0xaddec8 M LargePositiveInteger(LargeInteger)>quo: 0x314093e8: a(n) LargePositiveInteger 0xaddee8 M LargePositiveInteger(Integer)>// 0x314093e8: a(n) LargePositiveInteger 0xaddf04 M LargePositiveInteger(LargeInteger)>// 0x314093e8: a(n) LargePositiveInteger 0xaddf34 I LargePositiveInteger(Integer)>nthRootTruncated: 0x30cc8350: a(n) LargePositiveInteger 0xaddf5c I LargePositiveInteger(Integer)>nthRootRounded: 0x30cc8350: a(n) LargePositiveInteger 0xaddf88 I SmallInteger(Integer)>nthRoot: 0xfb3=2009 0xaddfb4 I Fraction>nthRoot: 0x4f9a940: a(n) Fraction 0xaddfd8 I Fraction(Number)>raisedTo: 0x4f9a940: a(n) Fraction 0xaddffc I Fraction(Number)>** 0x4f9a940: a(n) Fraction 0xade018 M UndefinedObject>DoIt 0x5fe5d00: a(n) UndefinedObject 0xade048 I OpalCompiler>evaluate 0x4f9a998: a(n) OpalCompiler 0xade074 I RubSmalltalkEditor>evaluate:andDo: 0x305e5878: a(n) RubSmalltalkEditor 0xade09c I RubSmalltalkEditor>highlightEvaluateAndDo: 0x305e5878: a(n) RubSmalltalkEditor 0xade0b8 M GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>popupPrint 0x3062fdc8: a(n) GLMMorphicPharoScri enderer 0xade0d8 I MorphicAlarm(MessageSend)>value 0x4f9ab20: a(n) MorphicAlarm 0xade0f4 M MorphicAlarm>value: 0x4f9ab20: a(n) MorphicAlarm 0xade114 M WorldState>triggerAlarmsBefore: 0x71bb5e0: a(n) WorldState 0xade140 M WorldState>runLocalStepMethodsIn: 0x71bb5e0: a(n) WorldState 0xade164 M WorldState>runStepMethodsIn: 0x71bb5e0: a(n) WorldState 0xade180 M WorldMorph>runStepMethods 0x6ab7778: a(n) WorldMorph 0xade198 M WorldState>doOneCycleNowFor: 0x71bb5e0: a(n) WorldState 0xade1b4 M WorldState>doOneCycleFor: 0x71bb5e0: a(n) WorldState 0xade1d0 M WorldMorph>doOneCycle 0x6ab7778: a(n) WorldMorph 0xade1e8 M WorldMorph class>doOneCycle 0x6a9f960: a(n) WorldMorph class 0xade200 M [] in MorphicUIManager>spawnNewProcess 0x2cc88718: a(n) MorphicUIManager 0xade220 I [] in BlockClosure>newProcess 0x2f178150: a(n) BlockClosure

6 8

Re: [Pharo-dev] [squeak-dev] Serializers/Encoders
by henry Aug. 15, 2017

Aug. 15, 2017

After more research, including TJSON, we realized the choice of ASN.1 at the lower layer is exactly what could continue at the higher layer, with more work to expand ASN.1 capability. Sorry for the huge 1 MB image. The classes in Fuel are, beginning with serialization or demanifestation: Serializer * Serialization * Analyzer * Encoder ** Analysis ***[] Clusterizations { handling source-substitutions } onthe wire these clusterizations are encoded. On the receiving side, the process of materialization or manifestation is straightforwards, activate the clusterizations, with a decoder forming a proxy instance graph, then annealing them as references. I think these are the points of substitution, but I am honestly guessing from a faint memory. Materializer * Materialization * Decoder (***[]) on the wire clusterizations... I really want/need/desire to dive into where and how substitutions are occurring, on source-side and destination. This in order to add this ability to the ASN.1 system. In ASN.1 specification, there is a mechanism to specify external structures and expand the definitional nature of ASN.1. ASN.1 carries a notation and we have the start of a DefinitionModel. Fitting this into Fuel would be sweet and it may be straightforward: break the graph walking of ASN.1 just have the target encoding, in nesting: so pre and post, and change the Fuel Encoder/Decoder. I believe that since clusterizations will not pass across, a decode analyzer will be needed. Getting III (Interactive Invocation Interface) support to generate ASN.1 definition models and classes to model them, bi-directionally, will enable the analyzers to setup clusterizations that en/decode properly. Here's to hope that this will be so. Among the varied requirements, the core requirement is passing extended substitutable types/schemas between environments: Squeak - Pharo - Java. I think ASN.1 with its types is the best choice. I have no idea if Bouncy Castle can support external types. I am happy it can do CHOICE, though with manual coding to implement this. Separating the Types in Squeak/Pharo Cryptograghy turns out to be a good choice and interchangeable we hope. I hope this clarifies and illuminates, I am driven to share these thoughts. Warmly, - HH > -------- Original Message -------- > Subject: Re: [squeak-dev] [Pharo-dev] Serializers/Encoders > Local Time: August 14, 2017 6:27 PM > UTC Time: August 14, 2017 10:27 PM > From: henry(a)callistohouse.club > To: Pharo Development List <pharo-dev(a)lists.pharo.org>, Squeak-dev <squeak-dev(a)lists.squeakfoundation.org> > > In further consideration, what seems missing from JSON encoding is an ANY type and a CHOICE type. With these and proper type encoding extension to JSON, we could pass arbitrary types w/o being required to specify a specific decoding structure. I think this is so. Types would be helpful. I found TJSON, which may be good, but no arbitrary types, still. > > I notice JSON decoding is where magic happens and it requires full specification of what is expected. Perhaps there is a way for ANY & CHOICE with a CustomMapper. Contrarily, Fuel does all analysis on encoding, the front side, and encodes the found clusters on-stream so the materialized is lightweight. ASN1MODULES does a little of both with external types but also with ANY & CHOICE. > > In looking at Fuel-Core, here are main classes.., > > - HH > > On Mon, Aug 14, 2017 at 13:44, henry <henry(a)callistohouse.club> wrote: > >> I find I do not necessarily have a specific question regarding a specific implementations, but a higher-level question of feasible solution. I need substitutable, type-relevant JSON encoding, perhaps based upon JSON Schemas. >> >> I am looking at ASN1Modules & types, Fuel clusterings/substitutions and NeoJSON clusters & mappers. Is it feasible to bring all these together? I would use ASN1Types, Fuel graph walking/substitutions and NeoJSON encoding and cluster hooks. >> >> Fuel also has Clusters but I see that Fuel encodes these clusters in each encoding. I am torn about this philosophically: good to have self-describing data encoding, but not suitable for JSON, unless just a type-name extension. Lightweight & robust descriptions? Well, this is all Fuel cluster specs within the encoding really is: a type-specification. >> >> The aspect of NeoJSON that has me wondering is the lack of polymorphism in type-spec lookup and recursive substitution. This is where Fuel shines, I feel. >> >> So what is the vision of the end state encoder? Use ASN1 Types as cluster descriptors, Fuel proxification on materializations and NeoJSON encoding and mappers. >> >> Would you have for me guidances in this area? >> >> - HH

1 1

[ANN] VistaCursor now scalable
by Torsten Bergmann Aug. 14, 2017

Aug. 14, 2017

Hi, Mike Davis asked about changing the cursor size as he runs Pharo with Windows 10 on a Microsoft Surface @ 2736 x 1824 dpi. He discussed on Discord and said that all of the display is well scaled, except the mouse cursor which is too small for him. As the Windows VM supports larger cursors I added some support to my loadable goodie package "VistaCursor" now. So there is now a new setting to scale the provided cursors (see screenshots). Either freshly load the package from catalog or update to "VistaCursors-TorstenBergmann.5" if you want to check this out. This might be also be useful for presentations. Have fun T.

1 0