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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,7b65fc33a05f24b6 X-Google-Attributes: gid103376,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news3.google.com!news.germany.com!nuzba.szn.dk!news.jacob-sparre.dk!pnx.dk!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: A curiosity... Date: Thu, 4 Dec 2008 16:30:09 -0600 Organization: Jacob Sparre Andersen Message-ID: References: NNTP-Posting-Host: static-69-95-181-76.mad.choiceone.net X-Trace: munin.nbi.dk 1228429845 18001 69.95.181.76 (4 Dec 2008 22:30:45 GMT) X-Complaints-To: news@jacob-sparre.dk NNTP-Posting-Date: Thu, 4 Dec 2008 22:30:45 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5512 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Xref: g2news1.google.com comp.lang.ada:2881 Date: 2008-12-04T16:30:09-06:00 List-Id: "mockturtle" wrote in message news:a88dafcc-04d0-4a46-a168-7cb034894181@k41g2000yqn.googlegroups.com... ... > Few days ago a formerly student of mine came to > ask me something about (C) threads. She showed > me a tutorial she found somewhere (unfortunately > I do not know where, so I cannot give you any > reference). ... > Excuse me while I turn the heat up... I suddenly > feel a chill down my spine.... ;-) I thought you were going to show her (and us) the proper Ada way to do this. Otherwise, I think I'm missing your point. Every C-language interface that I've every used (the most important being Win32) is full of hacks to get around strong typing. This isn't news, or even a reflection on the C language itself. Claw is full of similar hacks (in Ada!) in order to use Win32 properly. The best thing to do with almost any C-language interface is to wrap it as thickly as possible to cover up as much as possible of that cruft. That's irrespective of the implementation language (why do you think MFC was so widely used??). Perhaps C programmers are so used to cruft that they fail to abstract it away properly, but that reflects more on the programmers (and the culture that they work it) than the language. Randy.