TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

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

Print Reply
Sender: "Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
Date: Fri, 11 Jun 1999 23:11:22 +0400
Reply-To: "Alexandre E. Kopilovitch" <[log in to unmask]>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit 7bit
Content-Type: text/plain; charset=us-ascii
Organization: h w c employees, b f
From: "Alexandre E. Kopilovitch" <[log in to unmask]>
Parts/Attachments: text/plain (27 lines)
"Robert I. Eachus" <[log in to unmask]> wrote:
>In fact, I and a lot of other poeple I know have
>used Ada as a PDL for other languages, especially C.

It is interesting. I thought about this opportunity, but vaguely. Besides of
(possible) direct usefulness for a program designed, it may create another
way for introducing Ada into unfriendly environments. For example: while my
manager insists on C++ against Ada (saying that nobody around knows Ada so
future maintenance will be too costly), at the same time he will not object
for use Ada as PDL -- simply because he totally ignores this level (it sounds
to him like I want to put Lady Ada picture on my desktop). Then (assuming
some positive results) PDL texts may be used inside the team and some
understanding of Ada begins to spread.
  So, I think that presenting Ada as pure PDL that not competes with "true
programmimg languages", but supports them during design phase, may be wise
in some (and not too rare) circumstances.
  But examples and guidelines are needed. For those who aren't Ada experts,
and have little exposure to Ada, but wish to try Ada as PDL (either in
"native" mode or "foreing" mode). Are there such examples and/or guidelines
-- publicly accessible?



Alexander Kopilovitch                      [log in to unmask]
Saint-Petersburg
Russia

ATOM RSS1 RSS2