Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!mit-eddie!uw-beaver!sumax!amc-gw!pilchuck!dataio!bright
From: bright@Data-IO.COM (Walter Bright)
Newsgroups: comp.lang.c++
Subject: Re: zortech problem with lex
Message-ID: <2347@dataio.Data-IO.COM>
Date: 25 Feb 90 09:38:37 GMT
References: <6300008@ux1.cso.uiuc.edu>
Reply-To: bright@Data-IO.COM (Walter Bright)
Organization: Data I/O Corporation; Redmond, WA
Lines: 16

In article <6300008@ux1.cso.uiuc.edu> cs326ad@ux1.cso.uiuc.edu writes:
<Now, when porting this code to C++ zortech style, the lex.yy.c program compiles
<fine (with a few minor changes.)  However, the executable does NOT recognize
<the \n the same as the executable on the net.  i.e.:
<If we input:   1234     to the lex executable on the net, I get the output
<INT	1234
<However, on the zortech implementation, for the same input, I get
<INT	1
<Doing a little debugging on the zortech code, I came to realize that the
<eoln was ended with a   \r\n   for carriage return newline.  Fine.  But
<for some reason the zortech implementation does not catch the newline at
<the end of the line, like it does on the net.

I'm afraid I don't understand. Is the *compiler* not working right or the
*run-time library*? Please reduce the problem to a few lines of code
which exhibit the problem. I know very little about lex/flex.