On 29/lug/2015, at 10:25, Frank-Rene Schäfer fschaef@users.sf.net wrote: Does this...
Thanks, I look forward to it.
No, because I cannot use 0.65.4, since it does not handle stream input.
So, what is the solution to get the proper offsets from tell(), rather than the offsets...
You must use a file that is longer than 256 characters to see the problem.
I already posted the code.
You have the .qx above, the .cpp is not needed since it fails the generation. The...
I fixed the last problem by replacing: QUEX_NAME(Buffer_move_away_passed_content)(&me->buffer);...
The problem still remains with function: qlex.buffer_fill_region_append_conversion_direct()...
The bug seems to be that QUEX_NAME(buffer_conversion_fill_region_end) invokes: QUEX_NAME(Buffer_move_away_passed_content)(&me->buffer);...
More precisely, the count is reset to 256 within the call to: QUEX_NAME(Buffer_move_away_passed_content)(&me->buffer);...
Further investigation shows that the value returned by tell() is reset to 256 by...
Any hope for a solution?
Here it is: define { P_EOS [:space:]*\n+ P_LETTER [:intersection(union(\G{Ll}, \G{Lu},...
Here it is: define { P_EOS [:space:]*\n+ P_LETTER [:intersection(union(\G{Ll}, \G{Lu},...
I need to retain the character offset of tokens, in order to transfer the text annotations...
You suggested to look at example 009 for a solution. However, what the example does...
I think we are mixing two issues: the Unicode issue and the streaming issue. I reply...
I am not using any such character, AFAIK. These are the only Unicode constants in...
What the example does is to read data and push it to the lexer. That does not work...
With version 0.64.8, if I use --codec utf8 -b 1 instead of --iconv -b 4, I get this...
I need to create a lexer reading data from an ifstream: istream is(argv[1]); quex::tokenizer_it...
I need to create a lexer reading data from an ifstream: istream is(argv[1]); quex::tokenizer_it...
qex runs forever
Basic DlParser