On 14/06/2016 14:33, Peter TB Brett wrote:
Hi Alex,
I don't think an enhancement to the split command would be adequate
for correct parsing of a CSV file.
I wasn't suggesting that. Having struggled to create the current version
of csvToText, I am all too aware of the vagaries of csv forma
Be my guest.
-- Peter
Peter M. Brigham
pmb...@gmail.com
On Jun 14, 2016, at 9:46 AM, Mike Kerner wrote:
> Peter B,
> If you don't mind, I would like to add your goodies to the codebase we're
> building for csv handling. I'll want to tweak it so that we use the other
> code we already have insi
Peter B,
If you don't mind, I would like to add your goodies to the codebase we're
building for csv handling. I'll want to tweak it so that we use the other
code we already have inside, of course.
On Tue, Jun 14, 2016 at 9:21 AM, Peter M. Brigham wrote:
> Although incorporating this into the en
Peter,
You forgot "far" as in "far beyond". Coping with non-standards and moving
standards is something that is better left at a higher level, IMHO.
I want to add more test and corner cases for things that are legitimate csv
that we should make sure that we handle, properly, so when anyone thinks
On 13/06/2016 12:45, Alex Tweedly wrote:
"into an array" in what way ?presumably a numerically indexed
array.
Perhaps a more general feature requests would be to extend the 'split'
command, so that it would parse by Primary and Secondary delimiters into
numerically indexed arrays ? (u
Although incorporating this into the engine is clearly the way to go, here are
a couple of pure LC functions that are possibly relevant. They could be
generalized to arbitrary line- and item-delimiters.
-- Peter
Peter M. Brigham
pmb...@gmail.com
---
function tabTableToArray pTable, withHe
Sorry, Paul - I suspect I had seen that before, but forgotten it.
It was a good idea back then, and still is :-)
Though, if we are going to add some form of "with colkeys", I believe
there should be a version which says that the first line of the input
contains the column keys; thus you could
I too have a preference for the MIT license.
(Could you also correct the spelling of my name - on Github, you have an
extra 'e' in Tweedley; Tweedly is enough. Thanks :-)
Alex.
On 13/06/2016 17:08, Richard Gaskin wrote:
Mike Kerner wrote:
> Richard and Alex, do we have a preference for whi
Mike Kerner wrote:
> Richard and Alex, do we have a preference for which license to
> release the code under? Peter was asking, on the dropbox thread,
> that we specify it.
Good idea. Not only is Github strongly encouraging more explicit
license declaration, but it's also just a good move to
Richard and Alex, do we have a preference for which license to release the
code under? Peter was asking, on the dropbox thread, that we specify it.
On Mon, Jun 13, 2016 at 9:10 AM, Paul Dupuis wrote:
> On 6/13/2016 7:45 AM, Alex Tweedly wrote:
> > Perhaps a more general feature requests would b
On 6/13/2016 7:45 AM, Alex Tweedly wrote:
> Perhaps a more general feature requests would be to extend the 'split'
> command, so that it would parse by Primary and Secondary delimiters
> into numerically indexed arrays ? (using a new optional keyword
> "completely" ... :-)
See http://quality.livec
"into an array" in what way ?presumably a numerically indexed
array.
Perhaps a more general feature requests would be to extend the 'split'
command, so that it would parse by Primary and Secondary delimiters into
numerically indexed arrays ? (using a new optional keyword "completely
On 10/06/2016 14:53, Mike Kerner wrote:
As far as I know, the latest/greatest code for converting csv to text is
now on my git repository:
https://github.com/macMikey/csvToText
This is great!
Can I make a feature request to parse CSV data into an array?
It is on git. Do a pull and tweak it as you see fit, and I'll be happy to
push the update.
On Fri, Jun 10, 2016 at 1:00 PM, Richard Gaskin
wrote:
> Earlier I wrote:
> > I can update the article to use a non-numeric name, but before I do
> > it's worth exploring that relative to whichever versio
Earlier I wrote:
> I can update the article to use a non-numeric name, but before I do
> it's worth exploring that relative to whichever version you have on
> Github, since there was at least one later version which appeared to
> be faster but turned out to cover fewer edge cases.
I've done some
Mike Kerner wrote:
> It's on git. I'm just keeping it and all the test cases together.
> I think we're at v3 or v4.
I think we covered that a few months ago in a long thread here:
When we were first discussing the need for a CSV parser I proposed a
version named Csv2Tab. The "2" there is not
nope. my bad, v5
On Fri, Jun 10, 2016 at 11:24 AM, Mike Kerner
wrote:
> It's on git. I'm just keeping it and all the test cases together. I
> think we're at v3 or v4.
>
> On Fri, Jun 10, 2016 at 11:17 AM, Richard Gaskin <
> ambassa...@fourthworld.com> wrote:
>
>> Mike Kerner wrote:
>>
>> > It'
It's on git. I'm just keeping it and all the test cases together. I think
we're at v3 or v4.
On Fri, Jun 10, 2016 at 11:17 AM, Richard Gaskin wrote:
> Mike Kerner wrote:
>
> > It's actually based on Richard's code, which was then improved by
> > Alex.
>
> To the best of my knowledge, the Tweed
Mike Kerner wrote:
> It's actually based on Richard's code, which was then improved by
> Alex.
To the best of my knowledge, the Tweedly algo on my page represents the
best version we've seen yet.
If you can point me to where they differ I'll happily update that part
of the article.
--
Ric
Try it now, Roger.
It's actually based on Richard's code, which was then improved by Alex.
After fiddling, this is the version I use with my web scrapers.
On Fri, Jun 10, 2016 at 10:05 AM, Roger Eller
wrote:
> I have used the cvs import function from Richard Gaskin's great article.
> It works re
I have used the cvs import function from Richard Gaskin's great article.
It works relatively well on simple cvs files.
http://www.fourthworld.com/embassy/articles/csv-must-die.html
On Fri, Jun 10, 2016 at 9:53 AM, Mike Kerner
wrote:
> As far as I know, the latest/greatest code for converting
I clicked the link and got "This repository is empty".
On Fri, Jun 10, 2016 at 9:53 AM, Mike Kerner
wrote:
> As far as I know, the latest/greatest code for converting csv to text is
> now on my git repository:
> https://github.com/macMikey/csvToText
>
>
> --
> On the first day, God created the h
As far as I know, the latest/greatest code for converting csv to text is
now on my git repository:
https://github.com/macMikey/csvToText
--
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few h
23 matches
Mail list logo
