Path: utzoo!attcan!uunet!mcsun!unido!ztivax!sof3
From: sof3@ztivax.UUCP (Oliver Rothe)
Newsgroups: comp.lang.c++
Subject: Re: ObjectWorks for C++
Summary: LEX problems
Message-ID: <1208@ztivax.UUCP>
Date: 5 Jun 90 08:51:27 GMT
References: <3089@stl.stc.co.uk>
Organization: Siemens AG, Munich, W-Germany
Lines: 45

In article <3089@stl.stc.co.uk>, dsr@stl.stc.co.uk (D.S.Riches) writes:
> I just saw ObjectWorks for C++ and was very disappointed.  Having used
> the Smalltalk environment for a couple of years I was quite excited at
> the prospect of being able to do similar things with C++.  BUT it was
> quite a downer.  It seemed as though the package had been developed as
> separate tools and then tried to integrate them.
> 
> I know that there is a new version out but the bug-fix list doesn't
> seem to address some basic errors such as integration.
> 
> Has anyone used ObjectWorks in anger?  Does it help people to use the
> Object Oriented paradigms?  Any comments generally?
> 

First a general remark:

For those of us coming from the C environment, ObjectWorks is certainly a step 
forward. It hopefully marks the end of the times when C++ was a new language 
with an old-fashioned environment. 

But ...

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().

I had to forget the environment and now work solely with the front end.

Is there anyone with similar experiences 
and perhaps a work-around for this problem ? 

I would appreciate any comment.

	
	Oliver Rothe 




*** Standard Disclaimer ***