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=1.3 required=5.0 tests=BAYES_00,INVALID_MSGID, MSGID_RANDY autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,63585ba5c5be8595 X-Google-Attributes: gid103376,public From: Ted Dennison Subject: Re: Ada to Motif bindings Date: 2000/04/10 Message-ID: <8ct3pv$cnl$1@nnrp1.deja.com>#1/1 X-Deja-AN: 609189025 References: <38E8E8CE.81EC851F@mitre.org> <38EAC651.1DD94F40@home.com> <8cffvp$q0s$1@nnrp1.deja.com> <38EC2DC6.E17A407B@home.com> <38F17693.F32F2074@home.com> X-Http-User-Agent: Mozilla/4.7 [en] (WinNT; I) X-Http-Proxy: 1.0 x32.deja.com:80 (Squid/1.1.22) for client 204.48.27.130 Organization: Deja.com - Before you buy. X-Article-Creation-Date: Mon Apr 10 17:42:49 2000 GMT X-MyDeja-Info: XMYDJUIDtedennison Newsgroups: comp.lang.ada Date: 2000-04-10T00:00:00+00:00 List-Id: In article <38F17693.F32F2074@home.com>, Glen Cornell wrote: > > What features in Ada do you feel causes such a mismatch? > > I will point out that Xlib/Xt/Xm programming in Ada brings a new source > of potential errors: > > 1. Ada-c type conversions. That's kind of puzzing. Most objects X deals with are "cookie" objects, for which the internal structure is not to be mucked with. So there's really no need to do type conversions when using *either* language. Anyway, this is a binding issue. If the bindings have been properly tested, you don't have any problem here. > 2. Ada run-time conflicts with the Xt process model. Ditto. If the bindings have been tested for this, then this is *not* an issue for the bindings' users. > 3. Ada threads and the single-threaded nature of X. This is an issue with C as well. The only difference is that Ada supports threads and C users have to go to the OS to get them. That just means that C users tend to be less aware of this potential source of problems than Ada users. As an aside, I have seen X/Motif bindings that made the whole X/Motif subsystem task-safe by wrapping a synchronizing task around all the calls. This actually *removes* a potential source of errors that C X coders have to deal with. :-) -- T.E.D. http://www.telepath.com/~dennison/Ted/TED.html Sent via Deja.com http://www.deja.com/ Before you buy.