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

2019-12-22 Thread 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

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

2019-12-22 Thread 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. Ma

Re: [Pharo-users] NeoCSV with numerous fields

2019-12-22 Thread Sven Van Caekenberghe
Yes, Paul, I was about to write the same thing. > On 22 Dec 2019, at 18:44, Paul DeBruicker 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

Re: [Pharo-users] NeoCSV with numerous fields

2019-12-22 Thread 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 belo

Re: [Pharo-users] NeoCSV with numerous fields

2019-12-22 Thread 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

Re: [Pharo-users] NeoCSV with numerous fields

2019-12-22 Thread 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

Re: [Pharo-users] NeoCSV with numerous fields

2019-12-22 Thread 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)

Re: [Pharo-users] NeoCSV with numerous fields

2019-12-22 Thread 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 a écrit : > > Hi, > > I have float number datas coming with 60, 600 and 6000 rows. > > Is there a convenient way to let Ne

[Pharo-users] NeoCSV with numerous fields

2019-12-22 Thread 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

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

2019-12-22 Thread ponyatov
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