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.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,3398541ec18f6aa6 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news2.google.com!news.glorb.com!wn13feed!worldnet.att.net!bgtnsc05-news.ops.worldnet.att.net.POSTED!53ab2750!not-for-mail Newsgroups: comp.lang.ada From: anon@anon.org (anon) Subject: Re: Taking another spanking. Reply-To: anon@anon.org (anon) References: <6f8fcf5b-09d7-40b6-9ac3-ed7e9f228b89@t21g2000yqi.googlegroups.com> <4a2a6ef5$0$30223$9b4e6d93@newsspool1.arcor-online.net> X-Newsreader: IBM NewsReader/2 2.0 Message-ID: Date: Sat, 06 Jun 2009 17:56:50 GMT NNTP-Posting-Host: 12.64.120.20 X-Complaints-To: abuse@worldnet.att.net X-Trace: bgtnsc05-news.ops.worldnet.att.net 1244311010 12.64.120.20 (Sat, 06 Jun 2009 17:56:50 GMT) NNTP-Posting-Date: Sat, 06 Jun 2009 17:56:50 GMT Organization: AT&T Worldnet Xref: g2news2.google.com comp.lang.ada:6340 Date: 2009-06-06T17:56:50+00:00 List-Id: GNAT uses both Ada and C code to create it RTL. If they were truly serious about programmers not using the GNAT.Sockets.Thin package they would simply replace the Ada version of Thin with a C version. And may be the body of GNAT.Sockets. The deal is if your partition calls for streams type of Sockets then use GNAT.Sockets only. But if a package needs low_level access to the sockets interface such as creating a non-standard or security protocol, use GNAT.Sockets.Thin only and rebuild a replacement Sockets package. This is from a set of emails back in the late 1990s with Adacore. And besides why recreate the "pragma Import" from the Thin package in order to use those low_level routines. That just causes bad programming habits. Plus with the concept that the GNAT 2009 compiler including C and C like structures, I think Adacore wants the new programmers to act as if they if they are programming in C/C++ with the style of C/C++. Which means any thing goes! Comments are for the legal department! No programmer should care about the comments in any Ada packages, because as most of the posters here including Simon, Martin and yourself have said, Ada programmer must use the Ada RM for any reference. So, where is the additional RM sections that not only includes the Sockets, but explain the other device packages such as Printer, Serial, USB, etc? In <4a2a6ef5$0$30223$9b4e6d93@newsspool1.arcor-online.net>, Georg Bauhaus writes: >anon wrote: >> As for GNAT.Sockets.Thin -- I expand what "Robert Dewar" the CEO and >> one of the chief authors of GNAT said in Aug 3, 1996 at 3:00 am. >> "If you can do it in C, you can do it in Ada! Use pragma Import >> and call exactly the same routines that you would call from C." >> >> In this case, I expand that to: Why not use GNAT package GNAT.Sockets.Thin >> instead of re-creating a few "pragma import" or re-creating the Thin package. > >GNAT.Sockets is vendor specific, sockets aren't as far as Ada goes. >GNAT.Sockets.Thin is not only vendor specific, the vendor says you >should not use it. >Pragma Import is standard Ada. POSIX is a standard. >If sockets are ubiquituous, I'd think that the community >of Ada programmers might like vendor neutral sockets code. >Much more than it would like, say, IBM.Rational.Sockets.NonGNAT, >or GNAT.Sockets.Thin.