- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Environment variables encoding ?

by Sven Van Caekenberghe

> On 19 Apr 2018, at 10:21, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Hi, > > I think this problem is not environment variable exclusive. It also affects file paths and others. So far Pharo does not detect the locale to perform the encoding and it should be nice to do it. Sure, it would be nice/good/helpful to detect locale (BTW, don't we have that already more or less). But I would be surprised if an OS API would deliver different encoded data to a process, depending on the locale - I mean in general. That would be setting up things for a huge distaster, IMHO. A modern OS should just deliver UTF-8 (full Unicode data points) and be done with it. > On Tue, Apr 17, 2018 at 10:56 AM, Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> wrote: > Damien Pollet wrote > > It seems macOS normalizes UTF-8 differently from everyone else in file > > names (I think base character + composing instead of precomposed > > codepoint). That might affect PWD. > > For environment variables, even if most sensible platforms should have > > adopted UTF-8 by now, I wouldn't be surprised if there's no official > > encoding whatsoever (i.e. they're just bytes with a 0 at the endâ¦) > > > > On 17 April 2018 at 09:36, Sven Van Caekenberghe < > > > sven@ > > > > wrote: > > > >> Hi, > >> > >> The dictionary > >> > >> OSPlatform current environment > >> > >> contains a copy of the OS's environment variables (more correctly of the > >> VM process), as key/value pairs. > >> > >> These are obtained via the following system calls: > >> > >> on macOS & *nix > >> > >> LIBC environ > >> > >> on Windows > >> > >> KERNEL32 GetEnvironmentStrings > >> > >> It is however a bit unclear how these are encoded. On macOS & *nix that > >> seems to be UTF8, on Windows there are some reports that it appears to be > >> Latin1 - but both might be locale specific, I don't know either way. > >> > >> Does anyone know for sure ? > >> > >> I furthermore think that OSEnvironment and its subclasses, who do this > >> call, should be responsible for decoding the C strings into proper Pharo > >> strings, and not leave that responsibility to its users. > >> > >> Fundamentally, in the following, the decoding is still not done correctly > >> and that is wrong/confusing IMHO. > >> > >> $ FOO=benoÃ®t ./pharo Pharo.image eval 'OSEnvironment current > >> associations' > >> {'TERM_PROGRAM'->'Apple_Terminal'. 'TERM'->'xterm-256color'. > >> 'SHELL'->'/bin/bash'. 'TMPDIR'->'/var/folders/sy/ > >> sndrtj9j1tq06j0lfnshmrl80000gn/T/'. 'FOO'->'benoÃÂ®t'. > >> 'Apple_PubSub_Socket_Render'->'/private/tmp/com.apple.launchd.uWk7pivcLT/Render'. > >> 'TERM_PROGRAM_VERSION'->'404'. > >> 'TERM_SESSION_ID'->'845BECCD-0AB0-4686-B7F9-3A0FF84BDCB7'. > >> 'USER'->'sven'. > >> 'SSH_AUTH_SOCK'->'/private/tmp/com.apple.launchd.y5oCwdUyaG/Listeners'. > >> 'PATH'->'/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/texbin:/opt/X11/bin'. > >> 'PWD'->'/tmp/benoiÃât'. 'XPC_FLAGS'->'0x0'. 'XPC_SERVICE_NAME'->'0'. > >> 'HOME'->'/Users/sven'. 'SHLVL'->'2'. 'LOGNAME'->'sven'. > >> 'LC_CTYPE'->'UTF-8'. 'DISPLAY'->'/private/tmp/com. > >> apple.launchd.lsgASYFiWW/org.macosforge.xquartz:0'. > >> 'SECURITYSESSIONID'->'186a9'. 'OLDPWD'->'/tmp/benoiÃât'. > >> '_'->'/tmp/benoiÃât/pharo-vm/Pharo.app/Contents/MacOS/Pharo'. > >> '__CF_USER_TEXT_ENCODING'->'0x1F5:0x0:0x0'} > >> > >> Of course, if we change this, we will need to fix callers. > >> > >> Opinions ? > >> > >> Sven > >> > >> PS: Furthermore, I note that there is a subtle difference in how $FOO and > >> $PWD in the above are UTF-8 encoded. In the former, normalisation was > >> done, > >> in the latter not. Maybe that could lead to problems (when > >> comparing/composing them). This is a difficult/complex subject ( > >> https://medium.com/concerning-pharo/an-implementation-of-unicode- > >> normalization-7c6719068f43). > >> > >> > >> > >> > > > > > > -- > > Damien Pollet > > type less, do more [ | ] http://people.untyped.org/damien.pollet > > If by different, you mean that it actually normalizes the file names, then > yes. > All Mac filenames are in a well defined form; NFD. > On linux, they're just arrays of bytes, and anything goes. > That the bytes mostly happen to be valid utf8 strings in NFC, is just a > by-product of the fact that's the format most programs use when calling the > file primitives. > > Cheers, > Henry > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > > > > > -- > > Guille Polito > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > CRIStAL - UMR 9189 > French National Center for Scientific Research - http://www.cnrs.fr > > Web: http://guillep.github.io > Phone: +33 06 52 70 66 13

April 19, 2018

Re: [Pharo-dev] Do we kill the catalog?

by Torsten Bergmann

Now today you had loading trouble with Smacc from Catalog ... and now directly want to kill catalog. Wow! Sometimes I have the impression that our community tries to reinvent itself each day doing it differently (but not only better) instead of extending, improving and supporting what we have have done before. Which sometimes is good ... but not always. Thx T. > Gesendet: Donnerstag, 19. April 2018 um 08:42 Uhr > Von: "Stephane Ducasse" <stepharo.self(a)gmail.com> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: [Pharo-dev] Do we kill the catalog? > > Hi guys > > What do we do with it? > What alternatives? > > Stef > >

April 19, 2018

Re: [Pharo-dev] Environment variables encoding ?

by Guillermo Polito

Hi, I think this problem is not environment variable exclusive. It also affects file paths and others. So far Pharo does not detect the locale to perform the encoding and it should be nice to do it. On Tue, Apr 17, 2018 at 10:56 AM, Henrik Sperre Johansen < henrik.s.johansen(a)veloxit.no> wrote: > Damien Pollet wrote > > It seems macOS normalizes UTF-8 differently from everyone else in file > > names (I think base character + composing instead of precomposed > > codepoint). That might affect PWD. > > For environment variables, even if most sensible platforms should have > > adopted UTF-8 by now, I wouldn't be surprised if there's no official > > encoding whatsoever (i.e. they're just bytes with a 0 at the endâ¦) > > > > On 17 April 2018 at 09:36, Sven Van Caekenberghe < > > > sven@ > > > > wrote: > > > >> Hi, > >> > >> The dictionary > >> > >> OSPlatform current environment > >> > >> contains a copy of the OS's environment variables (more correctly of the > >> VM process), as key/value pairs. > >> > >> These are obtained via the following system calls: > >> > >> on macOS & *nix > >> > >> LIBC environ > >> > >> on Windows > >> > >> KERNEL32 GetEnvironmentStrings > >> > >> It is however a bit unclear how these are encoded. On macOS & *nix that > >> seems to be UTF8, on Windows there are some reports that it appears to > be > >> Latin1 - but both might be locale specific, I don't know either way. > >> > >> Does anyone know for sure ? > >> > >> I furthermore think that OSEnvironment and its subclasses, who do this > >> call, should be responsible for decoding the C strings into proper Pharo > >> strings, and not leave that responsibility to its users. > >> > >> Fundamentally, in the following, the decoding is still not done > correctly > >> and that is wrong/confusing IMHO. > >> > >> $ FOO=benoÃ®t ./pharo Pharo.image eval 'OSEnvironment current > >> associations' > >> {'TERM_PROGRAM'->'Apple_Terminal'. 'TERM'->'xterm-256color'. > >> 'SHELL'->'/bin/bash'. 'TMPDIR'->'/var/folders/sy/ > >> sndrtj9j1tq06j0lfnshmrl80000gn/T/'. 'FOO'->'benoÃÂ®t'. > >> 'Apple_PubSub_Socket_Render'->'/private/tmp/com.apple. > launchd.uWk7pivcLT/Render'. > >> 'TERM_PROGRAM_VERSION'->'404'. > >> 'TERM_SESSION_ID'->'845BECCD-0AB0-4686-B7F9-3A0FF84BDCB7'. > >> 'USER'->'sven'. > >> 'SSH_AUTH_SOCK'->'/private/tmp/com.apple.launchd.y5oCwdUyaG/Listeners'. > >> 'PATH'->'/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/ > texbin:/opt/X11/bin'. > >> 'PWD'->'/tmp/benoiÃât'. 'XPC_FLAGS'->'0x0'. 'XPC_SERVICE_NAME'->'0'. > >> 'HOME'->'/Users/sven'. 'SHLVL'->'2'. 'LOGNAME'->'sven'. > >> 'LC_CTYPE'->'UTF-8'. 'DISPLAY'->'/private/tmp/com. > >> apple.launchd.lsgASYFiWW/org.macosforge.xquartz:0'. > >> 'SECURITYSESSIONID'->'186a9'. 'OLDPWD'->'/tmp/benoiÃât'. > >> '_'->'/tmp/benoiÃât/pharo-vm/Pharo.app/Contents/MacOS/Pharo'. > >> '__CF_USER_TEXT_ENCODING'->'0x1F5:0x0:0x0'} > >> > >> Of course, if we change this, we will need to fix callers. > >> > >> Opinions ? > >> > >> Sven > >> > >> PS: Furthermore, I note that there is a subtle difference in how $FOO > and > >> $PWD in the above are UTF-8 encoded. In the former, normalisation was > >> done, > >> in the latter not. Maybe that could lead to problems (when > >> comparing/composing them). This is a difficult/complex subject ( > >> https://medium.com/concerning-pharo/an-implementation-of-unicode- > >> normalization-7c6719068f43). > >> > >> > >> > >> > > > > > > -- > > Damien Pollet > > type less, do more [ | ] http://people.untyped.org/damien.pollet > > If by different, you mean that it actually normalizes the file names, then > yes. > All Mac filenames are in a well defined form; NFD. > On linux, they're just arrays of bytes, and anything goes. > That the bytes mostly happen to be valid utf8 strings in NFC, is just a > by-product of the fact that's the format most programs use when calling the > file primitives. > > Cheers, > Henry > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 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

April 19, 2018

[CfP] ICOOOLPS 2018

by Tim Felgentreff

Call for Papers: ICOOOLPS'18 ============================ 13th Workshop on Implementation, Compilation, Optimization of Object- Oriented Languages, Programs and Systems Co-located with ECOOP 2018 held Mon 16 - Sun 22 July in Amsterdam, Netherlands Twitter: @ICOOOLPS URL: https://conf.researchr.org/track/ecoop-issta-2018/ICOOOLPS-2018-papers The ICOOOLPS workshop series brings together researchers and practitioners working in the field of language implementation and optimization. The goal of the workshop is to discuss emerging problems and research directions as well as new solutions to classic performance challenges. The topics of interest for the workshop include techniques for the implementation and optimization of a wide range of languages including but not limited to object-oriented ones. Furthermore, meta-compilation techniques or language-agnostic approaches are welcome, too. ### Topics of Interest A non-exclusive list of topics of interest for this workshop is: - Implementation and optimization of fundamental languages features (from automatic memory management to zero-overhead metaprogramming) - Runtime systems technology (libraries, virtual machines) - Static, adaptive, and speculative optimizations and compiler techniques - Meta-compilation techniques and language-agnostic approaches for the efficient implementation of languages - Compilers (intermediate representations, offline and online optimizations,â¦) - Empirical studies on language usage, benchmark design, and benchmarking methodology - Resource-sensitive systems (real-time, low power, mobile, cloud) - Studies on design choices and tradeoffs (dynamic vs. static compilation, heuristics vs. programmer input,â¦) - Tooling support, debuggability and observability of languages as well as their implementations ### Workshop Format and Submissions This workshop welcomes the presentation and discussion of new ideas and emerging problems that give a chance for interaction and exchange. More mature work is welcome as part of a mini-conference format, too. We aim to interleave interactive brainstorming and demonstration sessions between the formal presentations to foster an active exchange of ideas. The workshop papers will be published in ACM DL or an open archive (to be confirmed). Papers are to be submitted using the sigplanconf LaTeX template (http://www.sigplan.org/Resources/LaTeXClassFile/) Please submit contributions via EasyChair: https://easychair.org/conferences/submission_show_all.cgi?a=17114062 ### Important Dates Submissions: 18 May 2018 Author Notification: 8 June 2018 ### Program Committee The program committee consists of the organizers and the following reviewers: Nada Amin, University of Cambridge ClÃ©ment BÃ©ra, RMOD - INRIA Lille Nord Europe Shigeru Chiba, University of Tokyo Benoit Daloze, JKU Linz GÃ¶rel Hedin, Lund University Eric Jul, University of Oslo Stefan Marr, University of Kent Eliot Miranda, Cadence Design Systems Sarah Mount, King's College London Tobias Pape, Hasso Plattner Institute Jennifer Sartor, Vrije Universiteit Brussel + University Ghent ### Workshop Organizers Tim Felgentreff, Oracle Labs Potsdam Olivier Zendra, INRIA / LORIA

April 19, 2018

Re: [Pharo-dev] DelayScheduler cleanup & Bootstrap

by Guillermo Polito

On Sun, Apr 15, 2018 at 3:19 PM, Ben Coman <btc(a)openinworld.com> wrote: > I am doing a pass to cleanup the DelayScheduler hierarchy. > I'll be refactoring of the hierarchy to aid code understanding > and eliminate redundant instance variables from the original code. > The target structure is.... > DelayNullScheduler -- minimum interface to avoid errors in rest of system > (6 empty methods) > |__DelayBasicScheduler -- fully working sans race protection (equivalent > to Courageous scheduler) > |__DelaySpinScheduler -- plus race protection > > Can someone advise how/where the Bootstrap loads Delay and the > DelaySchedulers? > Delay and Delay schedulers are atomically loaded during bootstrap (because they are part of the Kernel package so far). So there should be nothing special to do there. > where the invocation of Delay_class>>#initialize selects the delay > scheduler. > Once the image is created, the first method invoked is PharoBootstrapInitialization >> initializeCommandLineHandlerAndErrorHandling which is in the image. You can change it as you please :). > I need to determine whether during transition the Bootstrap might need to > temporarily hop to a different scheduler, > and how to provide the new structure in the Image for operational testing > before switching. > In the bootstrap there is no "switching". A new image is created from scratch with the code that you provide... Initially the image has no delay scheduler process, so calling `Delay class initialize` will create it for you. So as soon as you define Delay class >> initialize "Delay initialize" Scheduler ifNotNil: [ Scheduler stopTimerEventLoop ]. Scheduler := *MyNewScheduler new*. Scheduler startTimerEventLoop. SessionManager default registerSystemClassNamed: self name atPriority: 20. The bootstrap will take it into account. And tests will be run with that configuration. Maybe there is something else to it? You want to do test the switching also? Because for this I would do it with normal smalltalk code... no bootstrap involved... > > cheers -ben > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 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

April 19, 2018

Re: [Pharo-dev] Do we kill the catalog?

by Ben Coman

> > > > > Esteban > > > >> On 19 Apr 2018, at 08:42, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > >> > >> Hi guys > >> > >> What do we do with it? > >> What alternatives? > >> > >> Stef > >> > > > On 19 April 2018 at 14:59, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > > On 19 Apr 2018, at 08:46, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > > why to kill it? > > right now we do not have a replacement. > > btw, I had this idea of > > - using a STON spec instead a class (I think Dale has already something > about it) > - using github as centralised repository to simplify the infrastructure, > and to accept new projects as PRs :) > > justâ¦ no time to implement it yet, but it should be fairly easy. > > cheers, > Esteban > > This is a good idea. The STON could be easily edited directly with github's web-based text editor which would encourage third-parties to enhance the descriptions. Maybe good to publish it as a github pages, with a custom domain to shield against having to move away from github. https://help.github.com/articles/about-supported-custom-domains/#custom-sub… cheers -ben

April 19, 2018

Re: [Pharo-dev] Do we kill the catalog?

by Esteban Lorenzano

> On 19 Apr 2018, at 08:46, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > why to kill it? > right now we do not have a replacement. btw, I had this idea of - using a STON spec instead a class (I think Dale has already something about it) - using github as centralised repository to simplify the infrastructure, and to accept new projects as PRs :) justâ¦ no time to implement it yet, but it should be fairly easy. cheers, Esteban > > Esteban > >> On 19 Apr 2018, at 08:42, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> >> Hi guys >> >> What do we do with it? >> What alternatives? >> >> Stef >> >

April 19, 2018

[Pharo 7.0-dev] Build #783: 21729 Less lint violations in AST-Core and related

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #783 was: SUCCESS. The Pull Request #1216 was integrated: "21729 Less lint violations in AST-Core and related" Pull request url: https://github.com/pharo-project/pharo/pull/1216 Issue Url: https://pharo.fogbugz.com/f/cases/21729 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 19, 2018

Re: [Pharo-dev] Do we kill the catalog?

by Esteban Lorenzano

why to kill it? right now we do not have a replacement. Esteban > On 19 Apr 2018, at 08:42, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi guys > > What do we do with it? > What alternatives? > > Stef >

April 19, 2018

Re: [Pharo-dev] Hierarchy (roots) of package

by ClÃ©ment Bera

I would do that: Implementation: rootsInsidePackage := [ :packageName | | myPackage | myPackage := RPackageOrganizer default packageNamed: packageName. myPackage definedClasses select: [ :each | each superclass package ~~ myPackage ] ]. Example use-case: rootsInsidePackage value: 'OpalCompiler-Core' Is that what you expected ? On Thu, Apr 19, 2018 at 7:19 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi > > Given a package I would like to know the classes that are roots > of hierarchy inside the package. > > Do we have something like that? > > Stef > > -- ClÃ©ment BÃ©ra https://clementbera.github.io/ https://clementbera.wordpress.com/

April 19, 2018