December 2019 - Pharo-users

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

Re: [Pharo-users] NeoCSV with numerous fields

by Hilaire

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

Dec. 22, 2019

Re: [Pharo-users] NeoCSV with numerous fields

by Sven Van Caekenberghe

Hi Hilaire, Maybe I don't understand your question, but reading floats with NeoCSV is quite elementary: data := '10.5,-7.5\10.4,-7.4\10.3,-7.3\10.2,-7.2\10.1,-7.1' withCRs. (NeoCSVReader on: data readStream) addFloatField; addFloatField; upToEnd. "#(#(10.5 -7.5) #(10.4 -7.4) #(10.3 -7.3) #(10.2 -7.2) #(10.1 -7.1))" There is even a #addFloatFieldRadixPointComma that shows how to do more custom number reading. Or do you want something else ? Sven > On 22 Dec 2019, at 17:03, Hilaire <hilaire(a)drgeo.eu> wrote: > > Hi, > > I have float number datas coming with 60, 600 and 6000 rows. > > Is there a convenient way to let NeoCSV load and convert to array of floats. > > So far, I am doing it by "hand" with stream? > > Thanks > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > > >

Dec. 22, 2019

Re: [Pharo-users] NeoCSV with numerous fields

by CÃ©drick BÃ©ler

Hi Hilaire, I think data frame is better for such case https://github.com/PolyMathOrg/DataFrame Cheers, Cedrick et bonne fÃªtes ;) > Le 22 dÃ©c. 2019 Ã 17:04, Hilaire <hilaire(a)drgeo.eu> a Ã©crit : > > ï»¿Hi, > > I have float number datas coming with 60, 600 and 6000 rows. > > Is there a convenient way to let NeoCSV load and convert to array of floats. > > So far, I am doing it by "hand" with stream? > > Thanks > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > > >

Dec. 22, 2019

NeoCSV with numerous fields

by Hilaire

Hi, I have float number datas coming with 60, 600 and 6000 rows. Is there a convenient way to let NeoCSV load and convert to array of floats. So far, I am doing it by "hand" with stream? Thanks Hilaire -- Dr. Geo http://drgeo.eu

Dec. 22, 2019