rhh88@ecs.soton.ac.uk (Heywood RH) (06/21/91)
I am haveing a few hassles with the flex and bison ports. It all works
ok until I add too many different items in the flex part. At this point
the freshly compiled parser fails to parse any of the files it was quite
happy with before. Delete the new keyword from the tokeniser and it all
works again. It is not that I am entering the keyword data into the .l
file incorrectly, it just that flex seems to be breaking if too may
keywords are used. The flex file is a trivialy simple one that simply
finds fixed words in the source file. A typical entry goes along the
lines of :-
sphere return ySPHERE;
Where ySPHERE is #defined beforehand.
What am I doing wrong! All the parsers I can find were originaly used
with LEX and have commands such as %p 3000 in them. Flex ignores these
(and says it ignoring them) but I think they change the amount of space
available to LEX.
If anyone has any ideas on how to get Flex to accept a greater selection
of keywords without going wrong I would be very happy.
It is used as part of a Ray Tracing Package I am writting (appearing in
the public domain soon hopefully).
Thanks in advance.
Rik
______________________________________________________
/ \
/ Richard Heywood (Rik) \
/ rhh88@uk.ac.soton.ecs \
\ /
\ The Spice must flow /
\______________________________________________________/
Don't go surfing in South Dakota for a while.