[Interest] FLex / Bison and QT4 4.8.1 Win32 interaction

[william.crocker at analog.com]

>>
>> I suggest you just take the weekend and write your own
>> parser and lexical analysis, void of Flex and Bison.
>> I did and I have never looked back.
>>
>> :-)
>
> If you advice to reinvent the wheel, it's bad advice. But it makes sense
> to know alternatives which may be easier to use or more convenient to work
> with. For example, I very much like re2c lexer, it is simple, fast, and
> can be used in ad-hoc manner inside regular c++ sources.
>

I grew up with Lex and Yacc.
Issues (none of which were ultimately show stoppers).
- Multiple sets in the same program.
- Error reporting.
- Memory recovery on errors.
- Size constraints.
- Parsing poorly designed languages.
- Parsing the idiosyncrasies of well designed languages.
- Porting to other platforms.
- GPL.

Now I just brute force it with C++
minimizing my dependencies on others.

Not wanting to start an off topic thread.

Bill

>>
>>>   Il 07/lug/2016 17:40, "K. Frank"<kfrank29.c at gmail.com
>>>   <mailto:kfrank29.c at gmail.com>>  ha scritto:
>>>
>>>       Ciao Fabio!
>>>
>>>       On Thu, Jul 7, 2016 at 7:19 AM, Fabio Giovagnini<fab at gio.com
>>>       <mailto:fab at gio.com>>  wrote:
>>>       >  Ciao to all.
>>>       >  I have an application linux native based on:
>>>       >  1) qt4 (4.8.1)
>>>       >  3) lex/bison
>>>       >
>>>       >  Under Ubuntu 14.04 and prevoius everithing ok.
>>>       >
>>>       >  Under Windows, I cannot find lex/bison support.
>>>       >  I have to say that I installed only QT SDK (w/ MinGW support)
>>>       >  Any suggestion will be really appreciated.
>>>
>>>       Windows does not come with built-in flex / bison support, nor
>>>       does mingw, nor (to the best of my knowledge) does Qt. (This
>>>       is true of a lot of unix-world libraries that are nearly universal
>>>       on various flavors of unix.)
>>>
>>>       I would expect (but don't know for a fact) that you could find a
>>>       third-party port of flex / bison to windows that you could then
>>>       use for your Qt / flex / bison project. In general, you would be
>>>       best off if you found a port built with the same compiler as your
>>>       Qt project (apparently mingw). One way to insure this would be
>>>       to build it yourself. If you're careful and know what your doing
>>>       you can sometimes get away with using c libraries compiled with
>>>       a different compiler (For example, the ms system calls were not
>>>       compile with mingw and you can call into those.), but it's likely to
>>>       be more bother trying to mix compilers than compiling something
>>>       like flex / bison yourself.
>>>
>>>       >  Thanks
>>>       >  Fabio
>>>
>>>       Happy Parsing!
>>>
>>>       K. Frank
>>>       _______________________________________________
>>>       Interest mailing list
>>>       Interest at qt-project.org<mailto:Interest at qt-project.org>
>>>       http://lists.qt-project.org/mailman/listinfo/interest
>>>
>>>   _______________________________________________
>>>   Interest mailing list
>>>   Interest at qt-project.org
>>>   http://lists.qt-project.org/mailman/listinfo/interest
>>
>> _______________________________________________
>> Interest mailing list
>> Interest at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/interest
>