Very good points. Let me add more inline noise.
On Wed, May 13, 2015 at 11:25 PM, Matt Gushee wrote:
> Hi, Moritz--
>
> On Thu, Apr 16, 2015 at 2:35 PM, Moritz Heidkamp <
> mor...@twoticketsplease.de> wrote:
>
>>
>> sorry for the late reply, got busy :-)
>>
>
> And I'm sorry for the even later
Hi, Moritz--
On Thu, Apr 16, 2015 at 2:35 PM, Moritz Heidkamp wrote:
>
> sorry for the late reply, got busy :-)
>
And I'm sorry for the even later reply, got scared :-)
No, really! It's stupid, but I am often scared of people's reactions when I
make even mildly critical remarks (I hasten to poi
Hi Matt,
sorry for the late reply, got busy :-)
On 28 March 2015 22:18 CET, Matt Gushee wrote:
>
> On Sat, Mar 28, 2015 at 5:33 AM, Moritz Heidkamp > wrote:
>
>>
>> ah, that's what you are referring to, I see! It's like that because I
>> didn't want to force a utf8 dependency on the user.
>
>
> M
On Sat, Mar 28, 2015 at 3:24 PM, John Cowan wrote:
> Matt Gushee scripsit:
>
> > string-kmp-partial-search
> > make-kmp-restart-vector
> >
> > Substring/shared is not too big a deal, but that KMP stuff is a bit
> > daunting. Maybe I'll look into it if I have time. I do like the comparse
>
Matt Gushee scripsit:
> string-kmp-partial-search
> make-kmp-restart-vector
>
> Substring/shared is not too big a deal, but that KMP stuff is a bit
> daunting. Maybe I'll look into it if I have time. I do like the comparse
> API, and would like to be able to use it.
Fortunately, KMP work
Hi, Moritz--
On Sat, Mar 28, 2015 at 5:33 AM, Moritz Heidkamp wrote:
>
> ah, that's what you are referring to, I see! It's like that because I
> didn't want to force a utf8 dependency on the user.
Maybe in that case it would be good if the API doc said something like:
"comparse is compatible w
Hey Matt,
On 27 March 2015 21:19 CET, Matt Gushee wrote:
> That's a fair question. I was working on a toy XML parser as a learning
> exercise, and I thought "hmm ... this should support UTF-8". So I attempted
> to use utf8-srfi-14 in place of regular srfi-14; then certain parsing
> functions didn
Hi, Moritz--
On Fri, Mar 27, 2015 at 11:32 AM, Moritz Heidkamp <
mor...@twoticketsplease.de> wrote:
>
> On 27 March 2015 18:18 CET, Matt Gushee wrote:
>
> > BTW, in case you are interested, I was going to use comparse, which is a
> > bit easier to learn (don't know about performance), but found t
I also think that the question of input stream encoding is orthogonal
to the issues of parsing.
There is no technical reason why there could not be a unified and extensible
Chicken input stream library that can be used by all the different
parser libraries available.
The problems solved by lexgen/a
Hi Matt,
On 27 March 2015 18:18 CET, Matt Gushee wrote:
> BTW, in case you are interested, I was going to use comparse, which is a
> bit easier to learn (don't know about performance), but found that it
> didn't support UTF-8, which in my world is not acceptable.
as the author of Comparse I wond
Thanks, Ivan, that's a great help!
BTW, in case you are interested, I was going to use comparse, which is a
bit easier to learn (don't know about performance), but found that it
didn't support UTF-8, which in my world is not acceptable. And it appears
that abnf is the only general-purpose parsing
Hi Matt,
Thanks for your interest in using abnf. I admit that the details of
parsing are hidden away in the documentation for lexgen.
I have updated the example to include a definition for fws and create
and import the appropriate input type classes (more or less equivalent
to importing abnf-ch
Hello--
I'm attempting to learn how to use the abnf egg, but I'm having some
difficulties.
First of all, I think the example needs to be updated. It uses the 'lit'
matcher, which requires 'abnf-charlist' to be imported; also, the 'fws' and
'cfws' symbols are not defined. It's not hard to define t
13 matches
Mail list logo
