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.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!hplabs!hpcc05!hpyhde4!hpycla!hpcuhc!hpcupt3!defaria@hpcupt3.cup.hp.com
From: defaria@hpcupt3.cup.hp.com (Andy DeFaria)
Newsgroups: comp.lang.ada
Subject: Re: X Bindings and Implementations
Message-ID: <46820004@hpcupt3.cup.hp.com>
Date: 8 Apr 91 17:03:32 GMT
References: <2260@winnie.fit.edu>
Organization: Hewlett Packard, Cupertino
List-Id: <comp.lang.ada>

>/ hpcupt3:comp.lang.ada / gsttallet@zach.fit.edu (Joe Tallet) /  4:48 pm  Apr  4, 1991 /
>
>I'm in need of information concerning different X products.  I am
>familiar with the following X products:
>
>        o  from Rational, an implementation of X written in Ada,
>        o  from MIT, Rational's Ada implementation of X,
>        o  from Verdix, Ada bindings to the C implementation of X,
>           this is the STARS 'version',
>        o  from GHG, an Ada implementation of X, similiar to
>           Rational's version?
>        o  from EVB, Ada bindings to MOTIF,
>        o  from TAE++, bindings or implementation?

Gee, you  left out  HP: HP has bindings to  Xlib, Xt and Motif.   These are
bindings to the C implementations (no need to reinvent the wheel eh!).

Also, I don't believe that EVB has bingings to MOTIF.  I've heard  they are
only Xlib bindings and are for the Mac.

>The reason that I am looking for this information is that I need to
>know what kinds of problems I will have in porting an application to
>these different X products.  Problems in terms of interface differences
>and Ada compiler support issues.
>
>  Please respond through e-mail to jot@sps.com or uunet to ...!uunet!sps!jot.
>I may not be able to review every response posted here.

Tried email, it didn't work.

Interfacewise, we tried to keep the interface as close to  the  C interface
as possible,  changing things only when they  made sense  Ada-wise, such as
the use of enumeration types and the like.  It's not that we  wouldn't want
a  clean implementation of these  products written  exclusively in Ada, but
the real question that comes up is who is going to  constantly roll the Ada
implementation each time X changes and how  long  will it  take them to get
newer versions to markets.  Our approach  and processes  helps us keep pace
with the changing X versions.

If you want more information about our products I suggest that  you contact
our marketing department:

Queene Mavor
California Language Labs
Hewlett Packard Company
Cupertino, CA 95014
(408)-447-7956