Re: minor fixes to improve flex compatability with g++ 3.0

[erik quanstrom]

yy_scan_bytes() has the right interface. i have a memory mapped
file that i want to scan.

i do need to compile this stuff with g++ because of some of the 
libraries i'm using. since i need to use c++, i would rather use
the flex c++ interface (via flex++ or flex -+)
because it is fully reentrant.

flex.skl doesn't include the code for yy_scan_bytes() when compiled
in -+ mode -- it's enclosed in a %- ... %* block.

i am taking a crack at modifying flex.skl to accomplish the task,
but please let me know if there's something i'm missing.

what would be really excellent would be making the yy_buffer_state
a public interface (in both the c and c++-style skel files) and 
tweaking the engine to be able to scan a non-writable buffer
directly. i bet we'd loose the ultimate in efficiency by doing this
(extra test to see if we've run off the end of the file), but we'd
sure gain in reduced memory footprint.

erik