Re: parser recommendation

2008-06-06 Thread Kay Schluehr
On 6 Jun., 01:58, Alan Isaac <[EMAIL PROTECTED]> wrote: > One other possibility: > SimpleParse (for speed). > http://simpleparse.sourceforge.net/> > It is very nice. > Alan Isaac How does SimpleParse manage left-factorings, left-recursion and other ambiguities? For example according to [1] there

Re: parser recommendation

2008-06-05 Thread Alan Isaac
One other possibility: SimpleParse (for speed). http://simpleparse.sourceforge.net/> It is very nice. Alan Isaac -- http://mail.python.org/mailman/listinfo/python-list

Re: parser recommendation

2008-06-03 Thread rurpy
On Jun 3, 2:55 pm, "Filipe Fernandes" <[EMAIL PROTECTED]> wrote: > I haven't given up on pyparsing, although I'm now heavily leaning > towards PLY as an end solution since lex and yacc parsing is available > on other platforms as well. Keep in mind that PLY's "compatibility" with YACC is functiona

Re: parser recommendation

2008-06-03 Thread Filipe Fernandes
> On Jun 3, 12:34 pm, "Filipe Fernandes" <[EMAIL PROTECTED]> wrote: >> On Tue, Jun 3, 2008 at 10:41 AM, Paul McGuire <[EMAIL PROTECTED]> wrote: >> But I do have more questions... when reading the ply.py header (in >> 2.5) I found the following paragraph... >> >> # The current implementation is only

Re: parser recommendation

2008-06-03 Thread Paul McGuire
On Jun 3, 12:34 pm, "Filipe Fernandes" <[EMAIL PROTECTED]> wrote: > On Tue, Jun 3, 2008 at 10:41 AM, Paul McGuire <[EMAIL PROTECTED]> wrote: > But I do have more questions... when reading the ply.py header (in > 2.5) I found the following paragraph... > > # The current implementation is only somewh

Re: parser recommendation

2008-06-03 Thread Kay Schluehr
On 3 Jun., 19:34, "Filipe Fernandes" <[EMAIL PROTECTED]> wrote: > # The current implementation is only somewhat object-oriented. The > # LR parser itself is defined in terms of an object (which allows multiple > # parsers to co-exist). However, most of the variables used during table > # construc

Re: parser recommendation

2008-06-03 Thread Filipe Fernandes
On Tue, Jun 3, 2008 at 10:41 AM, Paul McGuire <[EMAIL PROTECTED]> wrote: > If you learn both, you may find that pyparsing is a good way to > quickly prototype a particular parsing problem, which you can then > convert to PLY for performance if necessary. The pyparsing prototype > will be an effici

Re: parser recommendation

2008-06-03 Thread Paul McGuire
On Jun 3, 8:43 am, "Filipe Fernandes" <[EMAIL PROTECTED]> wrote: > > I've briefly looked at PLY and pyparsing.  There are several others, > but too many to enumerate.  My understanding is that PLY (although > more difficult to use) has much more flexibility than pyparsing.  I'm > basically looking

Re: parser recommendation

2008-06-03 Thread Kay Schluehr
On 3 Jun., 15:43, "Filipe Fernandes" <[EMAIL PROTECTED]> wrote: > I have a project that uses a proprietary format and I've been using > regex to extract information from it. I haven't hit any roadblocks > yet, but I'd like to use a parsing library rather than maintain my own > code base of compli

parser recommendation

2008-06-03 Thread Filipe Fernandes
I have a project that uses a proprietary format and I've been using regex to extract information from it. I haven't hit any roadblocks yet, but I'd like to use a parsing library rather than maintain my own code base of complicated regex's. I've been intrigued by the parsers available in python, w