- Pharo-users - lists.pharo.org

Re: [Pharo-users] Namespaces (was Re: Behold Pharo: The Modern Smalltalk)

by Torsten Bergmann

To clarify: I was never was for the dot and always favoured the :: notation for namespaced classes. With that one one could create classes like: Seaside::Component Core::Boolean Model::Person GLM::BrickListModel Tx::FontAttribute (see my post on http://forum.world.st/Separator-in-class-names-td4926162.html from 2016). I know this from SmalltalkMT system and it worked nicely. Anyhow: Namespace discussion pop up each year - often in December and mostly because we still not have them ;) The oldest reference you can find is from 2010: http://www.jarober.com/blog/blogView?entry=3462762798 mentioning a Google summer of code project. Then GermÃ¡n Leiva demonstrates this Namespaces project in Pharo https://www.youtube.com/watch?v=n4I7fSVNX2A then it was declared dead: http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2012-June/066765… Then there was a discussion from 2012: http://forum.world.st/Pharo-and-Namespaces-td4636635.html and one in 2016 http://forum.world.st/Separator-in-class-names-td4926162.html Having proper namespaces would avoid such strange things as in https://github.com/pharo-spec/Spec/issues/813 and solve many other issues (but introduce new ones as well). But as always it is a question of time and resources. It's not only about introducing the namespaces itself - it would also mean to change the tools to support them. With Pharo 8 now more experiments are possible into bootstrapping an own Pharo (possibly with Namespaces): 1. One can bootstrap an own image / have it's own personal "Pharo" using Bootstrap to do experiments https://github.com/pharo-project/pharo/tree/Pharo8.0/bootstrap https://rmod.inria.fr/archives/papers/Poli15a-Onward-Bootstrapping.pdf 2. A class now knows about its environment environment "Return the environment in which the receiver is visible" ^Smalltalk globals and OpalCompiler supports an environment in the CompilationContext. So basically you can compile into a second environment withing the existing running image. 3. There is an experiment on modules called Metalo: https://github.com/guillep/metalo According to what Stef wrote on Discord in #bootstrap channel: "The idea is that we want to be able to edit dynamically module (package + namespace) without for example having to remove a full hierarchy of classes when just we change an import statement in a module. Our goal is to split Smalltalk globals into multiple namespaces one per module." "Metalo includes also supports for editing module, bootstrapping a kernel with modules and new class definitions." Dont know about its state. 4. There is a tool called "Candle" to help you bootstrapping own images: https://github.com/carolahp/pharo/tree/candle so one could bootstrap an own kernel with namespace support or other. Bye T. > Gesendet: Montag, 23. Dezember 2019 um 01:18 Uhr > Von: "Esteban Maringolo" <emaringolo(a)gmail.com> > An: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> > Betreff: Re: [Pharo-users] Namespaces (was Re: Behold Pharo: The Modern Smalltalk) > > There are two uses for namespacing: > 1. Avoiding class name collisions between different packages > 2. Modularization > > I don't have the use cases for 2, but Torsten had an idea to support > the dot in the class name, that'd solve the problem 1. (e.g. > Chronology.Date and YourPackage.Date). > > Esteban A. Maringolo > > On Sun, Dec 22, 2019 at 8:57 AM ponyatov <dponyatov(a)gmail.com> wrote: > > > > What is the modern state of namespaces support? Maybe in Pharo 8 (or 9) > > > > I'm going to model some generic async Smalltalk in Pharo, package-bounded > > namespaces can save me from prefixing every class name. > > > > > > > > -- > > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > > >

Dec. 24, 2019

Re: [Pharo-users] High CPU use idling

by Esteban Maringolo

I did a few extra things to detect the anomaly and I found that this happens mostly when running on battery (with CPU throttling). The CPU use gets more intense the more power friendly the power scheme is. I created an issue with a linked video because this might be happening only with VirtualBox or some weird combination. https://github.com/pharo-project/pharo/issues/5417 Regards, Esteban A. Maringolo On Mon, Dec 23, 2019 at 6:27 PM Esteban Maringolo <emaringolo(a)gmail.com> wrote: > > I constantly find Pharo eating the CPU of the VM, from 25% on idle to > 100%, which of course heats up any laptop. > > The Pharo Process monitor doesn't show anything unusual, but I cannot > tell from that tool if some process is the culprit. > > How can I know what is eating the CPU? > Is there a way to kill all the unnecessary process and respawn the needed ones? > > I run Pharo 7 within a VirtualBox VM with Lubuntu on a Windows 10 host. > But the CPU issue happens only with Pharo. > > Regards, > > Image: Pharo-7.0.3+build.164.sha.591a635c8922e5f1cff1d0b3fbf2e525b590d25f > (64 Bit) > Vm: /lib/pharo/5.0-201901051900/pharo (downloaded by PharoLauncher) > > Esteban A. Maringolo

Dec. 24, 2019

High CPU use idling

by Esteban Maringolo

I constantly find Pharo eating the CPU of the VM, from 25% on idle to 100%, which of course heats up any laptop. The Pharo Process monitor doesn't show anything unusual, but I cannot tell from that tool if some process is the culprit. How can I know what is eating the CPU? Is there a way to kill all the unnecessary process and respawn the needed ones? I run Pharo 7 within a VirtualBox VM with Lubuntu on a Windows 10 host. But the CPU issue happens only with Pharo. Regards, Image: Pharo-7.0.3+build.164.sha.591a635c8922e5f1cff1d0b3fbf2e525b590d25f (64 Bit) Vm: /lib/pharo/5.0-201901051900/pharo (downloaded by PharoLauncher) Esteban A. Maringolo

Dec. 23, 2019

Re: [Pharo-users] NeoCSV with numerous fields

by Hilaire

There is no header. I think it is a non-standard case. Thanks for the suggestion. Le 22/12/2019 Ã 18:44, Paul DeBruicker a Ã©critÂ : > Is there a header row? IF so you can do: > > csv := (NeoCSVReader on: stream) separator: Character tab. > header:= csv readHeader. > header size timesRepeat:[csv addFloatField]. > csv upToEnd inspect -- Dr. Geo http://drgeo.eu

Dec. 23, 2019

Re: [Pharo-users] Namespaces (was Re: Behold Pharo: The Modern Smalltalk)

by Kasper Ãsterbye

On 23 December 2019 at 01.31.00, Ronie Salgado (roniesalg(a)gmail.com) wrote: P.S: A bigger problem that I remember from that ESUG discussion is having namespaced/modularized selectors and extension methods. :) Was there ever any reasonable solution/proposal to that issue ? Best, Kasper

Dec. 23, 2019

Re: [Pharo-users] Namespaces (was Re: Behold Pharo: The Modern Smalltalk)

by Ronie Salgado

I do not like the idea of using a dot in class names because dot is already used to separate expressions in a sequence. I am pretty sure that using dot may introduce several ambiguities in the parsing process. For example, the following with the current parser will produce the same AST: someMethod > Chronology.Date > vs someMethod > Chronology. > Date > Using spaces for supporting namespace in theory allows for an implementation that does not require to make several modifications to the compiler (except for efficiency reasons). Using some other separator such as two colons ( :: ) may also solve this parsing ambiguity problem. A single colon ( : ) also posses this ambiguity problem because it could clash with keyword message sends. P.S: A bigger problem that I remember from that ESUG discussion is having namespaced/modularized selectors and extension methods. :) Best regards, Ronie El dom., 22 dic. 2019 a las 21:20, Esteban Maringolo (<emaringolo(a)gmail.com>) escribiÃ³: > There are two uses for namespacing: > 1. Avoiding class name collisions between different packages > 2. Modularization > > I don't have the use cases for 2, but Torsten had an idea to support > the dot in the class name, that'd solve the problem 1. (e.g. > Chronology.Date and YourPackage.Date). > > Esteban A. Maringolo > > On Sun, Dec 22, 2019 at 8:57 AM ponyatov <dponyatov(a)gmail.com> wrote: > > > > What is the modern state of namespaces support? Maybe in Pharo 8 (or 9) > > > > I'm going to model some generic async Smalltalk in Pharo, package-bounded > > namespaces can save me from prefixing every class name. > > > > > > > > -- > > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > > >

Dec. 23, 2019

Re: [Pharo-users] Namespaces (was Re: Behold Pharo: The Modern Smalltalk)

by Esteban Maringolo

There are two uses for namespacing: 1. Avoiding class name collisions between different packages 2. Modularization I don't have the use cases for 2, but Torsten had an idea to support the dot in the class name, that'd solve the problem 1. (e.g. Chronology.Date and YourPackage.Date). Esteban A. Maringolo On Sun, Dec 22, 2019 at 8:57 AM ponyatov <dponyatov(a)gmail.com> wrote: > > What is the modern state of namespaces support? Maybe in Pharo 8 (or 9) > > I'm going to model some generic async Smalltalk in Pharo, package-bounded > namespaces can save me from prefixing every class name. > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Dec. 23, 2019

Re: [Pharo-users] NeoCSV with numerous fields

by Sven Van Caekenberghe

Yes, Paul, I was about to write the same thing. > On 22 Dec 2019, at 18:44, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > > Is there a header row? IF so you can do: > > csv := (NeoCSVReader on: stream) separator: Character tab. > header:= csv readHeader. > header size timesRepeat:[csv addFloatField]. > csv upToEnd inspect > > > > > > HilaireFernandes wrote >> The data come from sensors in 60, 600 and 6000 fields. >> >> I can do has below but I need to know first the number of fields. But >> it's ok. >> >> csv := (NeoCSVReader on: stream) separator: Character tab. >> 60 timesRepeat: [ csv addFloatField]. >> csv upToEnd inspect. >> >> Le 22/12/2019 Ã 17:34, Sven Van Caekenberghe a Ã©crit : >>> Or do you want something else ? >> >> -- >> Dr. Geo >> http://drgeo.eu > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Dec. 22, 2019

Re: [Pharo-users] NeoCSV with numerous fields

by Paul DeBruicker

Is there a header row? IF so you can do: csv := (NeoCSVReader on: stream) separator: Character tab. header:= csv readHeader. header size timesRepeat:[csv addFloatField]. csv upToEnd inspect HilaireFernandes wrote > The data come from sensors in 60, 600 and 6000 fields. > > I can do has below but I need to know first the number of fields. But > it's ok. > > csv := (NeoCSVReader on: stream) separator: Character tab. > 60 timesRepeat: [ csv addFloatField]. > csv upToEnd inspect. > > Le 22/12/2019 Ã 17:34, Sven Van Caekenberghe a Ã©critÂ : >> Or do you want something else ? > > -- > Dr. Geo > http://drgeo.eu -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 22, 2019

Re: [Pharo-users] NeoCSV with numerous fields

by Hilaire

Merci Cedrick. Looks nice. I heard a bit about on Serge's presentation on polymath. Can you do analysis like prediction with? Joyeuses fÃªtes Ã©galement Le 22/12/2019 Ã 17:11, CÃ©drick BÃ©ler a Ã©critÂ : > I think data frame is better for such case > > https://github.com/PolyMathOrg/DataFrame -- Dr. Geo http://drgeo.eu

Dec. 22, 2019