http://blog.gmane.org/gmane.comp.lex.flex.general hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.lex.flex.general/2990 <pre>Hi, attached is a bzipped patch to convert the testsuite to autotest. A fine-grained version that proves that the data files are imported verbatim can be found at &lt;URI:https://github.com/scfc/flex/tree/autotest&gt;. The patch is based on my previous "m4-nopreproc" patch but it should be possible to adapt it to HEAD if care is taken of the "--skeldir" option. Tim _______________________________________________ help-flex mailing list help-flex&lt; at &gt;gnu.org https://lists.gnu.org/mailman/listinfo/help-flex </pre> Tim Landscheidt 2011-11-19T01:36:07 http://comments.gmane.org/gmane.comp.lex.flex.general/2988 <pre>Hi, I'm looking at adding support for PHP to flex, and it looks generally feasible. What I don't quite understand is the reasoning behind flex's skeleton system. While Bison's is pretty straight forward, - CMIIW - flex processes the skeleton with m4 to a C array, then implements some "%if-..." control structures of its own and processes the result again with m4 (offering the user another set of control structures for his code). The only technical advantage to Bison's that I can see from a distance is that in this way the whole shebang is contain- ed in one binary. So with regard to my goal, should I go for "%if-php-only", or would a patch to streamline the skeleton system first be met favourably? TIA, Tim </pre> Tim Landscheidt 2011-11-01T01:30:02 http://comments.gmane.org/gmane.comp.lex.flex.general/2984 <pre>_______________________________________________ help-flex mailing list help-flex&lt; at &gt;gnu.org http://lists.gnu.org/mailman/listinfo/help-flex </pre> sdatta 2010-01-23T20:41:47 http://comments.gmane.org/gmane.comp.lex.flex.general/2983 <pre>_______________________________________________ help-flex mailing list help-flex&lt; at &gt;gnu.org http://lists.gnu.org/mailman/listinfo/help-flex </pre> Una Radovanovic 2010-01-03T23:05:52 http://comments.gmane.org/gmane.comp.lex.flex.general/2978 <pre>_______________________________________________ help-flex mailing list help-flex&lt; at &gt;gnu.org http://lists.gnu.org/mailman/listinfo/help-flex </pre> Mahalingam Arumugam 2009-09-28T04:05:34 http://comments.gmane.org/gmane.comp.lex.flex.general/2977 <pre>Hi, I have problem with printing functionality in FireFox. The print preview shows an empty page. So the user ends with this step and thinks no print is available. Another problem is when I try to print directly not the whole application will be printed. Is there an easy way to get FireFox to print correctly. Thank you for all your helpful answers. </pre> Thomas Wukasch 2009-08-26T09:31:14 http://comments.gmane.org/gmane.comp.lex.flex.general/2976 <pre>Is it possible to set the flex start conditions from within bison? I've set a couple of lexer start conditions in the flex file and added yy_push_state() to the bison file, which already includes a flex- generated header. Nonetheless, the compiler still complains that the start condition symbol (named s_element) is undeclared. As the start condition symbol is described in the flex file as: #ifdef YY_HEADER_EXPORT_START_CONDITIONS #define INITIAL 0 #define s_element 1 #endif That leads me to believe that some other tweaking is needed to at least define YY_HEADER_EXPORT_START_CONDITIONS and therefore declare the start condition symbol. So, how do we set flex start conditions from within a bison file? Thanks in advance, Rui Maciel </pre> Rui Maciel 2009-08-24T12:32:42 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.lex.flex.general