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: a07f3367d7,163994d4f34e92d0 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.180.95.2 with SMTP id dg2mr1585840wib.2.1344324555105; Tue, 07 Aug 2012 00:29:15 -0700 (PDT) Path: n2ni6330529win.0!nntp.google.com!volia.net!news2.volia.net!feed-A.news.volia.net!npeer.de.kpn-eurorings.net!npeer-ng0.de.kpn-eurorings.net!border2.nntp.ams2.giganews.com!border4.nntp.ams.giganews.com!border2.nntp.ams.giganews.com!border2.nntp.dca.giganews.com!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!ctu-peer!ctu-gate!news.nctu.edu.tw!usenet.stanford.edu!panix!newsfeed-00.mathworks.com!nntp.TheWorld.com!.POSTED!not-for-mail From: Robert A Duff Newsgroups: comp.lang.ada Subject: Re: how to tell gnatmake to send executables to a different directory when compiling multi source? Date: Thu, 02 Aug 2012 11:08:19 -0400 Organization: The World Public Access UNIX, Brookline, MA Message-ID: References: <214bbd15-f7cb-4710-a6a7-64f37923bf4e@googlegroups.com> <87wr1moexq.fsf@ludovic-brenta.org> <87sjcaoa08.fsf@ludovic-brenta.org> <50167d29$0$6570$9b4e6d93@newsspool4.arcor-online.net> <873947cbja.fsf@catnip.gol.com> NNTP-Posting-Host: shell01.theworld.com Mime-Version: 1.0 X-Trace: pcls6.std.com 1343920099 20343 192.74.137.71 (2 Aug 2012 15:08:19 GMT) X-Complaints-To: abuse@TheWorld.com NNTP-Posting-Date: Thu, 2 Aug 2012 15:08:19 +0000 (UTC) User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.3 (irix) Cancel-Lock: sha1:hXI2t2VI5DvCYKTG7DruhwYiWEI= Content-Type: text/plain; charset=us-ascii Date: 2012-08-02T11:08:19-04:00 List-Id: "J-P. Rosen" writes: > Well, apparently it assumes that #include is used for every needed > library - and nothing /requires/ that in the C standard. An > undisciplined programmer could copy lines instead of #including them, > and then all tools will be fooled. I don't think that's a very strong criticism of C. Yeah, you're right that it's not required to use #include properly, but every competent C programmer does so. It's not like you can do it wrong by accident. Compare to (say) array indexing, where it's easy to accidentally go out of bounds. Of course I agree that a language with a proper module system is better. Patient: "Doctor, it hurts when I copy lines instead of #including them." Doctor: "So don't do that." - Bob