[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Thread expierence with bison
From: |
Xinan Tang |
Subject: |
RE: Thread expierence with bison |
Date: |
Wed, 23 Apr 2003 09:31:43 -0700 |
Hi
I should warn you that the code generated by flex and bison is thread safe
doesn't mean that the entire code is thread safe. The programmers need to
guarantee that any code inserted between %{ .... %} is thread too.
Xinan Tang (Ph.D)
Senior MTS
Xambala Inc
2025 Gateway Place, Suite 130
San Jose, CA 95110
-----Original Message-----
From: John [mailto:address@hidden
Sent: Wednesday, April 23, 2003 12:45 AM
To: Rüdiger Härtel
Cc: address@hidden
Subject: Re: Thread expierence with bison
> What are your experiences with a flex/bison built scanner/parser
> (threads/processes, longlevity, RAM consumption ...) ? Where are
> pitfalls ?
The latest flex can generate a thread-safe scanner (%option reentrant)
and even unload the large DFA tables when you're done scanning. Bison
can generate a thread-safe parser (%pure). One pitfall is that you
have to hand over the flow-control of your program to the flex and
bison-generated code, which operates in the form of callback blocks.
_______________________________________________
address@hidden http://mail.gnu.org/mailman/listinfo/help-bison