LISTSERV mailing list manager LISTSERV 16.0

Help for TEAM-ADA Archives


TEAM-ADA Archives

TEAM-ADA Archives


TEAM-ADA@LISTSERV.ACM.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

TEAM-ADA Home

TEAM-ADA Home

TEAM-ADA  April 1998

TEAM-ADA April 1998

Subject:

Re: Embedded Systems Programming Magazine

From:

Stanley Allen <[log in to unmask]>

Reply-To:

Stanley Allen <[log in to unmask]>

Date:

Fri, 17 Apr 1998 03:52:03 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (147 lines)

Tom Moran wrote:
>
>   What might cause a programmer, when given a new assignment,
> to say to his boss "Let's try Ada for this"?  What might
> cause him to spend his own money on a book to learn something
> about Ada, or to spend his own time to, say, download Gnat or
> ObjectAda, and experiment?

A fair question.  You could ask the same thing about
Java.  Why are they downloading Java tools and playing
with them?  Why are they buying Java books by the
truckloads?

It's because they 1) have been persuaded by the hype
that Java is the a) the next big thing and/or b) cool;
or 2) are attracted by this or that feature of Java.

The point of my last few messages about marketing and
Ada have been that now is the right time to "claim"
real-time systems specifically for Ada.  If our hype
was directed towards this end, then a certain amount
of momentum might be generated to persuade a new
generation of developers that Ada 95 is the "big thing"
for real-time systems.

People can also be attracted to try Ada because of
some of its features.  I always emphasize tasking
features when I "sell" Ada.  It's a very, *very* cool
topic.  At Tri-Ada '96 when Tucker Taft had a face-
off forum with a Java dude from Sun, Tucker stated
that he believed that Ada had a lot of "steak",
whereas Java had a lot of "sizzle".  I interpreted
him to mean that Java had "sex appeal" to programmers
but that Ada did not, and mentally I said "what
about tasking?".  Whenever I teach Ada, everyone
wants to learn about tasking.  It's got panache.
(Under the "tasking" heading I am including all aspects
of concurrency and real-time features.)  It's a world
of fun to learn and play with.  I can envision a number
of articles in pop magazines like ESP or JOOP that
highlight different aspects of Ada concurrency features,
specifically protected records, asynchronous transfer
of control, rendezvous variants, etc.

Programmers are attracted by features and the extra
level of power that they feel they gain when having
access to and understanding of a feature.  When
promoting Ada, it's important not simply to claim
"Ada is so wonderful, it's so great, you should
really consider Ada".  Get down to specifics by
describing a single feature in detail.  I've done
this a number of times recently in my office with
the ATC ("select ... then abort ...") feature of
Ada 95, to great effect.

Generally, it's necessary to walk someone through
the semantics of the feature and given them a few
examples of how it can be used to solve this or
that problem.  In a way, you must be the teacher in
a mini Ada 95 class focused on a single feature.
This is how almost all of the "practical programmer"
columns are written in magazines like "C++ Report".

Introducing and illustrating a feature has a
tendency to fire the imaginations of programmers.
Their fingers begin to itch -- they want to use
the new, fun feature in their own work.

>   Imagine yourself one of the best programmers in your shop,
> your boss and colleagues know it, and you feel confident in
> your abilities in your current language.  What would cause
> you to spend time and perhaps even money investigating Ada?

For programmers in a "shop" ("we're a C shop, we don't use
Ada/Java/Eiffel around here"), you've got to show them how
to use Ada (or any new technology, for that matter) without
disturbing the world they are already working in.  This
means that you have to be able to show them that they
can use Ada for some things even if they can't use it
for everything.  The first step is to illustrate how
some Ada feature would be useful to them, but which is
unavailable in whatever language they are using.  After
this, it's necessary to explain how to do the multi-
language interfacing (I've done this for a number of
people -- it's always a real eye-opener for the
un-initiated) and provide good examples.  This is
a heck of a lot easier with Ada 95 than it used to
be in Ada 83, so this approach is even better these
days than it once was.

Let's take an example.  Let's say that we get a
programmer in a C shop excited about the possibility
of using ATC ("select .. then abort").  This feature
is not available in C except via some convoluted
POSIX signal mess.  Then we show this programmer how
to use this in the context of their current system.
All he or she must do is write an Ada procedure
that "imports" a C function; this is then called in
the "then abort" section of the ATC.  Demonstrate
how to link it all using adainit and adafinal.
Voila; you have now initiated them into the world
of Ada.

BTW, Ada's tasking/concurrency features are ideal
for this kind of blending of systems; almost no
other language provides multi-tasking as a part
of the language (Java excepted), and in a large
project on a Unix system direct use of pthreads
and signaling is often confusing and messy.  Ada
can be introduced in such an environment as the
"tasking harness" from which the C system is
invoked via imported function calls.  Our company
has such an Ada harness for real-time simulation
systems and has delivered it for use in other
companies which are generally C or C++ "shops".
A project at one of these companies decided
to switch to using Ada for its own development
effort after receiving our harness!

Most shops will not be so extreme, but once Ada's
foot is in the door, it will find other users.
In spite of the snide remarks you always hear
being bandied about in the popular press and on
Usenet, I find there's not much deep prejudice
against Ada among C programmers I have worked with.
Of course some people are just that way, but I rarely
encounter it on a person-to-person basis.

Apart from the perception that "Ada is dead/dying"
(which is simply the result of poor marketing)
that causes programmers to shun Ada and acquire
skills that they think will get them good jobs,
the major barrier to introducing Ada into a lot of
"shops" is the lack of compilers for the specific
hosts/targets that they need to use.

For a C/C++ shop which produces a product that must run
on 12 different platforms, Ada cannot be an option if
only 6 of those platforms have Ada compilers.  This
will only change if the Ada market gets big enough to
motivate vendors to port their compilers, or if
Intermetrics' new Ada-to-C converter has a highly
portable run-time library.

Stanley Allen
mailto:[log in to unmask]

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

December 2017
November 2017
October 2017
September 2017
June 2017
May 2017
April 2017
January 2017
December 2016
November 2016
October 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
December 2010
November 2010
October 2010
September 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
June 2007
May 2007
March 2007
February 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
November 1999
October 1999
September 1999
August 1999
July 1999
June 1999
May 1999
April 1999
March 1999
February 1999
January 1999
December 1998
November 1998
October 1998
September 1998
August 1998
July 1998
June 1998
May 1998
April 1998
March 1998
February 1998
January 1998
December 1997
November 1997
October 1997
September 1997
August 1997
July 1997
June 1997
May 1997
April 1997
March 1997
February 1997
January 1997
December 1996
November 1996
October 1996

ATOM RSS1 RSS2



LISTSERV.ACM.ORG

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager