Okay,
I just submitted one more fix. This time, I left in what we had done;
i.e. switched to flex -l, but I also added a test after this to check
for yylineno and use the old idea of just having it available in
Network.C if it doesn't exist. This takes care of the problem with
lexers we don't
Update of /src/master/dx/src/uipp/dxuilib
In directory opendx.watson.ibm.com:/tmp/cvs-serv15158/src/uipp/dxuilib
Modified Files:
Tag: libtool
Network.C
Log Message:
Update the problem with yylineno one more time.
Update of /src/master/dx
In directory opendx.watson.ibm.com:/tmp/cvs-serv15158
Modified Files:
Tag: libtool
acinclude.m4 configure.ac
Log Message:
Update the problem with yylineno one more time.
On Thu, Jul 03, 2003 at 03:16:26PM -0600, David Thompson wrote:
> So why don't I go back to the original plan and just see if I can
> make configure detect if the lexer adds a yylineno? Wouldn't this be
> a heck of a lot easier?
Maybe, but it's not what we want. The code (prior to your 'flex -l'
Okay,
So why don't I go back to the original plan and just see if I can
make configure detect if the lexer adds a yylineno? Wouldn't this be
a heck of a lot easier?
David
On Thu, Jul 03, 2003 at 11:25:44AM -0600, David Thompson wrote:
That was my first thought, but then I thought maybe I
On Thu, Jul 03, 2003 at 11:25:44AM -0600, David Thompson wrote:
> That was my first thought, but then I thought maybe I should actually
> write the test for it--but after almost finishing that (hitting a few
> bugs), I think I agree with you--but are there other lexers that
> don't define yyline
Update of /src/master/dx
In directory opendx.watson.ibm.com:/tmp/cvs-serv14136
Modified Files:
Tag: libtool
acinclude.m4 configure.ac
Log Message:
Fix up our problem with yylineno by making flex create one as
well. Also update acinclude for the newer AutoConf
Update of /src/master/dx/src/uipp/dxuilib
In directory opendx.watson.ibm.com:/tmp/cvs-serv14136/src/uipp/dxuilib
Modified Files:
Tag: libtool
Network.C
Log Message:
Fix up our problem with yylineno by making flex create one as
well. Also update acinclude for the newer AutoConf
That was my first thought, but then I thought maybe I should actually
write the test for it--but after almost finishing that (hitting a few
bugs), I think I agree with you--but are there other lexers that
don't define yylineno? I guess we'll find out.
David
On Thu, Jul 03, 2003 at 07:22:07AM
On Thu, Jul 03, 2003 at 07:22:07AM -0600, David Thompson wrote:
> 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 f
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 ne
Guess I didn't know this. I was going from the flex documentation. I
will see what I can do.
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.
Update of /src/master/dx/src/exec/libdx
In directory opendx.watson.ibm.com:/tmp/cvs-serv15334
Modified Files:
Tag: libtool
Makefile.am
Log Message:
Add plock.c to libDXlite.
Moi!
When compiling the libtool branch with --enable-linux-smp, file
src/exec/libdx/lock.c references functions from plock.c in the same
directory. Unlike lock.c, plock.c is not compiled into libDXlite, and
linkage of the final executables fails due to unresolved symbols. Since
the whole code in p
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
@@ -120
15 matches
Mail list logo
