On Wednesday, 9 March 2016 at 21:55:23 UTC, Jack Stouffer wrote:
The code and docs can be found here:
https://github.com/JackStouffer/date-parser
Quick update: all dateutil tests are now passing. It can how
parse just about any date format you can throw at it :)
On Thursday, 10 March 2016 at 21:25:16 UTC, Jack Stouffer wrote:
On Wednesday, 9 March 2016 at 22:12:42 UTC, Walter Bright wrote:
I haven't read the article yet, but you'll get more interest
by putting a summary as the first comment on reddit.
Thanks for the advice, I think it caused more
On Wednesday, 9 March 2016 at 22:12:42 UTC, Walter Bright wrote:
I haven't read the article yet, but you'll get more interest by
putting a summary as the first comment on reddit.
Thanks for the advice, I think it caused more people to read it.
Also, I forgot to mention in the article that the
On Thursday, 10 March 2016 at 17:59:21 UTC, Chris Wright wrote:
It's a little easier to write iterators in the Python style:
you don't have to cache the current value, and you don't have
to have a separate check for end-of-iteration. It's a little
easier to use them in the D style: you get
On Thu, 10 Mar 2016 08:22:58 +, Ola Fosheim Grøstad wrote:
> On Thursday, 10 March 2016 at 00:29:46 UTC, Jack Stouffer wrote:
>>> It's a pretty straight forward standard iterator design and quite
>>> different from the table pointers C++ uses.
>>
>> I explain my grievances in the article.
>
Just pointing out the obvious:
For the simple iterators/generators that run on a non-changing
source you can basically break it up into:
1. iterators without lookahead
2. iterators with lookahead
Which is basically the same issues you deal with when
implementing a lexer.
Python-style
On Thursday, 10 March 2016 at 00:29:46 UTC, Jack Stouffer wrote:
It's a pretty straight forward standard iterator design and
quite different from the table pointers C++ uses.
I explain my grievances in the article.
They didn't make all that much sense to me, so I wondered what
Theo's issues
On Wednesday, 9 March 2016 at 23:31:04 UTC, Ola Fosheim Grøstad
wrote:
On Wednesday, 9 March 2016 at 22:17:39 UTC, H. S. Teoh wrote:
system for my personal projects), I can totally sympathize
with the annoyances of using a dynamically-typed language, as
well as dodgy iterator designs like
On Wednesday, 9 March 2016 at 22:17:39 UTC, H. S. Teoh wrote:
system for my personal projects), I can totally sympathize with
the annoyances of using a dynamically-typed language, as well
as dodgy iterator designs like __next__. (I've not had to deal
with __next__ in Python so far, but *have*
On Wed, Mar 09, 2016 at 02:12:42PM -0800, Walter Bright via
Digitalmars-d-announce wrote:
> On 3/9/2016 1:55 PM, Jack Stouffer wrote:
> >Hello everyone,
> >
> >I have spent the last two weeks porting the date string parsing
> >functionality from the popular Python library, dateutil, to D. I have
On 3/9/2016 1:55 PM, Jack Stouffer wrote:
Hello everyone,
I have spent the last two weeks porting the date string parsing functionality
from the popular Python library, dateutil, to D. I have written about my
experience here: http://jackstouffer.com/blog/porting_dateutil.html
The code and docs
Hello everyone,
I have spent the last two weeks porting the date string parsing
functionality from the popular Python library, dateutil, to D. I
have written about my experience here:
http://jackstouffer.com/blog/porting_dateutil.html
The code and docs can be found here:
12 matches
Mail list logo
