Re: [tcpdump-workers] [Fwd: Re: Thread Safe Lexer]

2009-07-13 Thread Gianluca Varenni
PM Subject: Re: [tcpdump-workers] [Fwd: Re: Thread Safe Lexer] - Original Message - From: "Guy Harris" To: Sent: Thursday, July 09, 2009 5:45 PM Subject: Re: [tcpdump-workers] [Fwd: Re: Thread Safe Lexer] On Jul 9, 2009, at 3:34 PM, Gianluca Varenni wrote: This actually

Re: [tcpdump-workers] [Fwd: Re: Thread Safe Lexer]

2009-07-09 Thread Gianluca Varenni
- Original Message - From: "Guy Harris" To: Sent: Thursday, July 09, 2009 5:45 PM Subject: Re: [tcpdump-workers] [Fwd: Re: Thread Safe Lexer] On Jul 9, 2009, at 3:34 PM, Gianluca Varenni wrote: This actually makes sense to me (I actually have the same problem with Wi

Re: [tcpdump-workers] [Fwd: Re: Thread Safe Lexer]

2009-07-09 Thread Guy Harris
On Jul 9, 2009, at 3:34 PM, Gianluca Varenni wrote: This actually makes sense to me (I actually have the same problem with WinPcap, and I do ship the generated files in the WinPcap source package). Are there any cons to this? The only potential risk would be if the version of Flex or Bison

Re: [tcpdump-workers] [Fwd: Re: Thread Safe Lexer]

2009-07-09 Thread Gianluca Varenni
- Original Message - From: "Sam Roberts" To: Sent: Thursday, July 02, 2009 11:14 AM Subject: Re: [tcpdump-workers] [Fwd: Re: Thread Safe Lexer] On Wed, Jul 1, 2009 at 12:32 PM, Eloy Paris wrote: Do we use Flex and Bison on all supported platforms, or we have things setup

Re: [tcpdump-workers] [Fwd: Re: Thread Safe Lexer]

2009-07-02 Thread Sam Roberts
On Wed, Jul 1, 2009 at 12:32 PM, Eloy Paris wrote: > Do we use Flex and Bison on all supported platforms, or we have things > setup so we use the original Lex and Yacc on some platforms to have > backward source code compatibility? Sorry if this is noise (it's been a while since I've used flex/bis

Re: [tcpdump-workers] [Fwd: Re: Thread Safe Lexer]

2009-07-01 Thread Eloy Paris
Behdad, On Wed, Jul 01, 2009 at 03:04:49PM -0400, Behdad Forghani wrote: > Hello, > > Gianluca asked me to forward this to the mailing list. During > Sharkfest09 he had mentioned that Winpcap cannot is not re-entrant > and thread-safe because Lex uses global variables. As you can see, > one solu

Re: [tcpdump-workers] [Fwd: Re: Thread Safe Lexer]

2009-07-01 Thread Eloy Paris
Hi Gianluca, On Wed, Jul 01, 2009 at 12:54:13PM -0700, Gianluca Varenni wrote: > - Original Message - From: "Guy Harris" > To: > Sent: Wednesday, July 01, 2009 12:47 PM > Subject: Re: [tcpdump-workers] [Fwd: Re: Thread Safe Lexer] > > > > >

Re: [tcpdump-workers] [Fwd: Re: Thread Safe Lexer]

2009-07-01 Thread Gianluca Varenni
- Original Message - From: "Guy Harris" To: Sent: Wednesday, July 01, 2009 12:47 PM Subject: Re: [tcpdump-workers] [Fwd: Re: Thread Safe Lexer] On Jul 1, 2009, at 12:04 PM, Behdad Forghani wrote: Gianluca asked me to forward this to the mailing list. During Sharkfes

Re: [tcpdump-workers] [Fwd: Re: Thread Safe Lexer]

2009-07-01 Thread Guy Harris
On Jul 1, 2009, at 12:04 PM, Behdad Forghani wrote: Gianluca asked me to forward this to the mailing list. During Sharkfest09 he had mentioned that Winpcap cannot is not re-entrant and thread-safe because Lex uses global variables. As you can see, one solution to this is to use re2c for le

[tcpdump-workers] [Fwd: Re: Thread Safe Lexer]

2009-07-01 Thread Behdad Forghani
Hello, Gianluca asked me to forward this to the mailing list. During Sharkfest09 he had mentioned that Winpcap cannot is not re-entrant and thread-safe because Lex uses global variables. As you can see, one solution to this is to use re2c for lexing and lemon for parsing. The link to re2c is: