Re: performance bottleneck in yy_get_next_buffer function

On 15 Jan 2013, at 09:57, Gautam Kapoor <[email protected]> wrote:

> This is true both for flex and flex++.
> 
> Yes, my patch fixed that problem. Ideally, I would expect memcpy to be used instead of a for-do there. But Martin (attached email) suggests that it could be fixed by changing the buffer size. I have to try that. If one can choose an optimal buffer size (may not always be possible), then the effect of this for-do will be minimized.

The problem seems to be buffer implementation problem. So making it larger might work for a particular lexer but it does not fix the problem in Flex.

Hans