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.4 required=5.0 tests=AC_FROM_MANY_DOTS,BAYES_00 autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,24c886836d1e1ef8 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-08-27 07:18:21 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!psinet-eu-nl!psiuk-p4!uknet!psiuk-n!news.pace.co.uk!nh.pace.co.uk!not-for-mail From: "Marin David Condic" Newsgroups: comp.lang.ada Subject: Re: My Gnat is rusty - link error Date: Mon, 27 Aug 2001 10:04:42 -0400 Organization: Posted on a server owned by Pace Micro Technology plc Message-ID: <9mdk1r$r28$1@nh.pace.co.uk> References: <3B8571D0.64268D43@home.com> <9m3sfj$g48$1@nh.pace.co.uk> NNTP-Posting-Host: dhcp-200-133.miami.pace.co.uk X-Trace: nh.pace.co.uk 998921083 27720 136.170.200.133 (27 Aug 2001 14:04:43 GMT) X-Complaints-To: newsmaster@news.cam.pace.co.uk NNTP-Posting-Date: 27 Aug 2001 14:04:43 GMT X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Xref: archiver1.google.com comp.lang.ada:12465 Date: 2001-08-27T14:04:43+00:00 List-Id: I don't think so - not any worse than using WinSock is going to bind you to Windows anyway. Remember that a pragma that isn't recognized by another implementation is just going to get ignored anyway - so hopefully it would just get dropped on the floor. My advice would be to code up a package to do all of the usual sockets jobs, only at an Ada level of abstraction - hiding in the implementation beneath any of the WinSock specifics. The pragma should be isolated in this part of the code as well. From there, if you have to switch to a different flavor of sockets, at least its all in one isolated place with a minimal level of fuss. Using GNAT.Sockets might be a wonderful thing - except that now your code is GNAT dependent. This may not be bad depending on your project. Many projects are committed to a specific compiler. However, I think a *cleaner* idea would be for there to be some sort of Sockets support in a generalized Ada package (descending from Ada-dot-something?) that was reasonably standard across all implementations. Its technically doable - just a political question. Do the vendors want to standardize this and if so at what level? But this raises the whole "Standard Ada Library" question again..... MDC -- Marin David Condic Senior Software Engineer Pace Micro Technology Americas www.pacemicro.com Enabling the digital revolution e-Mail: marin.condic@pacemicro.com Web: http://www.mcondic.com/ "Simon Wright" wrote in message news:x7vheuwk4d1.fsf@smaug.pushface.org... > "Marin David Condic" writes: > > > I believe you have to specify either a linker option or put the following > > pragma into your code somewhere: > > > > pragma Linker_Options ("-lwsock32") ; > > > > Putting it in the code will make it harder to forget. :-) > > Of course, it also binds your code to Windows .. umm, perhaps that > won't matter until 3.14p comes out? (with GNAT.Sockets)