From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,7fb807868446d767 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1995-03-11 14:44:26 PST Newsgroups: comp.lang.ada Path: bga.com!news.sprintlink.net!hookup!news.moneng.mei.com!uwm.edu!msunews!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!nntp.brisnet.org.au!ozspace.brisnet.org.au!wengelin From: wengelin@ozspace.brisnet.org.au (Daneil Wengelin) Subject: Re: ADA context sensitive editor X-Newsreader: TIN [version 1.2 PL2] Sender: usenet@nntp.brisnet.org.au (usenet) Nntp-Posting-Host: ozspace.brisnet.org.au Organization: OZSPACE BBS Message-ID: <1995Mar11.224426.23566@nntp.brisnet.org.au> References: Date: Sat, 11 Mar 1995 22:44:26 GMT Date: 1995-03-11T22:44:26+00:00 List-Id: Wayne Elliott (wayne@adied.oz.au) wrote: : I'm just sending out feelers to see if any one knows of : or has had experienced with context sensitive editors : for ADA. You know the sort of thing; features like: : - key word colour highlighting : - command anticipation : - auto indenting based on syntax : - early syntax checking : and any other clever time-saving features/gadgets. : What's out there? Commercial or otherwise If you are at ADI at Technology Park in Adelaide, you could just walk over to CelsiusTech Australia, to check out APEX by Rational. Otherwise your local Rational representative could tell you all about it. APEX is good, and does all the stuff you could need in a development system. Unfortunately, it's pretty expensive unless you're a university, which you are not. ------------------------------------------------------------------------ -- Daniel Wengelin -- Team Ada, the best 0$ mem- -- -- CelsiusTech -- bership fee you'll ever spend -- -- dawe@celsiustech.se -- -- -- wengelin@ozspace.brisnet.org.au -- -- ------------------------------------------------------------------------ with Standard_Disclaimer;