Looking at the change logs for flex, it appears that yylineno support
was added in 2.5.4 with the -l flag. Before that it didn't exist. I
bet you are getting the -l flag set somehow. From the info I've read,
using yylineno from flex gives a performance hit (just so you know).
I agree that it needs to be tested for and I will try and write an
autoconf test for it today.
David
Moi!
On Wed, Jul 02, 2003 at 12:05:47PM -0400, [EMAIL PROTECTED] wrote:
Log Message:
A fix for dealing with yylineno and dealing with lex vs flex.
--- dx/src/uipp/dxuilib/Network.C:1.21.2.7 Wed Mar 12 12:25:10 2003
+++ dx/src/uipp/dxuilib/Network.C Wed Jul 2 12:05:47 2003
@@ -1206,8 +1206,8 @@
-#if defined(USING_BISON)
-int yylineno;
+#if defined(USING_FLEX)
+int yylineno; /* flex line number */
Unfortunately it's not that easy. I'm using flex version 2.5.31 here,
and it already defines yylineno itself. Haven't figured out so far at
which version this has changed. How about checking explicitly for this
feature?
Regards,
Daniel.
--
.............................................................................
David L. Thompson Visualization and Imagery Solutions, Inc.
mailto:[EMAIL PROTECTED] 5515 Skyway Drive, Missoula, MT 59804
Phone : (406)756-7472
