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=-0.4 required=5.0 tests=AC_FROM_MANY_DOTS,BAYES_00 autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,db9a11afb3da4240 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-04-01 21:57:16 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!deine.net!amsnews01.chello.com!news-hub.cableinet.net!blueyonder!psiuk-p2!psiuk-p3!uknet!psiuk-n!news.pace.co.uk!nh.pace.co.uk!not-for-mail From: "Marin David Condic" Newsgroups: comp.lang.ada Subject: Re: Language support for flexible handling of system-detected errors. Date: Mon, 1 Apr 2002 13:22:18 -0500 Organization: Posted on a server owned by Pace Micro Technology plc Message-ID: References: NNTP-Posting-Host: dhcp-200-133.miami.pace.co.uk X-Trace: nh.pace.co.uk 1017685340 11818 136.170.200.133 (1 Apr 2002 18:22:20 GMT) X-Complaints-To: newsmaster@news.cam.pace.co.uk NNTP-Posting-Date: 1 Apr 2002 18:22:20 GMT X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Xref: archiver1.google.com comp.lang.ada:21981 Date: 2002-04-01T18:22:20+00:00 List-Id: Well, yeah, sure. If you have some interfacing capability, great. I guess I was arguing against the idea that there could be one single standard out there for all development tool interfaces or that any one given tool could be designed to connect to a multitude of TBD other tools. Some simple editors might provide no programming interface and no scripting language. If you want to integrate them you'll have to do a lot of your own glue-code and still not get everything you might desire. Some editors might provide a single buffer while others provide many buffers. The editor might expect to invoke other tools via its own scripts or it may provide a set of callable interfaces - expecting to be called by something else - or both. Given the multiplicity of ways that an editor might communicate (or not) with the rest of the world and throwing on top of it the multiplicity of ways that compilers, linkers, debuggers, GUI builders, code generators, analyzers, configuration managers, etc., might possibly communicate with the rest of the world, I don't think it is reasonable to expect some kind of standard to emerge. Where you do have specific tools and they provide some ability to communicate, integrating them into a development environment is possible. (Did this once in a previous incarnation. It was a really big job.) But since there are so many possible ways the various tools could choose to work, I don't think it is practical to hope for some kind of standard interoperability. DEC did it their way - GNU does it theirs. (Standards are such a wonderful thing that everyone should have one of their own! :-) Too much of *how* it is done is going to be determined by the design of the tools, so I think standards would be difficult to achieve. It may even be undesirable because it might inhibit design choices when building the tools. MDC -- Marin David Condic Senior Software Engineer Pace Micro Technology Americas www.pacemicro.com Enabling the digital revolution e-Mail: marin.condic@pacemicro.com "Stephen Leake" wrote in message news:u8z871fga.fsf@gsfc.nasa.gov... > > Not to every editor on the planet, but there have been some efforts in > this regard. > > DEC defined a standard format for compiler diagnostics (I forget what > it was called), that LSE and other DEC tools could read. For non-DEC > tools (like Emacs), there was a text equivalent. > > Gnu tools have a standard format for error messages, making them easy > to parse by simple scripts in editors. > > Most programmer-oriented editors allow you to customize the command > line used to invoke compilers and similar tools. > > I don't think we need a real "standard" here, just a common paradigm > and a reasonably powerful scripting language in the editor. >