Terry Reedy wrote:
> "Peter Hansen" <[EMAIL PROTECTED]> wrote:
>>Christopher Subich wrote:
>>>"The horse raced past the barn fell."
>>>
>>>It's just one of many "garden path sentences," where something that
>>>occurs late in the sentence needs to trigger a reparse of the entire
>>>sentence.
>>
>>I
Bengt Richter wrote:
> On Mon, 30 Jan 2006 16:39:51 -0500, Peter Hansen <[EMAIL PROTECTED]> wrote:
[...]
>
> The computer at CMU is pretty good at parsing. You can try it at
> http://www.link.cs.cmu.edu/link/submit-sentence-4.html
>
> Here's what it did with "The horse raced past the barn fel
On Mon, 30 Jan 2006 16:39:51 -0500, Peter Hansen <[EMAIL PROTECTED]> wrote:
>Christopher Subich wrote:
>> Using English, because that's the only language I'm fluent in, consider
>> the sentence:
>>
>> "The horse raced past the barn fell."
>>
>> It's just one of many "garden path sentences," whe
On Mon, 30 Jan 2006 16:39:51 -0500 in comp.lang.python, Peter Hansen
<[EMAIL PROTECTED]> wrote:
>Christopher Subich wrote:
>> Using English, because that's the only language I'm fluent in, consider
>> the sentence:
>>
>> "The horse raced past the barn fell."
>>
>> It's just one of many "garden
"Peter Hansen" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Christopher Subich wrote:
>> Using English, because that's the only language I'm fluent in, consider
>> the sentence:
>>
>> "The horse raced past the barn fell."
>>
>> It's just one of many "garden path sentences," where
Christopher Subich wrote:
> Using English, because that's the only language I'm fluent in, consider
> the sentence:
>
> "The horse raced past the barn fell."
>
> It's just one of many "garden path sentences," where something that
> occurs late in the sentence needs to trigger a reparse of the e
Anton Vredegoor wrote:
> And pave the way for a natural language parser. Maybe there's even some
> (sketchy) path now to link computer languages and natural languages. In
> my mind Python has always been closer to human languages than other
> programming languages. From what I learned about it, lan
Paul McGuire wrote:
> There are two types of parsers: design-driven and data-driven. With
> design-driven parsing, you start with a BNF that defines your language or
> data format, and then construct the corresponding grammar parser. As the
> design evolves and expands (new features, keywords, a
"Anton Vredegoor" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I like your article and pyparsing. But since you ask for comments I'll
> give some. For unchanging datafile formats pyparsing seems to be OK.
> But for highly volatile data like videotext pages or maybe some html
> tabl
Paul McGuire wrote:
> I just published my first article on ONLamp, a beginner's walkthrough for
> pyparsing.
>
> Please check it out at
> http://www.onlamp.com/pub/a/python/2006/01/26/pyparsing.html, and be sure to
> post any questions or comments.
I like your article and pyparsing. But since you
I just published my first article on ONLamp, a beginner's walkthrough for
pyparsing.
Please check it out at
http://www.onlamp.com/pub/a/python/2006/01/26/pyparsing.html, and be sure to
post any questions or comments.
-- Paul
--
http://mail.python.org/mailman/listinfo/python-list
11 matches
Mail list logo
