TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy


Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Mime-Version: 1.0
Sender: "Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
From: Ada Marketing <[log in to unmask]>
Date: Tue, 14 Nov 2000 18:08:16 -0500
Content-Type: multipart/mixed; boundary="------------572C5552993BEF23EA5E8765"
X-cc: Simon Wright <[log in to unmask]>
Reply-To: Ada Marketing <[log in to unmask]>
Parts/Attachments: text/plain (1238 bytes) , adamark.vcf (171 bytes)

Note that all the ObjectAda development environments do this as well (including the
free copy).

Simon Wright wrote:

> > From: [log in to unmask]
> >
> > >The Rational Apex browser will "jump" to the definition of an item with a
> > >single click (same window or bring up another window), regardless of whether
> > >name is qualified or not.  Numerous Rational Apex users get "hooked" on the
> > >browser for this feature alone.
> >
> > How much does it cost?
> Quite a lot. And you can't get it on Linux.
> > Clearly Apex (and other compilers) rely on a 'project' based
> > approach with sources being 'registered' to provide this
> > functionality. Although GNAT has started using project files which
> > presumably allow this, it is still possible to use GNAT without this
> > project facility and, in these case, searching through the source
> > (with Emacs extensions :-) is the way to do it.
> Once the code has compiled (and there's a similar restriction with
> Apex). you can skip straight to the definition with ada-mode (C-c
> C-d).
> As far as this is concerned, the GNAT project files control switches,
> name of executable etc, but really as far as this problem is concerned
> it's just the path that counts; no need to register sources. Or
> ability, for that matter :-)