parser recommendation

Kay Schluehr kay.schluehr at gmx.net
Tue Jun 3 19:53:10 CEST 2008


On 3 Jun., 19:34, "Filipe Fernandes" <fernandes... at gmail.com> 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
> # construction are defined in terms of global variables.  Users shouldn't
> # notice unless they are trying to define multiple parsers at the same
> # time using threads (in which case they should have their head examined).
>
> Now, I'm invariably going to have to use threads...  I'm not exactly
> sure what the author is alluding to, but my guess is that to overcome
> this limitation I need to acquire a thread lock first before
> "defining/creating" a parser object before I can use it?

Nope. It just says that the parser-table construction itself relies on
global state. But you will most likely build your parser offline  in a
separate run.




More information about the Python-list mailing list