What do you mean by "even though it's not GNU anymore?"
I'm looking at it - we needed some of the improvements to memory usage in our project.
However, it looks to me to be a major shift; it's really flex 2.6 or something.
M4 is now mandatory as well as regex. For Win32 that isn't so bad, but for some of the other platforms it might not be so hot.
I can do the work, in fact, I already have it compiling with MSVC8. However, I don't like the fact that the C++ side is 'broken' according to the developer.
We need something thread safe - right now, we're using the C++ lexer with each thread having it's own object. So far, no problems, but due to an issue with freeing the stack there is a small memory bug each time flex is invoked.
I'll do this work here or on flex 2.5.33, but I don't want to do it in two places.
Or should I take the code in 2.5.33 and update 2.5.4a here? I would hate to do that as it would make it win32 specific, I Think.
Thoughts?
== John ==
P.S. I know it's an older email, but FLEX moves slow :( and I need to move fast .. deadline of next week for a paying customer.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is there any plan to port flex 2.5.33, even though it is not GNU anymore ?
Tks
It is on the to-do list, but developer time is scarce at the moment, and any time there is, is occupied with other priorities.
What do you mean by "even though it's not GNU anymore?"
I'm looking at it - we needed some of the improvements to memory usage in our project.
However, it looks to me to be a major shift; it's really flex 2.6 or something.
M4 is now mandatory as well as regex. For Win32 that isn't so bad, but for some of the other platforms it might not be so hot.
I can do the work, in fact, I already have it compiling with MSVC8. However, I don't like the fact that the C++ side is 'broken' according to the developer.
We need something thread safe - right now, we're using the C++ lexer with each thread having it's own object. So far, no problems, but due to an issue with freeing the stack there is a small memory bug each time flex is invoked.
I'll do this work here or on flex 2.5.33, but I don't want to do it in two places.
Or should I take the code in 2.5.33 and update 2.5.4a here? I would hate to do that as it would make it win32 specific, I Think.
Thoughts?
P.S. I know it's an older email, but FLEX moves slow :( and I need to move fast .. deadline of next week for a paying customer.