Seeking: Information about available Ada bindings

Seeking: Information about available Ada bindings

[Rush Kester]

As a member of SIGAda's Ada Bindings Working Group, I am hoping to put
together an exhibit of "Available Ada Bindings" for the SIGAda 2000
Conference.

If anyone, including vendors, would like to contribute ideas, please
contact me at
Rush.Kester@jhuapl.edu

My goal is to highlight:
  * Ada bindings available for COTS/Open Source software
  * Tools for generating Ada bindings for new API's

If you would like to contribute, please provide the following
information:
  Name of COTS/Open Source software/library
  Version of COTS/Open Source software/library
  Brief description of functionality offered by the binding
  References for additional information
  Location of Ada binding (URL or vendor contact)
  Description of Ada binding (e.g., thin, thick)
  Dependencies in addition to COTS/Open Source for which the binding is
made
    (E.g., other COTS/Open Source software required, compiler/platform,
etc.)

Thanks for your help!
Rush Kester
Charter member Team Ada
Software Systems Engineer
AdaSoft at Johns Hopkins Applied Physics Lab.
email:  rush.kester@jhuapl.edu
phone: (240) 228-3030 (live M-F 9:30am-4:30pm, voicemail anytime)
fax:   (240) 228-6779
http://hometown.aol.com/rwkester/myhomepage/index.html

Re: Seeking: Information about available Ada bindings

[Robert Dewar]

In article <392AB46D.465FDCAC@jhuapl.edu>,
  Rush Kester <Rush.Kester@jhuapl.edu> wrote:
> As a member of SIGAda's Ada Bindings Working Group, I am
hoping to put
> together an exhibit of "Available Ada Bindings" for the SIGAda
2000
> Conference.
>
> If anyone, including vendors, would like to contribute ideas,
please
> contact me at
> Rush.Kester@jhuapl.edu
>
> My goal is to highlight:
>   * Ada bindings available for COTS/Open Source software
>   * Tools for generating Ada bindings for new API's

The presentation here seems to imply that somehow COTS and
Open Source are distinct. In fact these are two orthogonal
concepts.

There can be software that definitely is NOT commercial off
the shelf software but is still open source. Examples are
unsupported research software that does not qualify as
commercial, or specialized software that is commercial but
not "off the shelf".

On the other hand there can definitely be COTS software that
happens to use a license that is compatible with the OSS
definitions. Note that the only difference between typical
open source software and software that is not considered
open source is

   a) the availability of sources
   b) the nature of the license

Certainly we consider GNAT to be COTS, it is most definitely
commercial software, and it is most definitely off the shelf.
Our "shelf" contains all sorts of standard software that we
distribute and support. Yes, like most companies we also do
specialized consulting that would not come under the COTS
description.

I make this point because this is not the first time I have run
into an informal viewpoint that there is a divide between the
notions of COTS and open source, and in fact this is an
incorrect distinction. We are not talking about POTS
(proprietary off the shelf software), but COTS, and most
certainly open source software can be commercial. There are
after all many large companies that are definitely commercial
in nature and built around open source and free software.

It is useful in such a catalog of bindings to talk about the
licensing issues, as Ted pointed out, and also about whether
the bindings are freely available and/or downloadable at no
charge. But let's not create an artificial and unuseful
distinction between OSS and COTS.

Robert Dewar
Ada Core Technologies


Sent via Deja.com http://www.deja.com/
Before you buy.

Re: Seeking: Information about available Ada bindings

[tmoran]

>>   * Ada bindings available for COTS/Open Source software
>The presentation here seems to imply that somehow COTS and
>Open Source are distinct. In fact these are two orthogonal
>concepts.
  Perhaps "Publicly Available" would have been a better term?
Presumably the intent is to have a list of Ada bindings that
many Ada users would find useful.  An Ada binding to the
concert hall acoustics simulation written in Fortran by Fred
across the hall probably doesn't qualify, but an Ada binding
to Windows or Linux surely does.  Price, source availability,
restrictions, etc should be available so the potential Ada
user can make his own decision about the usefulness, to him,
of the various bindings.

Re: Seeking: Information about available Ada bindings

[Ted Dennison]

In article <392AB46D.465FDCAC@jhuapl.edu>,
  Rush Kester <Rush.Kester@jhuapl.edu> wrote:

> If you would like to contribute, please provide the following
> information:
(snip).

If I were reading this myself as a resource, there's one other piece of
information I'd want to know about: Licensing.


--
T.E.D.

http://www.telepath.com/~dennison/Ted/TED.html


Sent via Deja.com http://www.deja.com/
Before you buy.

Re: Seeking: Information about available Ada bindings

[Robert Dewar]

In article <8geql3$1sg$1@nnrp1.deja.com>,
  Ted Dennison <dennison@telepath.com> wrote:
> In article <392AB46D.465FDCAC@jhuapl.edu>,
>   Rush Kester <Rush.Kester@jhuapl.edu> wrote:
>
> > If you would like to contribute, please provide the
following
> > information:
> (snip).
>
> If I were reading this myself as a resource, there's one other
piece of
> information I'd want to know about: Licensing.

and presumably cost :-)


Sent via Deja.com http://www.deja.com/
Before you buy.