Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cornell!vern
From: vern@fjalar.cs.cornell.edu (Vern Paxson)
Newsgroups: comp.lang.c++
Subject: Re: ObjectWorks for C++
Message-ID: <41850@cornell.UUCP>
Date: 7 Jun 90 01:45:50 GMT
References: <3089@stl.stc.co.uk> <1208@ztivax.UUCP>
Sender: nobody@cornell.UUCP
Reply-To: vern@cs.cornell.edu (Vern Paxson)
Organization: Cornell Univ. CS Dept, Ithaca NY
Lines: 25
Keywords: Possible solution to lex/ObjectWorks problems

In article <1208@ztivax.UUCP> sof3@ztivax.UUCP (Oliver Rothe) writes:
> ...
> I have a special problem using ObjectWorks (Version 1.1) on a Sun-3.
> Part of my sources are generated by lex and yacc. The C++ front end delivered as
> part of the ObjectWorks package has nothing negative to say about it, but 
> I am not able to import my sources into the ObjectWorks environment due to 
> an internal error ("symbol not found").
>
> It is possible to import the code when I generate it with "lex -f"
> but then I get a runtime error in yylex().
> ...
> Is there anyone with similar experiences 
> and perhaps a work-around for this problem ? 

You might try using my lex replacement, flex.  It's supposed to generate
code that's fully C++-compatible.  You can get version 2.2 by anonymous ftp
to ftp.ee.lbl.gov (or I can mail it to you if you don't have anonymous ftp
access).  2.2 is an alpha release; 2.3, which is a full release, should be
out on comp.sources.unix or such in a couple of weeks.

		Vern

	Vern Paxson			      vern@cs.cornell.edu
	Computer Science Dept.		      decvax!cornell!vern
	Cornell University