On Wed, 06 Apr 2011 01:53:19 -0400, Robert Jacques wrote:
> The library should work with both and be efficient with both. i.e.
> detect at compile-time whether you have a string or an input range, and
> act accordingly.
I'm actually considering trying to benchmark my two implementations.
However
On Tue, 05 Apr 2011 12:45:59 -0400, Jesse Phillips
wrote:
Robert Jacques Wrote:
* You should input ranges. It's fine to detect slicing and optimize for
it, but you should support simple input ranges as well.
This implementation only operates with input ranges, of text. I have
another im
On 04/05/2011 05:32 PM, Robert Jacques wrote:
* There should be a way to specify other separators; I've started using tab
separated files as ','s show up in a lot of data.
There are formats using control codes as separators, as well.
Denis
--
_
vita es estrany
spir.wikidot.com
Robert Jacques Wrote:
> * You should input ranges. It's fine to detect slicing and optimize for
> it, but you should support simple input ranges as well.
This implementation only operates with input ranges, of text. I have another
implementation which works on a slice-able forward range of any
On Tue, 05 Apr 2011 01:44:34 -0400, Jesse Phillips
wrote:
I have implemented an input range based CSV parser that works on text
input[1]. I combined my original implementation with some details of
David's implementation[2]. It is not ready for formal review as I need to
update and polish docume
I have implemented an input range based CSV parser that works on text
input[1]. I combined my original implementation with some details of
David's implementation[2]. It is not ready for formal review as I need to
update and polish documentation and probably consolidate unit tests.
It provides a
