khaw@pplace.COM (Mike Khaw) (06/29/89)
When making inquiries about Objectworks for C++,
please direct calls to the main number at ParcPlace: (415) 691-6700
and e-mail to: info@parcplace.com or info@parcplace.uucp
Thanks,
Mike Khaw
--
ParcPlace Systems, 1550 Plymouth St., Mountain View, CA 94043 415/691-6749
Domain=khaw@parcplace.com, UUCP={uunet,sun,decwrl}!parcplace!khawdsr@stl.stc.co.uk (D.S.Riches) (05/31/90)
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? Dave Riches PSS: David.S.Riches@stl.stc.co.uk (or dsr@stl.stc.co.uk) ARPA: dsr%stl.stc.co.uk@earn-relay.ac.uk Smail: Systems Methods, (Dept. 607, T2 West), STC Technology Ltd., London Road, Harlow, Essex. CM17 9NA. England Phone: +44 (0)279-29531 x2496
sof3@ztivax.UUCP (Oliver Rothe) (06/05/90)
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 ***
vern@fjalar.cs.cornell.edu (Vern Paxson) (06/07/90)
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