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.1 required=5.0 tests=BAYES_05,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,39e272d357c68416 X-Google-Attributes: gid103376,public From: "Steven Hovater" Subject: Re: Is Apex dead as an environment for Ada & Java? Date: 1999/11/26 Message-ID: #1/1 X-Deja-AN: 553453009 References: <000b8d9b.8e8e4afb@usw-ex0107-042.remarq.com> X-Priority: 3 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Complaints-To: abuse@mediaone.net X-Trace: wbnws01.ne.mediaone.net 943656657 24.128.96.60 (Fri, 26 Nov 1999 17:50:57 EST) Organization: Road Runner X-MSMail-Priority: Normal NNTP-Posting-Date: Fri, 26 Nov 1999 17:50:57 EST Newsgroups: comp.lang.ada Date: 1999-11-26T00:00:00+00:00 List-Id: Useless for Ada95? That'll come as a surprise to quite a few of my customers. And how do you enforce your architecture? Another of the strengths that Apex brings is that one can use its subsystems and views to enforce your software architecture. It's common practice among Apex users to use what are called "export sets" which allow a user to define the visibility into a view, thereby preventing unintended and potentially architecture-breaking dependencies to be established. The browsing that Apex does is far beyond what one can get with emacs (I can't comment on the other environments). One can navigate (based on Asis) to object and type definitions that the compiler sees - it's not a tags-based paradigm as in other approaches. Finally, as Tom indicated, for tiny projects, Apex _is_ probably overkill. BUT - imagine a single program library and the sheer impracticality of having mega-lines of source code in a single bucket. Apex scales. Disclaimer: I spend 99% of my time working with Apex and Apex embedded projects with Rational's customers in the NorthEast. Regards, Steve -- Steven Hovater svh@rational.com Software Engineering Consultant Phone/fax:781-676-2565/2500 Rational Software Pager: 888-906-2209 83 Hartwell Ave, Lexington, MA Amateur radio: AA1YH jim_snead wrote in message news:000b8d9b.8e8e4afb@usw-ex0107-042.remarq.com... > In article , > Tom_Hargraves@Raytheon.com wrote: > > *** We are an Ada83 project. Ada 95 may be of help here. However, > > my brain gets > > more and more taxed, the more dots I see in declarations, and > > 'renames' doesn't > > seem to help ;-) > > Like I said, I don't care about Ada 83 with respect to Apex. > Apex Subsystems may be a viable option for organizing Ada 83 > packages. However subsystems are useless for standard Ada 95. > According to one rationale I saw, the Ada 95 package > hierarchy was introduced as an advancement of the old > Rational R1000 (?) subsystem approach. > > My hypothesis is that using a single subsystem and then using > multiple Apex "views" is all that is needed for a large Ada 95 project. > It stands to reason that the concept of a subsystem is therefore > unnecessary and outdated. > > Other options are combinations of CVS, emacs, etc as others > have proposed. These sound much more effective for Ada 95 > and Java development. > > > > * Sent from RemarQ http://www.remarq.com The Internet's Discussion Network * > The fastest and easiest way to search and participate in Usenet - Free! >